From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+a3e82ae343b26b4d2335@syzkaller.appspotmail.com>
Cc: aleksandr.mikhalitsyn@canonical.com, brauner@kernel.org,
jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [mm?] BUG: sleeping function called from invalid context in vma_alloc_folio_noprof
Date: Mon, 15 Jul 2024 20:51:40 -0700 [thread overview]
Message-ID: <20240715205140.c260410215836e753a44b5e9@linux-foundation.org> (raw)
In-Reply-To: <00000000000069b4ee061d5334e4@google.com>
On Mon, 15 Jul 2024 18:24:19 -0700 syzbot <syzbot+a3e82ae343b26b4d2335@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 3fe121b62282 Add linux-next specific files for 20240712
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=12ba9149980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=98dd8c4bab5cdce
> dashboard link: https://syzkaller.appspot.com/bug?extid=a3e82ae343b26b4d2335
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144c4b66980000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=163c28f6980000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/8c6fbf69718d/disk-3fe121b6.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/39fc7e43dfc1/vmlinux-3fe121b6.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/0a78e70e4b4e/bzImage-3fe121b6.xz
>
> The issue was bisected to:
>
> commit ca567df74a28a9fb368c6b2d93e864113f73f5c2
> Author: Christian Brauner <brauner@kernel.org>
> Date: Sun Jun 7 20:47:08 2020 +0000
>
> nsfs: add pid translation ioctls
>
yup, thanks. Breaking out of the switch statement while holding
rcu_read_lock().
next prev parent reply other threads:[~2024-07-16 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 1:24 syzbot
2024-07-16 3:51 ` Andrew Morton [this message]
2024-07-16 7:19 ` [PATCH] nsfs: use cleanup guard Christian Brauner
2024-07-16 7:28 ` Christian Brauner
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=20240715205140.c260410215836e753a44b5e9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+a3e82ae343b26b4d2335@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®