From: Dominique Martinet <asmadeus@codewreck.org>
To: Tomas Bortoli <tomasbortoli@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
David Miller <davem@davemloft.net>,
v9fs-developer@lists.sourceforge.net,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: [PATCH] 9p: fix NULL pointer dereferences
Date: Thu, 26 Jul 2018 16:21:09 +0200 [thread overview]
Message-ID: <20180726142109.GA4235@nautica> (raw)
In-Reply-To: <abbeafa2-9008-5749-aee5-b4a115d71af7@gmail.com>
Tomas Bortoli wrote on Thu, Jul 26, 2018:
>> But I think trans=fd allows NULL addr today, no?
>
> How ?
Just using the mount syscall with a NULL dev_name? I haven't checked
this syzcaller reproducer but it's probably what it does.
p9_fd_create doesn't use 'addr' at all so it's safe to create a 9p mount
for trans=fd with no device name, as Dmitry pointed out
> > On the other hand, virtio, rdma and xen all have the same problem, so
> > Thomas, please fix them instead :)
>
> So just by patching v9fs_mount ?
If we want to preserve the current behaviour for trans=fd (and I don't
see why not) we just have to patch all the transports that use the
device, that is all .create functions but p9_fd_create()
Basically exactly what you did, just for a few more functions - I
apparently was a little bit too optimistic thinking we could share
this check.
--
Dominique
next prev parent reply other threads:[~2018-07-26 14:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 8:10 [PATCH] 9p: fix NULL pointer dereferences Tomas Bortoli
2018-07-26 8:17 ` Dominique Martinet
2018-07-26 9:27 ` Dmitry Vyukov
2018-07-26 9:48 ` Dominique Martinet
2018-07-26 9:54 ` Dmitry Vyukov
2018-07-26 10:25 ` Dominique Martinet
2018-07-26 14:13 ` Tomas Bortoli
2018-07-26 14:21 ` Dominique Martinet [this message]
2018-07-26 14:32 ` Tomas Bortoli
2018-07-26 22:15 ` Dominique Martinet
2018-08-08 15:51 ` Dmitry Vyukov
2018-08-08 22:41 ` Dominique Martinet
2018-07-26 14:48 ` [V9fs-developer] " sqweek
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=20180726142109.GA4235@nautica \
--to=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=tomasbortoli@gmail.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 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).