From: Jakub Kicinski <kuba@kernel.org>
To: syzkaller-bugs@googlegroups.com, Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+d99d2414db66171fccbb@syzkaller.appspotmail.com>,
asmadeus@codewreck.org, ericvh@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux_oss@crudebyte.com, lucho@ionkov.net,
netdev@vger.kernel.org, v9fs@lists.linux.dev
Subject: Re: [syzbot] [net?] [v9fs?] WARNING: refcount bug in p9_req_put (3)
Date: Fri, 26 Jan 2024 14:23:35 -0800 [thread overview]
Message-ID: <20240126142335.6a01b39f@kernel.org> (raw)
In-Reply-To: <000000000000ee5c6c060fd59890@google.com>
On Fri, 26 Jan 2024 01:05:28 -0800 syzbot wrote:
> HEAD commit: 4fbbed787267 Merge tag 'timers-core-2024-01-21' of git://g..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=11bfbdc7e80000
> kernel config: https://syzkaller.appspot.com/x/.config?x=4059ab9bf06b6ceb
> dashboard link: https://syzkaller.appspot.com/bug?extid=d99d2414db66171fccbb
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: i386
Hi Aleksandr,
we did add a X: net/9p entry to MAINTAINERS back in November [1]
but looks like 9p still gets counted as networking. Is it going
to peter out over time or something's not parsing things right?
[1]
https://lore.kernel.org/all/CANp29Y77rtNrUgQA9HKcB3=bt8FrhbqUSnbZJi3_OGmTpSda6A@mail.gmail.com/
next prev parent reply other threads:[~2024-01-26 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 9:05 [syzbot] [net?] [v9fs?] WARNING: refcount bug in p9_req_put (3) syzbot
2024-01-26 22:23 ` Jakub Kicinski [this message]
2024-01-30 16:41 ` Aleksandr Nogikh
2024-07-22 6:14 ` [syzbot] " 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=20240126142335.6a01b39f@kernel.org \
--to=kuba@kernel.org \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzbot+d99d2414db66171fccbb@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).