From: "Paul Menage" <menage@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [PATCH] mm/cgroup.c add error check
Date: Wed, 7 May 2008 00:43:45 -0700 [thread overview]
Message-ID: <6599ad830805070043y4465a32h8e26c5e8890b1100@mail.gmail.com> (raw)
In-Reply-To: <20080507164526.884208f9.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, May 7, 2008 at 12:45 AM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@jp.fujitsu.com> wrote:
> Hmm, but It seems call_usermodehelper()'s fails in silent, no messages.
> A notify which can be silently dropped is useless.
True, but if we're so short of memory that we can't fork, userspace
probably won't be able to do much about the notification even if it
gets it.
> Can we add 'printk("notify_on_release: ... is failed")' or some workaround ?
>
Sounds reasonable for debugging, but don't expect any automated
middleware to notice it.
Paul
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-05-07 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 11:02 [PATCH] mm/cgroup.c add error check KOSAKI Motohiro
2008-05-06 12:43 ` Andi Kleen
2008-05-06 13:02 ` KOSAKI Motohiro
2008-05-06 18:32 ` Andi Kleen
2008-05-06 20:19 ` KOSAKI Motohiro
2008-05-07 5:08 ` Paul Menage
2008-05-07 7:45 ` KAMEZAWA Hiroyuki
2008-05-07 7:43 ` Paul Menage [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=6599ad830805070043y4465a32h8e26c5e8890b1100@mail.gmail.com \
--to=menage@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
/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;
as well as URLs for NNTP newsgroup(s).