From: asmadeus@codewreck.org
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: syzbot <syzbot+3c5d43e97993e1fa612b@syzkaller.appspotmail.com>,
cl@linux.com, ericvh@kernel.org, linux-kernel@vger.kernel.org,
linux_oss@crudebyte.com, lucho@ionkov.net,
syzkaller-bugs@googlegroups.com, v9fs@lists.linux.dev,
vbabka@suse.cz
Subject: Re: [syzbot] [v9fs?] WARNING in p9_client_create (2)
Date: Mon, 23 Sep 2024 01:40:55 +0900 [thread overview]
Message-ID: <ZvBIl8b9RRK9jgtJ@codewreck.org> (raw)
In-Reply-To: <CAKbZUD08BQeK0R-KuU07=QUCW7GHbmZ0RgfUcOpzKd+Yv4b5CQ@mail.gmail.com>
Pedro Falcato wrote on Sun, Sep 22, 2024 at 03:59:17PM +0100:
> This was one of the issues I actually ran into when using virtme.
> Fix was submitted here back in August:
> https://lore.kernel.org/v9fs/20240807094725.2193423-1-pedro.falcato@gmail.com/
>
> No replies nor was it picked up. Can it go through the slab tree?
Sorry, we're not getting many patches for 9p so I've been slacking and
trying to batch a bit for when I can find time to pick them up -- don't
hesitate to ping again if nobody replied in a week or two.
In this particular case I remember thinking it was a shame we're
creating a cache for this when most mounts will be sharing the same
msize but never found time to actually consider how to share the
caches... But this isn't anything wrong with the patch itself, sorry for
the delay.
(and now I'm thinking about it, I guess the slab code has something to
regroup identical caches? Just looked and didn't find it but I recall
something like that...)
Anyway, I've just picked that patch up (don't expect any trouble but
will be queued to next later today), I'll send it to Linus in a week.
(I'm also adding the syzbot reported by so this gets closed even if it
came later)
Thanks!
--
Dominique Martinet | Asmadeus
next prev parent reply other threads:[~2024-09-22 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 12:10 [syzbot] [v9fs?] WARNING in p9_client_create (2) syzbot
2024-09-22 14:59 ` Pedro Falcato
2024-09-22 16:40 ` asmadeus [this message]
2024-09-26 14:55 ` Vlastimil Babka
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=ZvBIl8b9RRK9jgtJ@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=cl@linux.com \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=pedro.falcato@gmail.com \
--cc=syzbot+3c5d43e97993e1fa612b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs@lists.linux.dev \
--cc=vbabka@suse.cz \
/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