From: syzbot <syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in mnt_want_write (2)
Date: Sun, 03 Jul 2022 00:40:07 -0700 [thread overview]
Message-ID: <00000000000077dcfd05e2e1baab@google.com> (raw)
In-Reply-To: <20220703070714.1237-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com
Tested on:
commit: 08986606 Merge tag 'libnvdimm-fixes-5.19-rc5' of git:/..
git tree: http://kernel.source.codeaurora.cn/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1479f7fff00000
kernel config: https://syzkaller.appspot.com/x/.config?x=75c9ff14e1db87c0
dashboard link: https://syzkaller.appspot.com/bug?extid=b42fe626038981fb7bfa
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=11e05fd4080000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-07-03 7:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220703070714.1237-1-hdanton@sina.com>
2022-07-03 7:40 ` syzbot [this message]
[not found] <20220703013354.1025-1-hdanton@sina.com>
2022-07-03 6:42 ` [syzbot] possible deadlock in mnt_want_write (2) syzbot
2021-06-15 16:59 syzbot
2021-07-19 15:11 ` Miklos Szeredi
2021-07-22 13:50 ` Mimi Zohar
2022-07-02 17:27 ` syzbot
2022-07-05 12:53 ` Mimi Zohar
2022-07-06 12:10 ` Hillf Danton
2022-07-06 22:24 ` Mimi Zohar
2023-06-06 9:12 ` Miklos Szeredi
2023-06-06 9:12 ` syzbot
2023-06-06 9:13 ` Miklos Szeredi
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=00000000000077dcfd05e2e1baab@google.com \
--to=syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com \
--cc=hdanton@sina.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 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.