Re: Serious reproducible 2.4.x kernel hang

2001-02-03 Thread kees
Hi, What is related in /proc w.r.t. sysrq? Kees - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/

Re: [Patch]Re: Serious reproducible 2.4.x kernel hang

2001-02-02 Thread David S. Miller
Prasanna P Subash writes: > I looked at the skb_recv_datagram code and noticed that wait_for_packet is not > returning an error, even while trying to read a closed socket. > Anyways here is a patch against 2.4.1 that will fix the issue. > Please feel free to flame me about the patch :) Pleas

[Patch]Re: Serious reproducible 2.4.x kernel hang

2001-02-02 Thread Prasanna P Subash
> #include > #include > #include > #include > > int > main(int argc, const char* argv[]) > { > int retval; > int sockets[2]; > char buf[1]; > > retval = socketpair(PF_UNIX, SOCK_DGRAM, 0, sockets); > if (retval != 0) > { > perror("socketpair"); > exit(1); > } > shut

Re: Serious reproducible 2.4.x kernel hang

2001-02-01 Thread Doug McNaught
Chris Evans <[EMAIL PROTECTED]> writes: > [cc: davem because of the severity] > > On Thu, 1 Feb 2001, Malcolm Beattie wrote: > > > rid of the hang. So it looks as though some combination of > > shutdown(2) and SIGABRT is at fault. After the hang the kernel-side > > Nope - I've nailed it to a _

Re: Serious reproducible 2.4.x kernel hang

2001-02-01 Thread rui.sousa
On Thu, 1 Feb 2001, Chris Evans wrote: > > Nope - I've nailed it to a _really_ simple test case. It looks like a > read() on a shutdown() unix dgram socket just kills the kernel. Demo code > below. I wonder if this affects UP or is SMP only? It surely killed my PIII UP machine (running 2.4.1) R

Re: Serious reproducible 2.4.x kernel hang

2001-02-01 Thread Chris Evans
[cc: davem because of the severity] On Thu, 1 Feb 2001, Malcolm Beattie wrote: > rid of the hang. So it looks as though some combination of > shutdown(2) and SIGABRT is at fault. After the hang the kernel-side Nope - I've nailed it to a _really_ simple test case. It looks like a read() on a sh

Re: Serious reproducible 2.4.x kernel hang

2001-02-01 Thread Chris Evans
On Thu, 1 Feb 2001, Malcolm Beattie wrote: > Mapping the addresses from whichever ScrollLock combination produced > the task list to symbols produces the call trace > do_exit <- do_signal <- tcp_destroy_sock <- inet_ioctl <- signal_return > > The inet_ioctl is odd there--vsftpd doesn't explicit

Re: Serious reproducible 2.4.x kernel hang

2001-02-01 Thread Malcolm Beattie
Chris Evans writes: > > On Thu, 1 Feb 2001, Malcolm Beattie wrote: > > > Mapping the addresses from whichever ScrollLock combination produced > > the task list to symbols produces the call trace > > do_exit <- do_signal <- tcp_destroy_sock <- inet_ioctl <- signal_return > > > > The inet_ioctl i

Re: Serious reproducible 2.4.x kernel hang

2001-02-01 Thread Malcolm Beattie
Malcolm Beattie writes: > Chris Evans writes: > > I've just managed to reproduce this personally on 2.4.0. I've had a report > > that 2.4.1 is also affected. Both myself and the other person who > > reproduced this have SMP i686 machines, which may or may not be relevant. > > > > To reproduce, al

Re: Serious reproducible 2.4.x kernel hang

2001-02-01 Thread Chris Evans
On Thu, 1 Feb 2001, Malcolm Beattie wrote: > Chris Evans writes: > > I've just managed to reproduce this personally on 2.4.0. I've had a report > > that 2.4.1 is also affected. Both myself and the other person who > > reproduced this have SMP i686 machines, which may or may not be relevant. > >

Re: Serious reproducible 2.4.x kernel hang

2001-02-01 Thread Malcolm Beattie
Chris Evans writes: > I've just managed to reproduce this personally on 2.4.0. I've had a report > that 2.4.1 is also affected. Both myself and the other person who > reproduced this have SMP i686 machines, which may or may not be relevant. > > To reproduce, all you need to do is get my vsftpd ft

Serious reproducible 2.4.x kernel hang

2001-02-01 Thread Chris Evans
Hi, I've just managed to reproduce this personally on 2.4.0. I've had a report that 2.4.1 is also affected. Both myself and the other person who reproduced this have SMP i686 machines, which may or may not be relevant. To reproduce, all you need to do is get my vsftpd ftp server: ftp://ferret.l