From: Matthew Wilcox <willy@infradead.org>
To: syzbot <syzbot+c915885f05d8e432e7b4@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, dhowells@redhat.com, hughd@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in split_huge_page_to_list
Date: Wed, 15 Dec 2021 04:19:03 +0000 [thread overview]
Message-ID: <Yblst9nyDSH2RQWQ@casper.infradead.org> (raw)
In-Reply-To: <00000000000091a18b05d324df40@google.com>
On Tue, Dec 14, 2021 at 05:03:26PM -0800, syzbot wrote:
> commit 3ebffc96befbaf9de9297b00d67091bb702fad8e
> Author: Matthew Wilcox (Oracle) <willy@infradead.org>
> Date: Sun Jun 28 02:19:08 2020 +0000
>
> mm: Use multi-index entries in the page cache
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1276e4bab00000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=1176e4bab00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1676e4bab00000
Well, this is all entirely plausible:
+ xas_split_alloc(&xas, head, compound_order(head),
+ mapping_gfp_mask(mapping) & GFP_RECLAIM_MASK);
It looks like I can fix this by moving the memory allocation before
the acquisition of the i_mmap_lock. Any objections to this:
+++ b/mm/huge_memory.c
@@ -2653,6 +2653,13 @@ int split_huge_page_to_list(struct page *page, struct lis
t_head *list)
goto out;
}
+ xas_split_alloc(&xas, head, compound_order(head),
+ mapping_gfp_mask(mapping) & GFP_RECLAIM_MASK);
+ if (xas_error(&xas)) {
+ ret = xas_error(&xas);
+ goto out;
+ }
+
anon_vma = NULL;
i_mmap_lock_read(mapping);
@@ -2679,15 +2686,6 @@ int split_huge_page_to_list(struct page *page, struct list_head *list)
unmap_page(head);
- if (mapping) {
- xas_split_alloc(&xas, head, compound_order(head),
- mapping_gfp_mask(mapping) & GFP_RECLAIM_MASK);
- if (xas_error(&xas)) {
- ret = xas_error(&xas);
- goto out_unlock;
- }
- }
-
/* block interrupt reentry in xa_lock and spinlock */
local_irq_disable();
if (mapping) {
(relative to the above patch)
prev parent reply other threads:[~2021-12-15 4:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 1:03 syzbot
2021-12-15 4:19 ` Matthew Wilcox [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=Yblst9nyDSH2RQWQ@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+c915885f05d8e432e7b4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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