From: syzbot <syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com>
To: ardb@kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context
Date: Thu, 22 May 2025 07:50:02 -0700 [thread overview]
Message-ID: <682f399a.a70a0220.253bc2.0058.GAE@google.com> (raw)
In-Reply-To: <CAMj1kXEn_fx6=X4ixhmWST1scUH4kY0SXBt1sXT=-5_ctcKGoA@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
unregister_netdevice: waiting for DEV to become free
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
Tested on:
commit: 1afe9e7d f2fs: fix freezing filesystem during resize
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs-6.16.super
console output: https://syzkaller.appspot.com/x/log.txt?x=102105f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bcb473848aa62842
dashboard link: https://syzkaller.appspot.com/bug?extid=52cd651546d11d2af06b
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
userspace arch: arm64
Note: no patches were applied.
next parent reply other threads:[~2025-05-22 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMj1kXEn_fx6=X4ixhmWST1scUH4kY0SXBt1sXT=-5_ctcKGoA@mail.gmail.com>
2025-05-22 14:50 ` syzbot [this message]
[not found] <CAMj1kXEUW2arc4E1z5VkqUm6yi_bPyPwUtvg99PpM4bQLpct5w@mail.gmail.com>
2025-05-22 14:17 ` [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context syzbot
[not found] <20250513204140.1987-1-hdanton@sina.com>
2025-05-14 1:13 ` syzbot
[not found] <20250512103556.1921-1-hdanton@sina.com>
2025-05-12 12:16 ` syzbot
2025-05-11 17:44 syzbot
2025-05-21 17:28 ` Ard Biesheuvel
2025-05-22 12:24 ` Christian Brauner
2025-05-22 13:47 ` Ard Biesheuvel
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=682f399a.a70a0220.253bc2.0058.GAE@google.com \
--to=syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com \
--cc=ardb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.