linux-kernel - Re: New crashes walking proc with Saturday's git

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 23 Nov 2014 11:16:51 -0500
From:	Chris Mason <clm@...com>
To:	Borislav Petkov <bp@...en8.de>
CC:	<torvalds@...ux-foundation.org>, <linux-kernel@...r.kernel.org>
Subject: Re: New crashes walking proc with Saturday's git



On Sun, Nov 23, 2014 at 11:11 AM, Borislav Petkov <bp@...en8.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 <clm@...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 going.  I'll 
>> try to
>>  bisect.
> 
> I'm seeing the same thing:


It must be:

commit 6e998916dfe327e785e7c2447959b2c1a3ea4930
Author: Stanislaw Gruszka <sgruszka@...hat.com>
Date:   Wed Nov 12 16:58:44 2014 +0100

    sched/cputime: Fix clock_nanosleep()/clock_gettime() inconsistency

I'll do two runs to confirm, but it's the only related patch between 
rc5 and now.

-chris




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