From: syzbot <syzbot+eb6201248f684e99b9f8@syzkaller.appspotmail.com>
To: chao@kernel.org, hdanton@sina.com, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
nogikh@google.com, 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, 14 Sep 2023 22:49:27 -0700 [thread overview]
Message-ID: <000000000000045d4d06055f5bff@google.com> (raw)
In-Reply-To: <0000000000000534da05faa4d3d4@google.com>
syzbot suspects this issue was fixed by commit:
commit 5079e1c0c879311668b77075de3e701869804adf
Author: Chao Yu <chao@kernel.org>
Date: Fri Jun 2 08:36:05 2023 +0000
f2fs: avoid dead loop in f2fs_issue_checkpoint()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15aae552680000
start commit: c8c655c34e33 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=5eadbf0d3c2ece89
dashboard link: https://syzkaller.appspot.com/bug?extid=eb6201248f684e99b9f8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13130a1c280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d919f8280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: f2fs: avoid dead loop in f2fs_issue_checkpoint()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
_______________________________________________
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, hdanton@sina.com, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
nogikh@google.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_write_single_data_page
Date: Thu, 14 Sep 2023 22:49:27 -0700 [thread overview]
Message-ID: <000000000000045d4d06055f5bff@google.com> (raw)
In-Reply-To: <0000000000000534da05faa4d3d4@google.com>
syzbot suspects this issue was fixed by commit:
commit 5079e1c0c879311668b77075de3e701869804adf
Author: Chao Yu <chao@kernel.org>
Date: Fri Jun 2 08:36:05 2023 +0000
f2fs: avoid dead loop in f2fs_issue_checkpoint()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15aae552680000
start commit: c8c655c34e33 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=5eadbf0d3c2ece89
dashboard link: https://syzkaller.appspot.com/bug?extid=eb6201248f684e99b9f8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13130a1c280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d919f8280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: f2fs: avoid dead loop in f2fs_issue_checkpoint()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-15 5:55 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 ` [f2fs-dev] " syzbot
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 ` syzbot [this message]
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=000000000000045d4d06055f5bff@google.com \
--to=syzbot+eb6201248f684e99b9f8@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=hdanton@sina.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--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.