From: "David Hildenbrand (Arm)" <david@kernel.org>
To: syzbot <syzbot+8edc46c9c781c802acf4@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, jgg@ziepe.ca, jhubbard@nvidia.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
netdev@vger.kernel.org, peterx@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] possible deadlock in gup_fast_fallback (3)
Date: Wed, 13 May 2026 13:44:58 +0200 [thread overview]
Message-ID: <1ddf6f68-4aff-4475-aa82-c2bf15c9706c@kernel.org> (raw)
In-Reply-To: <6a0321a3.050a0220.106bf4.0005.GAE@google.com>
On 5/12/26 14:48, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 63751099502d Merge branch 'net-mlx5-steering-misc-enhancem..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1714fbce580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=f2b487b72ffad035
> dashboard link: https://syzkaller.appspot.com/bug?extid=8edc46c9c781c802acf4
> compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/1f8de738e2f8/disk-63751099.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/ae6cfb0d3b70/vmlinux-63751099.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/f00e218e1a55/bzImage-63751099.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+8edc46c9c781c802acf4@syzkaller.appspotmail.com
>
> ======================================================
> WARNING: possible circular locking dependency detected
> syzkaller #0 Not tainted
> ------------------------------------------------------
> syz.4.2801/16593 is trying to acquire lock:
> ffff88802ae527f8 (&mm->mmap_lock){++++}-{4:4}, at: gup_fast_fallback+0x20d/0x20d0 mm/gup.c:3193
>
> but task is already holding lock:
> ffff888055ac9d60 (sk_lock-AF_INET6){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1713 [inline]
> ffff888055ac9d60 (sk_lock-AF_INET6){+.+.}-{0:0}, at: tls_sw_sendmsg+0x15d/0x2430 net/tls/tls_sw.c:1291
>
> which lock already depends on the new lock.
I don't know what going on here, but I know for sure that GUP is not to blame ;)
--
Cheers,
David
parent reply other threads:[~2026-05-13 11:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6a0321a3.050a0220.106bf4.0005.GAE@google.com>]
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=1ddf6f68-4aff-4475-aa82-c2bf15c9706c@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=syzbot+8edc46c9c781c802acf4@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