From: syzbot <syzbot+78ff2855f26377625419@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_commit_atomic_write
Date: Tue, 13 Aug 2024 20:58:05 -0700 [thread overview]
Message-ID: <000000000000bb32a9061f9cbb46@google.com> (raw)
In-Reply-To: <tencent_001B304B341B3D2501BAB0BB2733509E6A08@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+78ff2855f26377625419@syzkaller.appspotmail.com
Tested-by: syzbot+78ff2855f26377625419@syzkaller.appspotmail.com
Tested on:
commit: 9e686969 Add linux-next specific files for 20240812
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=126f95c5980000
kernel config: https://syzkaller.appspot.com/x/.config?x=61ba6f3b22ee5467
dashboard link: https://syzkaller.appspot.com/bug?extid=78ff2855f26377625419
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1279c9ed980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-08-14 3:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 20:49 [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_commit_atomic_write syzbot
2024-08-14 0:48 ` Edward Adam Davis
2024-08-14 3:21 ` syzbot
2024-08-14 3:33 ` Chao Yu
2024-08-14 6:01 ` Edward Adam Davis
2024-08-14 1:01 ` Edward Adam Davis
2024-08-14 3:58 ` syzbot [this message]
2024-09-05 1:31 ` [f2fs-dev] " Chao Yu
-- strict thread matches above, loose matches on Subject: below --
2024-08-14 11:51 [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_ioc_start_atomic_write syzbot
2024-08-14 13:36 ` [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_commit_atomic_write Edward Adam Davis
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=000000000000bb32a9061f9cbb46@google.com \
--to=syzbot+78ff2855f26377625419@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox