From: syzbot <syzbot+eb6201248f684e99b9f8@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_write_single_data_page
Date: Thu, 04 May 2023 06:31:21 -0700 [thread overview]
Message-ID: <00000000000032909d05fade30c8@google.com> (raw)
In-Reply-To: <fb9b6de8-1efc-eeea-7acb-09d291590576@kernel.org>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
no output from test machine
Tested on:
commit: 2adb872d f2fs: fix potential deadlock due to unpaired ..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git dev-test
console output: https://syzkaller.appspot.com/x/log.txt?x=114b5338280000
kernel config: https://syzkaller.appspot.com/x/.config?x=86e4eb913e90d4b2
dashboard link: https://syzkaller.appspot.com/bug?extid=eb6201248f684e99b9f8
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Note: no patches were applied.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+eb6201248f684e99b9f8@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_write_single_data_page
Date: Thu, 04 May 2023 06:31:21 -0700 [thread overview]
Message-ID: <00000000000032909d05fade30c8@google.com> (raw)
In-Reply-To: <fb9b6de8-1efc-eeea-7acb-09d291590576@kernel.org>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
no output from test machine
Tested on:
commit: 2adb872d f2fs: fix potential deadlock due to unpaired ..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git dev-test
console output: https://syzkaller.appspot.com/x/log.txt?x=114b5338280000
kernel config: https://syzkaller.appspot.com/x/.config?x=86e4eb913e90d4b2
dashboard link: https://syzkaller.appspot.com/bug?extid=eb6201248f684e99b9f8
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Note: no patches were applied.
next prev parent reply other threads:[~2023-05-04 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 17:05 [f2fs-dev] [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_write_single_data_page syzbot
2023-05-01 17:05 ` syzbot
2023-05-03 15:28 ` [f2fs-dev] " Chao Yu
2023-05-03 15:28 ` Chao Yu
2023-05-03 16:08 ` [f2fs-dev] " syzbot
2023-05-03 16:08 ` syzbot
2023-05-04 12:08 ` [f2fs-dev] " Chao Yu
2023-05-04 12:08 ` Chao Yu
2023-05-04 13:31 ` syzbot [this message]
2023-05-04 13:31 ` syzbot
2023-05-04 13:48 ` [f2fs-dev] " Chao Yu
2023-05-04 13:48 ` Chao Yu
2023-05-04 13:53 ` [f2fs-dev] " Aleksandr Nogikh via Linux-f2fs-devel
2023-05-04 13:53 ` Aleksandr Nogikh
2023-09-15 5:49 ` [f2fs-dev] " syzbot
2023-09-15 5:49 ` syzbot
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=00000000000032909d05fade30c8@google.com \
--to=syzbot+eb6201248f684e99b9f8@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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.