linux-kernel - Re: [RFC Patch 0/2] mm: Add parameters to make kernel behavior at memory error on dirty cache selectable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1366207098-f00491sj-mutt-n-horiguchi@ah.jp.nec.com>
Date:	Wed, 17 Apr 2013 09:58:18 -0400
From:	Naoya Horiguchi <n-horiguchi@...jp.nec.com>
To:	Mitsuhiro Tanino <mitsuhiro.tanino.gm@...achi.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>
Subject: Re: [RFC Patch 0/2] mm: Add parameters to make kernel behavior at
 memory error on dirty cache selectable

On Fri, Apr 12, 2013 at 11:13:03AM -0400, Naoya Horiguchi wrote:
...
> > So my proposal is as follows,
> >   For short term solution to care both memory error and I/O error:
> >     - I will resend a panic knob to handle data lost related to dirty cache
> >       which is caused by memory error and I/O error.
> 
> Sorry, I still think "panic on dirty pagecache error" is feasible in userspace.
> This new knob will be completely useless after memory error reporting is
> fixed in the future, so whenever possible I like the userspace solution
> even for a short term one.

My apology, you mentioned both memory error and I/O error.
So I guess that in your next post, a new sysctl knob will be implemented
around filemap_fdatawait_range() to make kernel panic immediately
if a process finds the AS_EIO set.
It's also effective for the processes which poorly handle EIO, so can
be useful even after the error reporting is fixed in the future.

Anyway, my previous comment is pointless, so ignore it.

Thanks,
Naoya Horiguchi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/