Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 4:38 PM, Thomas Gleixner wrote: On Sun, 23 Nov 2014, Chris Mason wrote: On Sun, Nov 23, 2014 at 4:05 PM, Thomas Gleixner wrote: > On Sun, 23 Nov 2014, Chris Mason wrote: > > On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov wrote: > > > On Sun, Nov 23, 2014

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Borislav Petkov
On Sun, Nov 23, 2014 at 04:29:53PM -0500, Chris Mason wrote: > 11 minutes later and it's still alive. I'll keep an eye on it and yell > if it falls over. Ditto. Box here suspends and resumes fine even while the fork bomb is running. I'll watch it the next days just in case though.

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Thomas Gleixner
On Sun, 23 Nov 2014, Chris Mason wrote: > On Sun, Nov 23, 2014 at 4:05 PM, Thomas Gleixner wrote: > > On Sun, 23 Nov 2014, Chris Mason wrote: > > > On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov wrote: > > > > On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: > > > > > It must

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 4:11 PM, Chris Mason wrote: On Sun, Nov 23, 2014 at 4:05 PM, Thomas Gleixner wrote: On Sun, 23 Nov 2014, Chris Mason wrote: On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov wrote: > On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: > > It must be:

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 4:05 PM, Thomas Gleixner wrote: On Sun, 23 Nov 2014, Chris Mason wrote: On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov wrote: > On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: > > It must be: > > > > commit

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Thomas Gleixner
On Sun, 23 Nov 2014, Chris Mason wrote: > On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov wrote: > > On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: > > > It must be: > > > > > > commit 6e998916dfe327e785e7c2447959b2c1a3ea4930 > > > Author: Stanislaw Gruszka > > > Date: Wed

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Borislav Petkov
On Sun, Nov 23, 2014 at 11:49:02AM -0500, Chris Mason wrote: > I've adding Ingo and Stanislaw to the cc. With > 6e998916dfe327e785e7c2447959b2c1a3ea4930 reverted, I'm no longer crashing. Ok, reverting here too, to confirm. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov wrote: On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: It must be: commit 6e998916dfe327e785e7c2447959b2c1a3ea4930 Author: Stanislaw Gruszka Date: Wed Nov 12 16:58:44 2014 +0100 sched/cputime: Fix

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov wrote: On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: It must be: commit 6e998916dfe327e785e7c2447959b2c1a3ea4930 Author: Stanislaw Gruszka Date: Wed Nov 12 16:58:44 2014 +0100 sched/cputime: Fix

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Borislav Petkov
On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: > It must be: > > commit 6e998916dfe327e785e7c2447959b2c1a3ea4930 > Author: Stanislaw Gruszka > Date: Wed Nov 12 16:58:44 2014 +0100 > >sched/cputime: Fix clock_nanosleep()/clock_gettime() inconsistency > > I'll do two runs to

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 11:11 AM, Borislav Petkov wrote: On Sun, Nov 23, 2014 at 10:56:27AM -0500, Chris Mason wrote: On Sun, Nov 23, 2014 at 10:02 AM, Chris Mason wrote: >Since it looks like a race between process exit and /proc, I'll try to >hammer on that for a better reproduction.

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Borislav Petkov
On Sun, Nov 23, 2014 at 10:56:27AM -0500, Chris Mason wrote: > On Sun, Nov 23, 2014 at 10:02 AM, Chris Mason wrote: > >Since it looks like a race between process exit and /proc, I'll try to > >hammer on that for a better reproduction. But, here's hoping that > >someone has already seen this one:

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 10:02 AM, Chris Mason wrote: Since it looks like a race between process exit and /proc, I'll try to hammer on that for a better reproduction. But, here's hoping that someone has already seen this one: It falls over in less than 5 minutes with a fork bomb going. I'll

New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
Hi everyone, I was running some tests on Saturday before my pull, and I'm now hitting this consistently across two boxes. One box has plain linus git: commit cb95413971d605b0d152d3ceecc47ba8991d66fb Merge: ecde006 6bab4a8 Author: Linus Torvalds Date: Sat Nov 22 14:33:11 2014 -0800 The other

