Re: Linux 2.1.125 doesn't dump core on SIGSEGV

Chris Wedgwood (cw@ix.net.nz)
Fri, 13 Nov 1998 11:08:55 +1300


On Thu, Nov 12, 1998 at 09:05:05AM -0800, Ken Pizzini wrote:

> (bit patterns made up for example purposes):
> #define O_CREAT 0x50
> #define O_EXCL 0xa0
> #define O_NOFOLLOW 0xc0
>
> Then we get (O_CREAT|O_EXCL) == (O_CREAT|O_EXCL|O_NOFOLLOW),
> but we can detect that none of O_CREAT, O_EXCL, ((O_CREAT|O_EXCL)&~O_NOFOLLOW)
> match (x&O_NOFOLLOW)==O_NOFOLLOW.
>
> Would this be an acceptable solution?

No, because open(..,O_RDWR|O_NOFOLLOW) won't work as expected then.

For now, I think things should stay as they are... people have
pointed out examples of thing that will go bad and have horribly
failure modes if its changed - something that won't help linux's
reputation.

I think this thread should be left to die now...

-cw

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/