From: Chen Gong <gong.chen@linux.intel.com>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Wanpeng Li <liwanp@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
Fengguang Wu <fengguang.wu@intel.com>,
Tony Luck <tony.luck@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] mm/hwpoison: fix return value of madvise_hwpoison
Date: Tue, 27 Aug 2013 03:37:01 -0400 [thread overview]
Message-ID: <20130827073701.GA23035@gchen.bj.intel.com> (raw)
In-Reply-To: <1377574896-5k1diwl4-mutt-n-horiguchi@ah.jp.nec.com>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
On Mon, Aug 26, 2013 at 11:41:36PM -0400, Naoya Horiguchi wrote:
> Date: Mon, 26 Aug 2013 23:41:36 -0400
> From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>, Andi Kleen
> <andi@firstfloor.org>, Fengguang Wu <fengguang.wu@intel.com>, Tony Luck
> <tony.luck@intel.com>, gong.chen@linux.intel.com, linux-mm@kvack.org,
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2 3/3] mm/hwpoison: fix return value of
> madvise_hwpoison
> User-Agent: Mutt 1.5.21 (2010-09-15)
>
> On Tue, Aug 27, 2013 at 11:38:27AM +0800, Wanpeng Li wrote:
> > Hi Naoya,
> > On Mon, Aug 26, 2013 at 11:28:16PM -0400, Naoya Horiguchi wrote:
> > >On Tue, Aug 27, 2013 at 10:39:31AM +0800, Wanpeng Li wrote:
> > >> The return value outside for loop is always zero which means madvise_hwpoison
> > >> return success, however, this is not truth for soft_offline_page w/ failure
> > >> return value.
> > >
> > >I don't understand what you want to do for what reason. Could you clarify
> > >those?
> >
> > int ret is defined in two place in madvise_hwpoison. One is out of for
> > loop and its value is always zero(zero means success for madvise), the
> > other one is in for loop. The soft_offline_page function maybe return
> > -EBUSY and break, however, the ret out of for loop is return which means
> > madvise_hwpoison success.
>
> Oh, I see. Thanks.
>
I don't think such change is a good idea. The original code is obviously
easy to confuse people. Why not removing redundant local variable?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-27 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 2:39 [PATCH v2 1/3] mm/hwpoison: fix bug triggered by unpoison empty zero page Wanpeng Li
2013-08-27 2:39 ` [PATCH v2 2/3] mm/hwpoison: change permission of corrupt-pfn/unpoison-pfn to 0200 Wanpeng Li
2013-08-27 2:39 ` [PATCH v2 3/3] mm/hwpoison: fix return value of madvise_hwpoison Wanpeng Li
2013-08-27 3:28 ` Naoya Horiguchi
2013-08-27 3:38 ` Wanpeng Li
2013-08-27 3:38 ` Wanpeng Li
[not found] ` <521c1f3f.813d320a.6ba7.5a17SMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-27 3:41 ` Naoya Horiguchi
2013-08-27 7:37 ` Chen Gong [this message]
2013-08-27 8:02 ` Wanpeng Li
2013-08-27 8:02 ` Wanpeng Li
2013-08-27 8:05 ` Wanpeng Li
2013-08-27 8:07 ` Chen Gong
2013-08-27 8:05 ` Wanpeng Li
[not found] ` <521c5ddd.c9fc440a.2724.ffff8c70SMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-27 21:34 ` Andrew Morton
2013-08-27 3:28 ` [PATCH v2 1/3] mm/hwpoison: fix bug triggered by unpoison empty zero page 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=20130827073701.GA23035@gchen.bj.intel.com \
--to=gong.chen@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--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 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).