From: Andrew Morton <akpm@linux-foundation.org>
To: Oscar Salvador <osalvador@suse.de>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
linux-mm@kvack.org, nao.horiguchi@gmail.com
Subject: Re: [bug report] mm,hwpoison: refactor soft_offline_huge_page and __soft_offline_page
Date: Tue, 25 Aug 2020 17:26:30 -0700 [thread overview]
Message-ID: <20200825172630.f8a7b49f9d44ddbb6430bf58@linux-foundation.org> (raw)
In-Reply-To: <20200825103922.GB18748@linux>
On Tue, 25 Aug 2020 12:39:22 +0200 Oscar Salvador <osalvador@suse.de> wrote:
> On Tue, Aug 25, 2020 at 12:35:17PM +0200, Oscar Salvador wrote:
> > > mm/memory-failure.c
> > > 1749 static bool isolate_page(struct page *page, struct list_head *pagelist)
> > > 1750 {
> > > 1751 bool isolated = false;
> > > 1752 bool lru = PageLRU(page);
> > > 1753
> > > 1754 if (PageHuge(page)) {
> > > 1755 isolated = isolate_huge_page(page, pagelist);
> > > 1756 } else {
> > > 1757 if (lru)
> > > 1758 isolated = !isolate_lru_page(page);
> > > 1759 else
> > > 1760 isolated = !isolate_movable_page(page, ISOLATE_UNEVICTABLE);
> > > 1761
> > > 1762 if (isolated)
> > > 1763 list_add(&page->lru, pagelist);
> > > 1764
> > > 1765 return -EBUSY;
> > >
> > > return false;?
> >
> > No, I this is a mistake, I guess it popped there when Naoya rebased.
> >
> > That return -EBUSY should be go.
> > I'll let Andrew know, thanks.
>
> Unless I'm blind, it seems it wasn't Naoya's mistake either [1]
>
> @Andrew, any idea what happened here? That "return -EBUSY" should not be there.
>
> [1] https://patchwork.kernel.org/patch/11704101/
Yup, thanks. That patchset has required quite a bit of conflict
resolution and I obviously failed to delete that line.
prev parent reply other threads:[~2020-08-26 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 10:25 Dan Carpenter
2020-08-25 10:35 ` Oscar Salvador
2020-08-25 10:39 ` Oscar Salvador
2020-08-26 0:26 ` Andrew Morton [this message]
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=20200825172630.f8a7b49f9d44ddbb6430bf58@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
/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