Re: [PATCH] Use NULL instead of integer 0 in security/selinux/

[viro]

On Sun, Jul 11, 2004 at 12:29:51PM +0200, Geert Uytterhoeven wrote:
> But why does sparse complain about
> 
>     p->thread.fs = get_fs().seg;
> 
> with
> 
>     linux-m68k-2.6.7/arch/m68k/kernel/process.c:265:23: warning: expected lvalue for member dereference
> 
> ? Looks valid to me?

It is valid and should be left alone.  sparse doesn't handle that area and
unless somebody feels heroic it will stay that way.

Note that there are very scary critters in that part of language - among
other things it contains such fun as arrays that can't be converted to
pointers in normal way, etc. (arrays that have no address, while we are
at it).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/