New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
Hi everyone, I was running some tests on Saturday before my pull, and I'm now hitting this consistently across two boxes. One box has plain linus git: commit cb95413971d605b0d152d3ceecc47ba8991d66fb Merge: ecde006 6bab4a8 Author: Linus Torvalds torva...@linux-foundation.org Date: Sat Nov 22

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 10:02 AM, Chris Mason c...@fb.com wrote: Since it looks like a race between process exit and /proc, I'll try to hammer on that for a better reproduction. But, here's hoping that someone has already seen this one: It falls over in less than 5 minutes with a fork bomb

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Borislav Petkov
On Sun, Nov 23, 2014 at 10:56:27AM -0500, Chris Mason wrote: On Sun, Nov 23, 2014 at 10:02 AM, Chris Mason c...@fb.com wrote: Since it looks like a race between process exit and /proc, I'll try to hammer on that for a better reproduction. But, here's hoping that someone has already seen this

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 11:11 AM, Borislav Petkov b...@alien8.de wrote: On Sun, Nov 23, 2014 at 10:56:27AM -0500, Chris Mason wrote: On Sun, Nov 23, 2014 at 10:02 AM, Chris Mason c...@fb.com wrote: Since it looks like a race between process exit and /proc, I'll try to hammer on that for

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Borislav Petkov
On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: It must be: commit 6e998916dfe327e785e7c2447959b2c1a3ea4930 Author: Stanislaw Gruszka sgrus...@redhat.com Date: Wed Nov 12 16:58:44 2014 +0100 sched/cputime: Fix clock_nanosleep()/clock_gettime() inconsistency I'll do

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov b...@alien8.de wrote: On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: It must be: commit 6e998916dfe327e785e7c2447959b2c1a3ea4930 Author: Stanislaw Gruszka sgrus...@redhat.com Date: Wed Nov 12 16:58:44 2014 +0100

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov b...@alien8.de wrote: On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: It must be: commit 6e998916dfe327e785e7c2447959b2c1a3ea4930 Author: Stanislaw Gruszka sgrus...@redhat.com Date: Wed Nov 12 16:58:44 2014 +0100

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Borislav Petkov
On Sun, Nov 23, 2014 at 11:49:02AM -0500, Chris Mason wrote: I've adding Ingo and Stanislaw to the cc. With 6e998916dfe327e785e7c2447959b2c1a3ea4930 reverted, I'm no longer crashing. Ok, reverting here too, to confirm. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Thomas Gleixner
On Sun, 23 Nov 2014, Chris Mason wrote: On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov b...@alien8.de wrote: On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: It must be: commit 6e998916dfe327e785e7c2447959b2c1a3ea4930 Author: Stanislaw Gruszka sgrus...@redhat.com

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 4:05 PM, Thomas Gleixner t...@linutronix.de wrote: On Sun, 23 Nov 2014, Chris Mason wrote: On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov b...@alien8.de wrote: On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason wrote: It must be: commit

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 4:11 PM, Chris Mason c...@fb.com wrote: On Sun, Nov 23, 2014 at 4:05 PM, Thomas Gleixner t...@linutronix.de wrote: On Sun, 23 Nov 2014, Chris Mason wrote: On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov b...@alien8.de wrote: On Sun, Nov 23, 2014 at 11:16:51AM

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Thomas Gleixner
On Sun, 23 Nov 2014, Chris Mason wrote: On Sun, Nov 23, 2014 at 4:05 PM, Thomas Gleixner t...@linutronix.de wrote: On Sun, 23 Nov 2014, Chris Mason wrote: On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov b...@alien8.de wrote: On Sun, Nov 23, 2014 at 11:16:51AM -0500, Chris Mason

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Borislav Petkov
On Sun, Nov 23, 2014 at 04:29:53PM -0500, Chris Mason wrote: 11 minutes later and it's still alive. I'll keep an eye on it and yell if it falls over. Ditto. Box here suspends and resumes fine even while the fork bomb is running. I'll watch it the next days just in case though.

Re: New crashes walking proc with Saturday's git

2014-11-23 Thread Chris Mason
On Sun, Nov 23, 2014 at 4:38 PM, Thomas Gleixner t...@linutronix.de wrote: On Sun, 23 Nov 2014, Chris Mason wrote: On Sun, Nov 23, 2014 at 4:05 PM, Thomas Gleixner t...@linutronix.de wrote: On Sun, 23 Nov 2014, Chris Mason wrote: On Sun, Nov 23, 2014 at 11:32 AM, Borislav Petkov