From: Richard Weinberger <richard@nod.at>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Thadeu Lima de Souza Cascardo <cascardo@minaslivre.org>,
linux-kernel@vger.kernel.org, marc.zyngier@arm.com,
manuel.lauss@googlemail.com, torvalds@linux-foundation.org,
akpm@linux-foundation.org, segoon@openwall.com, gregkh@suse.de
Subject: Re: [PATCH] shm: fix a race between shm_exit() and shm_init()
Date: Wed, 3 Aug 2011 15:45:00 +0200 [thread overview]
Message-ID: <201108031545.01122.richard@nod.at> (raw)
In-Reply-To: <CAPXgP12Ocdcmh7USsPv+WzYFTSh3EFi++q7YWop-XEUjrXfQAw@mail.gmail.com>
On Mittwoch 03 August 2011 15:33:27 Kay Sievers wrote:
> On Wed, Aug 3, 2011 at 15:13, Thadeu Lima de Souza Cascardo
>
> <cascardo@minaslivre.org> wrote:
> > As Marc Zyngier has pointed out, the culprit is driver_init, which
> > calls devices_init. I'd say other calls from driver_init also call into
> > kset and kobject, which will dispatch uevent helper.
> >
> > I tried to reproduce the problem using UML and only was successful after
> > setting CONFIG_UEVENT_HELPER_PATH. I guess we could obsolete this
> > feature and plan its removal soon. Is anybody still using this?
>
> Forking binaries from the kernel for frequent events is something
> fundamentally wrong to do. It is not even rate-limited or has any
> upper bounds. It is known to create out-of-memory situations on
> machines with many devices and tiny RAM. Configs that virtualizations
> with many guests use pretty often. They can not even bootup with
> /sbin/hotplug enabled then.
>
> It would be nice to remove that broken thing, no common system or
> distro uses it since quite some years now. But I wouldn't be surprised
> if some people still use it for whatever hack they need locally.
>
True.
I'll remove CONFIG_UEVENT_HELPER_PATH from UML's defconfig.
Thanks,
//richard
next prev parent reply other threads:[~2011-08-03 13:45 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 [this message]
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 ` [kernel-hardening] " Vasiliy Kulikov
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=201108031545.01122.richard@nod.at \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=cascardo@minaslivre.org \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.lauss@googlemail.com \
--cc=marc.zyngier@arm.com \
--cc=segoon@openwall.com \
--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
all inboxes | Powered by JetHome®