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:	Tue, 01 Sep 2009 16:22:11 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Ingo Molnar <mingo@...e.hu>, arjan@...radead.org, jeremy@...p.org,
	mschmidt@...hat.com, mingo@...hat.com, hpa@...or.com,
	linux-kernel@...r.kernel.org, tj@...nel.org, tglx@...utronix.de,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-tip-commits@...r.kernel.org,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 0/1] kthreads: simplify !kthreadd_task logic, kill kthreadd_task_init_done

Oleg Nesterov <oleg@...hat.com> writes:

> On 09/01, Oleg Nesterov wrote:
>>
>> On 09/01, Ingo Molnar wrote:
>> >
>> > * Oleg Nesterov <oleg@...hat.com> wrote:
>> >
>> > > On 09/01, Ingo Molnar wrote:
>> > > >
>> > > > * Oleg Nesterov <oleg@...hat.com> wrote:
>> > > >
>> > > > > Yes, this should work. But I _think_ we can make the better fix...
>> > > > >
>> > > > > I'll try to make the patch soon. Afaics we don't need
>> > > > > kthreadd_task_init_done.
>> > > >
>> > > > ok.
>> > >
>> > > Just in case, the patch is ready. [...]
>> >
>> > yes - that's roughly the cleanup i referred to in the commit log.
>> >
>> > way too late for -rc8 though - the minimal fix i did _might_ be
>> > eligible.
>> >
>> > agreed?
>>
>> Agreed. Then I will sent the patch on top of this change.
>
> OK, I am sending the patch on top of your fix. Not sure how to really
> test it, but at least the kernel works when I apply the debugging patch
> below on top.

Stupid question.  How is it that we wind up trying to start kernel threads
before it is safe to do so?

Races should be impossible because the scheduler isn't running until a few
lines later.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