All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Andi Kleen <andi.kleen@intel.com>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tony Luck <tony.luck@intel.com>, Rik van Riel <riel@redhat.com>,
	Jun'ichi Nomura <j-nomura@ce.jp.nec.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3 v2] HWPOISON: improve dirty pagecache error reporting
Date: Wed, 22 Aug 2012 13:22:36 -0700	[thread overview]
Message-ID: <m2obm27k37.fsf@firstfloor.org> (raw)
In-Reply-To: <1345648655-4497-1-git-send-email-n-horiguchi@ah.jp.nec.com> (Naoya Horiguchi's message of "Wed, 22 Aug 2012 11:17:32 -0400")

Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> writes:

> Hi,
>
> Based on the previous discussion, in this version I propose only error
> reporting fix ("overwrite recovery" is sparated out from this series.)
>
> I think Fengguang's patch (patch 2 in this series) has a corner case
> about inode cache drop, so I added patch 3 for it.

New patchkit looks very reasonable to me.

I haven't gone through all the corner cases the inode pinning may
have though. You probably want an review from Al Viro on this.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

--
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: Andi Kleen <andi@firstfloor.org>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Andi Kleen <andi.kleen@intel.com>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tony Luck <tony.luck@intel.com>, Rik van Riel <riel@redhat.com>,
	"Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3 v2] HWPOISON: improve dirty pagecache error reporting
Date: Wed, 22 Aug 2012 13:22:36 -0700	[thread overview]
Message-ID: <m2obm27k37.fsf@firstfloor.org> (raw)
In-Reply-To: <1345648655-4497-1-git-send-email-n-horiguchi@ah.jp.nec.com> (Naoya Horiguchi's message of "Wed, 22 Aug 2012 11:17:32 -0400")

Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> writes:

> Hi,
>
> Based on the previous discussion, in this version I propose only error
> reporting fix ("overwrite recovery" is sparated out from this series.)
>
> I think Fengguang's patch (patch 2 in this series) has a corner case
> about inode cache drop, so I added patch 3 for it.

New patchkit looks very reasonable to me.

I haven't gone through all the corner cases the inode pinning may
have though. You probably want an review from Al Viro on this.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

  parent reply	other threads:[~2012-08-22 20:22 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 15:17 [PATCH 0/3 v2] HWPOISON: improve dirty pagecache error reporting Naoya Horiguchi
2012-08-22 15:17 ` Naoya Horiguchi
2012-08-22 15:17 ` [PATCH 1/3] HWPOISON: fix action_result() to print out dirty/clean Naoya Horiguchi
2012-08-22 15:17   ` Naoya Horiguchi
2012-08-23  9:33   ` Fengguang Wu
2012-08-23  9:33     ` Fengguang Wu
2012-08-23 20:31     ` Naoya Horiguchi
2012-08-23 20:31       ` Naoya Horiguchi
2012-08-22 15:17 ` [PATCH 2/3] HWPOISON: report sticky EIO for poisoned file Naoya Horiguchi
2012-08-22 15:17   ` Naoya Horiguchi
2012-08-23  9:22   ` Fengguang Wu
2012-08-23  9:22     ` Fengguang Wu
2012-08-23 20:31     ` Naoya Horiguchi
2012-08-23 20:31       ` Naoya Horiguchi
2012-08-22 15:17 ` [PATCH 3/3] HWPOISON: prevent inode cache removal to keep AS_HWPOISON sticky Naoya Horiguchi
2012-08-22 15:17   ` Naoya Horiguchi
2012-08-23  9:11   ` Fengguang Wu
2012-08-23  9:11     ` Fengguang Wu
2012-08-23 20:31     ` Naoya Horiguchi
2012-08-23 20:31       ` Naoya Horiguchi
2012-08-24 21:52       ` Naoya Horiguchi
2012-08-24 21:52         ` Naoya Horiguchi
2012-08-24  1:31   ` Dave Chinner
2012-08-24  1:31     ` Dave Chinner
2012-08-24  2:39     ` Naoya Horiguchi
2012-08-24  2:39       ` Naoya Horiguchi
2012-08-24  4:39       ` Dave Chinner
2012-08-24  4:39         ` Dave Chinner
2012-08-24 17:24         ` Naoya Horiguchi
2012-08-24 17:24           ` Naoya Horiguchi
2012-08-26 22:26           ` Dave Chinner
2012-08-26 22:26             ` Dave Chinner
2012-08-27 22:05             ` Naoya Horiguchi
2012-08-27 22:05               ` Naoya Horiguchi
2012-08-29  2:59               ` Dave Chinner
2012-08-29  2:59                 ` Dave Chinner
2012-08-29  5:32                 ` Jun'ichi Nomura
2012-08-29  5:32                   ` Jun'ichi Nomura
2012-09-03  0:39                   ` Dave Chinner
2012-09-03  0:39                     ` Dave Chinner
2012-08-22 20:22 ` Andi Kleen [this message]
2012-08-22 20:22   ` [PATCH 0/3 v2] HWPOISON: improve dirty pagecache error reporting Andi Kleen
2012-08-22 21:14   ` Naoya Horiguchi
2012-08-22 21:14     ` Naoya Horiguchi

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=m2obm27k37.fsf@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi.kleen@intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=j-nomura@ce.jp.nec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=riel@redhat.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.