From: Vasiliy Kulikov <segoon@openwall.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Manuel Lauss <manuel.lauss@googlemail.com>,
linux-kernel@vger.kernel.org, Richard Weinberger <richard@nod.at>,
Marc Zyngier <maz@misterjones.org>, Ingo Molnar <mingo@elte.hu>,
kernel-hardening@lists.openwall.com,
"Paul E. McKenney" <paul.mckenney@linaro.org>,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [kernel-hardening] Re: [PATCH] shm: fix a race between shm_exit() and shm_init()
Date: Wed, 3 Aug 2011 23:52:58 +0400 [thread overview]
Message-ID: <20110803195258.GA7063@albatros> (raw)
In-Reply-To: <20110803123352.88670c9c.akpm@linux-foundation.org>
On Wed, Aug 03, 2011 at 12:33 -0700, Andrew Morton wrote:
> > > + /*
> > > + * For init_ipc_ns shm_ids().rw_mutex is statically initialized
> > > + * as kernel threads should be able to use it in do_exit() before
> > > + * shm_init(), which is called on do_initcall()
> > > + */
> > > + if (ns == &init_ipc_ns)
> > > + ipc_init_ids(&shm_ids(ns));
> > > + else
> > > + ipc_init_ids(&shm_ids(ns));
>
> afacit init_ipc_ns.ids[0].rw_mutex and init_ipc_ns.ids[1].rw_mutex
> never get initialised with this patch?
No, these .rw_mutex are initialized in runtime, as before.
This patch should fix the specific oops (not a dependency issue):
https://lkml.org/lkml/2011/8/3/256
> Still. It seems that the real bug is that driver_init() is trying to
> invoke userspace helpers before the kernel is ready to run userspace.
What if declare a completion, trigger it after all ns init code is
finished, and wait on the completion inside of
call_usermodehelper_exec()?
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
prev parent reply other threads:[~2011-08-03 19:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 18:01 initcall dependency problem (ns vs. threads) Vasiliy Kulikov
2011-08-01 18:20 ` Andrew Morton
2011-08-01 18:34 ` [kernel-hardening] " Vasiliy Kulikov
2011-08-01 19:03 ` Vasiliy Kulikov
2011-08-01 19:07 ` Andrew Morton
2011-08-01 19:22 ` Vasiliy Kulikov
2011-08-02 0:01 ` Linus Torvalds
2011-08-02 12:45 ` [PATCH] shm: fix a race between shm_exit() and shm_init() Vasiliy Kulikov
2011-08-02 12:51 ` Manuel Lauss
2011-08-02 13:23 ` Richard Weinberger
2011-08-02 13:29 ` Marc Zyngier
2011-08-02 20:33 ` Andrew Morton
2011-08-02 20:55 ` Andrew Morton
2011-08-03 5:30 ` Manuel Lauss
2011-08-03 8:05 ` Marc Zyngier
2011-08-03 8:19 ` Linus Torvalds
2011-08-03 10:04 ` Manuel Lauss
2011-08-03 10:30 ` Marc Zyngier
2011-08-03 13:13 ` Thadeu Lima de Souza Cascardo
2011-08-03 13:33 ` Kay Sievers
2011-08-03 13:45 ` Richard Weinberger
2011-08-04 0:35 ` Linus Torvalds
2011-08-04 0:50 ` Andrew Morton
2011-08-04 1:01 ` Linus Torvalds
2011-08-04 1:15 ` Kay Sievers
2011-08-04 8:26 ` Marc Zyngier
2011-08-03 7:43 ` Linus Torvalds
2011-08-03 7:50 ` Manuel Lauss
2011-08-03 8:00 ` Manuel Lauss
2011-08-03 19:33 ` Andrew Morton
2011-08-03 19:52 ` Vasiliy Kulikov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110803195258.GA7063@albatros \
--to=segoon@openwall.com \
--cc=akpm@linux-foundation.org \
--cc=kay.sievers@vrfy.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.lauss@googlemail.com \
--cc=maz@misterjones.org \
--cc=mingo@elte.hu \
--cc=paul.mckenney@linaro.org \
--cc=richard@nod.at \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox