Re: Kernel Oops on locking sockets via fcntl()

2000-11-28 Thread David S. Miller
This should fix the bug, there were some cases outside of file locking (bonus points to anyone who can craft an exploit for the ELF interpreter case :-): --- ./fs/binfmt_elf.c.~1~ Mon Oct 30 11:34:25 2000 +++ ./fs/binfmt_elf.c Tue Nov 28 03:03:43 2000 @@ -247,7 +247,7 @@

Re: Kernel Oops on locking sockets via fcntl()

2000-11-27 Thread Andi Kleen
On Mon, Nov 27, 2000 at 03:59:05PM +0300, Igor Yu. Zhbanov wrote: > On Fri, 24 Nov 2000, Andi Kleen wrote: > > > On Fri, Nov 24, 2000 at 04:32:26PM +0300, Igor Yu. Zhbanov wrote: > > > Hello! > > > > > > One fine day accidentally I have opened an Xserver's socket placed in /tmp > > > with my fav

Re: Kernel Oops on locking sockets via fcntl()

2000-11-27 Thread Igor Yu. Zhbanov
On Fri, 24 Nov 2000, Andi Kleen wrote: > On Fri, Nov 24, 2000 at 04:32:26PM +0300, Igor Yu. Zhbanov wrote: > > Hello! > > > > One fine day accidentally I have opened an Xserver's socket placed in /tmp > > with my favourite text editor "le". I have got a message from the kernel similar > > to thi

Re: Kernel Oops on locking sockets via fcntl()

2000-11-24 Thread Andi Kleen
On Fri, Nov 24, 2000 at 04:32:26PM +0300, Igor Yu. Zhbanov wrote: > Hello! > > One fine day accidentally I have opened an Xserver's socket placed in /tmp > with my favourite text editor "le". I have got a message from the kernel similar > to this: Which kernel version are you using ? It should