From: syzbot <syzbot+a4976ce949df66b1ddf1@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,
syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry
Date: Thu, 24 Aug 2023 18:47:30 -0700 [thread overview]
Message-ID: <0000000000001ba17a0603b5871e@google.com> (raw)
In-Reply-To: <8680b259-528b-32a9-73ee-ce6a6406f13d@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+a4976ce949df66b1ddf1@syzkaller.appspotmail.com
Tested on:
commit: 5c13e238 f2fs: avoid false alarm of circular locking
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev
console output: https://syzkaller.appspot.com/x/log.txt?x=121bdfcfa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=5ff9844b1e911216
dashboard link: https://syzkaller.appspot.com/bug?extid=a4976ce949df66b1ddf1
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
_______________________________________________
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+a4976ce949df66b1ddf1@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,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry
Date: Thu, 24 Aug 2023 18:47:30 -0700 [thread overview]
Message-ID: <0000000000001ba17a0603b5871e@google.com> (raw)
In-Reply-To: <8680b259-528b-32a9-73ee-ce6a6406f13d@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+a4976ce949df66b1ddf1@syzkaller.appspotmail.com
Tested on:
commit: 5c13e238 f2fs: avoid false alarm of circular locking
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev
console output: https://syzkaller.appspot.com/x/log.txt?x=121bdfcfa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=5ff9844b1e911216
dashboard link: https://syzkaller.appspot.com/bug?extid=a4976ce949df66b1ddf1
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2023-08-25 1:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 3:55 [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry syzbot
2023-07-07 3:55 ` syzbot
2023-08-24 15:55 ` [f2fs-dev] " syzbot
2023-08-24 15:55 ` syzbot
2023-08-25 1:08 ` [f2fs-dev] " Chao Yu
2023-08-25 1:08 ` Chao Yu
2023-08-25 1:47 ` syzbot [this message]
2023-08-25 1:47 ` syzbot
2023-08-25 5:37 ` [f2fs-dev] [PATCH] f2fs: fix deadlock in f2f2_add_dentry Lizhi Xu via Linux-f2fs-devel
2023-08-25 5:37 ` Lizhi Xu
2023-08-25 10:41 ` [f2fs-dev] " Chao Yu
2023-08-25 10:41 ` Chao Yu
2023-08-26 2:58 ` [f2fs-dev] " Lizhi Xu via Linux-f2fs-devel
2023-08-26 2:58 ` Lizhi Xu
2023-09-06 12:56 ` Tetsuo Handa
2023-09-06 12:56 ` Tetsuo Handa
2023-10-26 6:59 ` [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry syzbot
2023-10-26 6:59 ` syzbot
2023-10-26 9:21 ` [f2fs-dev] " Aleksandr Nogikh via Linux-f2fs-devel
2023-10-26 9:21 ` Aleksandr Nogikh
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=0000000000001ba17a0603b5871e@google.com \
--to=syzbot+a4976ce949df66b1ddf1@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=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.