From: syzbot <syzbot+733300ca0a9baca7e245@syzkaller.appspotmail.com>
To: djahchankoike@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_ioc_start_atomic_write
Date: Wed, 14 Aug 2024 13:23:02 -0700 [thread overview]
Message-ID: <000000000000345776061faa7edd@google.com> (raw)
In-Reply-To: <20240814185918.93407-1-djahchankoike@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+733300ca0a9baca7e245@syzkaller.appspotmail.com
Tested-by: syzbot+733300ca0a9baca7e245@syzkaller.appspotmail.com
Tested on:
commit: 320eb81d Add linux-next specific files for 20240814
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10d4f2a3980000
kernel config: https://syzkaller.appspot.com/x/.config?x=61ba6f3b22ee5467
dashboard link: https://syzkaller.appspot.com/bug?extid=733300ca0a9baca7e245
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=13821a05980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-08-14 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240814185918.93407-1-djahchankoike@gmail.com>
2024-08-14 20:23 ` syzbot [this message]
2024-08-14 13:36 [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_commit_atomic_write Edward Adam Davis
2024-08-14 20:27 ` [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_ioc_start_atomic_write syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-08-14 11:51 syzbot
2024-09-05 1:29 ` Chao Yu
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=000000000000345776061faa7edd@google.com \
--to=syzbot+733300ca0a9baca7e245@syzkaller.appspotmail.com \
--cc=djahchankoike@gmail.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