linux-kernel - Re: [BUG stable, 2.6.32.27] sched: delayed cleanup of user

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:	Mon, 10 Jan 2011 15:01:30 +0100
From:	Stefan Priebe - Profihost AG <s.priebe@...fihost.ag>
To:	Oleg Nesterov <oleg@...hat.com>
CC:	Kay Sievers <kay.sievers@...y.org>,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG stable, 2.6.32.27] sched: delayed cleanup of user_struct


>> is it a workaround to disable CONFIG_GROUP_SCHED?
>                                  ^^^^^^^^^^^^^^^^^^
> CONFIG_USER_SCHED, not CONFIG_GROUP_SCHED.
correct but CONFIG_USER_SCHED depends on CONFIG_GROUP_SCHED and as we 
don't use CONFIG_GROUP_SCHED at all my idea was to completely remove 
this feature.

> I think that disabling it should obviously help. But it is
> possible that there is something else. Given that you can
> reproduce the crash, it would be nice if you can test this
> and report ;)
Main problem - right i can't reproduce it. But the system was crashing 
two times more in the past.

You can find the logs here:
http://pastebin.com/hNd15E8K

> Or. You can revert
> 	b00bc0b237055b4c45816325ee14f0bd83e6f590
> 	uids: Prevent tear down race
>
> 	3959214f971417f4162926ac52ad4cd042958caa
> 	sched: delayed cleanup of user_struct
Not sure if it is a good idea to introduce another race again.

Stefan
--
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/