Re: [PATCH 2/2 v2] mm: print out information of file affected by memory error

2012-11-06 Thread Andrew Morton
On Tue, 6 Nov 2012 17:45:05 -0500 Naoya Horiguchi 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 hou

Re: [PATCH 2/2 v2] mm: print out information of file affected by memory error

2012-11-06 Thread Naoya Horiguchi
On Tue, Nov 06, 2012 at 12:12:20PM -0800, Andrew Morton wrote: > On Tue, 6 Nov 2012 00:07:53 -0500 > Naoya Horiguchi wrote: > > > On Mon, Nov 05, 2012 at 02:01:54PM -0800, Andrew Morton wrote: > > > On Fri, 2 Nov 2012 12:33:13 -0400 > > > Naoya Horiguchi wrote: > > > > > > > Printing out the

Re: [PATCH 2/2 v2] mm: print out information of file affected by memory error

2012-11-06 Thread Andrew Morton
On Tue, 6 Nov 2012 00:07:53 -0500 Naoya Horiguchi wrote: > On Mon, Nov 05, 2012 at 02:01:54PM -0800, Andrew Morton wrote: > > On Fri, 2 Nov 2012 12:33:13 -0400 > > Naoya Horiguchi wrote: > > > > > Printing out the information about which file can be affected by a > > > memory error in generic

Re: [PATCH 2/2 v2] mm: print out information of file affected by memory error

2012-11-05 Thread Naoya Horiguchi
On Mon, Nov 05, 2012 at 02:01:54PM -0800, Andrew Morton wrote: > On Fri, 2 Nov 2012 12:33:13 -0400 > Naoya Horiguchi wrote: > > > Printing out the information about which file can be affected by a > > memory error in generic_error_remove_page() is helpful for user to > > estimate the impact of t

Re: [PATCH 2/2 v2] mm: print out information of file affected by memory error

2012-11-05 Thread Andrew Morton
On Fri, 2 Nov 2012 12:33:13 -0400 Naoya Horiguchi wrote: > Printing out the information about which file can be affected by a > memory error in generic_error_remove_page() is helpful for user to > estimate the impact of the error. > > Changelog v2: > - dereference mapping->host after if (!map