From: syzbot <syzbot+edec7868af5997928fe9@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, davem@davemloft.net, ericvh@gmail.com,
hch@lst.de, kuba@kernel.org, linux-kernel@vger.kernel.org,
lucho@ionkov.net, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
v9fs-developer@lists.sourceforge.net
Subject: Re: WARNING: refcount bug in p9_req_put
Date: Fri, 14 Aug 2020 22:23:08 -0700 [thread overview]
Message-ID: <00000000000098e02c05ace3bbfb@google.com> (raw)
In-Reply-To: <000000000000eb6a8e057ab79f82@google.com>
syzbot suspects this issue was fixed by commit:
commit a39c46067c845a8a2d7144836e9468b7f072343e
Author: Christoph Hellwig <hch@lst.de>
Date: Fri Jul 10 08:57:22 2020 +0000
net/9p: validate fds in p9_fd_open
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1015f012900000
start commit: 459e3a21 gcc-9: properly declare the {pv,hv}clock_page sto..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ef1b87b455c397cf
dashboard link: https://syzkaller.appspot.com/bug?extid=edec7868af5997928fe9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1642ee48a00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net/9p: validate fds in p9_fd_open
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-08-15 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 17:46 WARNING: refcount bug in p9_req_put syzbot
2018-11-17 8:55 ` Dominique Martinet
2019-05-02 2:38 ` syzbot
2020-08-15 5:23 ` syzbot [this message]
2020-11-11 13:54 ` Dmitry Vyukov
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=00000000000098e02c05ace3bbfb@google.com \
--to=syzbot+edec7868af5997928fe9@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=hch@lst.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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.