From: Andrew Morton <akpm@linux-foundation.org>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Tony Luck <tony.luck@intel.com>,
Andi Kleen <andi.kleen@intel.com>,
Wu Fengguang <fengguang.wu@intel.com>,
Ingo Molnar <mingo@elte.hu>,
Jun'ichi Nomura <j-nomura@ce.jp.nec.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 2/2 v2] mm: print out information of file affected by memory error
Date: Tue, 6 Nov 2012 14:52:20 -0800 [thread overview]
Message-ID: <20121106145220.52a52829.akpm@linux-foundation.org> (raw)
In-Reply-To: <1352241905-4657-1-git-send-email-n-horiguchi@ah.jp.nec.com>
On Tue, 6 Nov 2012 17:45:05 -0500
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> wrote:
> > "should be" and "unlikely" aren't very reassuring things to hear!
> > Emitting a million lines into syslog is pretty poor behaviour and
> > should be reliably avoided.
>
> So capping maximum lines of messages per some duration (a hour or a day)
> is a possible option. BTW, even if we don't apply this patch, the kernel
> can emit million lines of messages in the above-mentioned situation because
> each memory error event emits a message like "MCE 0x3f57f4: dirty LRU page
> recovery: Ignored" on syslog. If it's also bad, we need to do capping
> also over existing printk()s, right?
Yes, that sounds like a bug report waiting to happen.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Tony Luck <tony.luck@intel.com>,
Andi Kleen <andi.kleen@intel.com>,
Wu Fengguang <fengguang.wu@intel.com>,
Ingo Molnar <mingo@elte.hu>,
"Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 2/2 v2] mm: print out information of file affected by memory error
Date: Tue, 6 Nov 2012 14:52:20 -0800 [thread overview]
Message-ID: <20121106145220.52a52829.akpm@linux-foundation.org> (raw)
In-Reply-To: <1352241905-4657-1-git-send-email-n-horiguchi@ah.jp.nec.com>
On Tue, 6 Nov 2012 17:45:05 -0500
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> wrote:
> > "should be" and "unlikely" aren't very reassuring things to hear!
> > Emitting a million lines into syslog is pretty poor behaviour and
> > should be reliably avoided.
>
> So capping maximum lines of messages per some duration (a hour or a day)
> is a possible option. BTW, even if we don't apply this patch, the kernel
> can emit million lines of messages in the above-mentioned situation because
> each memory error event emits a message like "MCE 0x3f57f4: dirty LRU page
> recovery: Ignored" on syslog. If it's also bad, we need to do capping
> also over existing printk()s, right?
Yes, that sounds like a bug report waiting to happen.
next prev parent reply other threads:[~2012-11-06 22:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 16:33 [PATCH 0/2] HWPOISON: improve logging Naoya Horiguchi
2012-11-02 16:33 ` Naoya Horiguchi
2012-11-02 16:33 ` [PATCH 1/2 v2] HWPOISON: fix action_result() to print out dirty/clean Naoya Horiguchi
2012-11-02 16:33 ` Naoya Horiguchi
2012-11-05 21:56 ` Andrew Morton
2012-11-05 21:56 ` Andrew Morton
2012-11-05 22:40 ` [PATCH v3] HWPOISON: fix action_result() to print out dirty/clean (Re: [PATCH 1/2 v2] HWPOISON: fix action_result() to print out) dirty/clean Naoya Horiguchi
2012-11-05 22:40 ` Naoya Horiguchi
2012-11-02 16:33 ` [PATCH 2/2 v2] mm: print out information of file affected by memory error Naoya Horiguchi
2012-11-02 16:33 ` Naoya Horiguchi
2012-11-05 22:01 ` Andrew Morton
2012-11-05 22:01 ` Andrew Morton
2012-11-06 5:07 ` Naoya Horiguchi
2012-11-06 5:07 ` Naoya Horiguchi
2012-11-06 20:12 ` Andrew Morton
2012-11-06 20:12 ` Andrew Morton
2012-11-06 22:45 ` Naoya Horiguchi
2012-11-06 22:45 ` Naoya Horiguchi
2012-11-06 22:52 ` Andrew Morton [this message]
2012-11-06 22:52 ` Andrew Morton
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=20121106145220.52a52829.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=fengguang.wu@intel.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.