From: syzbot <syzbot+e5600587fa9cbf8e3826@syzkaller.appspotmail.com>
To: chao@kernel.org, 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_getxattr
Date: Fri, 18 Aug 2023 14:49:30 -0700 [thread overview]
Message-ID: <000000000000ea8eaa0603398076@google.com> (raw)
In-Reply-To: <ZN/fVHbQA81Zk0Db@google.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+e5600587fa9cbf8e3826@syzkaller.appspotmail.com
Tested on:
commit: 47e4a92b f2fs: avoid false alarm of circular locking
git tree: https://github.com/jaegeuk/f2fs.git g-dev-test
console output: https://syzkaller.appspot.com/x/log.txt?x=16b569efa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6d0f369ef5fb88c9
dashboard link: https://syzkaller.appspot.com/bug?extid=e5600587fa9cbf8e3826
compiler: Debian clang version 15.0.6, 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+e5600587fa9cbf8e3826@syzkaller.appspotmail.com>
To: chao@kernel.org, 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_getxattr
Date: Fri, 18 Aug 2023 14:49:30 -0700 [thread overview]
Message-ID: <000000000000ea8eaa0603398076@google.com> (raw)
In-Reply-To: <ZN/fVHbQA81Zk0Db@google.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+e5600587fa9cbf8e3826@syzkaller.appspotmail.com
Tested on:
commit: 47e4a92b f2fs: avoid false alarm of circular locking
git tree: https://github.com/jaegeuk/f2fs.git g-dev-test
console output: https://syzkaller.appspot.com/x/log.txt?x=16b569efa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6d0f369ef5fb88c9
dashboard link: https://syzkaller.appspot.com/bug?extid=e5600587fa9cbf8e3826
compiler: Debian clang version 15.0.6, 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-18 21:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 4:06 [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_getxattr syzbot
2023-07-07 4:06 ` syzbot
2023-07-10 4:13 ` [f2fs-dev] " syzbot
2023-07-10 4:13 ` syzbot
2023-07-14 15:11 ` [f2fs-dev] " syzbot
2023-07-14 15:11 ` syzbot
2023-08-18 19:51 ` [f2fs-dev] " Jaegeuk Kim
2023-08-18 19:51 ` Jaegeuk Kim
2023-08-18 19:51 ` [f2fs-dev] " syzbot
2023-08-18 19:51 ` syzbot
2023-08-18 20:15 ` [f2fs-dev] " Jaegeuk Kim
2023-08-18 20:15 ` Jaegeuk Kim
2023-08-18 21:02 ` [f2fs-dev] " syzbot
2023-08-18 21:02 ` syzbot
2023-08-18 21:15 ` [f2fs-dev] " Jaegeuk Kim
2023-08-18 21:15 ` Jaegeuk Kim
2023-08-18 21:49 ` syzbot [this message]
2023-08-18 21: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=000000000000ea8eaa0603398076@google.com \
--to=syzbot+e5600587fa9cbf8e3826@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--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.