From: Dan Carpenter <dan.carpenter@oracle.com>
To: osalvador@suse.de
Cc: linux-mm@kvack.org
Subject: [bug report] mm,hwpoison: refactor soft_offline_huge_page and __soft_offline_page
Date: Tue, 25 Aug 2020 13:25:46 +0300 [thread overview]
Message-ID: <20200825102546.GA272697@mwanda> (raw)
Hello Oscar Salvador,
The patch e5bcf91e5cc6: "mm,hwpoison: refactor soft_offline_huge_page
and __soft_offline_page" from Aug 20, 2020, leads to the following
static checker warning:
mm/memory-failure.c:1765 isolate_page()
warn: signedness bug returning '(-16)'
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;?
1766 }
1767
1768 if (isolated && lru)
1769 inc_node_page_state(page, NR_ISOLATED_ANON +
1770 page_is_file_lru(page));
1771
1772 /*
1773 * If we succeed to isolate the page, we grabbed another refcount on
1774 * the page, so we can safely drop the one we got from get_any_pages().
1775 * If we failed to isolate the page, it means that we cannot go further
1776 * and we will return an error, so drop the reference we got from
1777 * get_any_pages() as well.
1778 */
1779 put_page(page);
1780 return isolated;
1781 }
regards,
dan carpenter
next reply other threads:[~2020-08-25 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 10:25 Dan Carpenter [this message]
2020-08-25 10:35 ` [bug report] mm,hwpoison: refactor soft_offline_huge_page and __soft_offline_page Oscar Salvador
2020-08-25 10:39 ` Oscar Salvador
2020-08-26 0:26 ` Andrew Morton
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=20200825102546.GA272697@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-mm@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).