From: Dominique Martinet <asmadeus@codewreck.org>
To: YueHaibing <yuehaibing@huawei.com>
Cc: davem@davemloft.net, ericvh@gmail.com, lucho@ionkov.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Subject: Re: [PATCH] 9p/virtio: Add cleanup path in p9_virtio_init
Date: Tue, 30 Apr 2019 16:09:07 +0200 [thread overview]
Message-ID: <20190430140907.GA19422@nautica> (raw)
In-Reply-To: <20190430115942.41840-1-yuehaibing@huawei.com>
YueHaibing wrote on Tue, Apr 30, 2019:
> KASAN report this:
That's not KASAN, but fair enough - fix looks good. I'll queue this for
5.2 unless you absolutely want this in 5.1
If you're feeling nice p9_trans_xen_init has the exact same problem and
could use the same fix :)
--
Dominique
next prev parent reply other threads:[~2019-04-30 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 11:59 [PATCH] 9p/virtio: Add cleanup path in p9_virtio_init YueHaibing
2019-04-30 14:09 ` Dominique Martinet [this message]
2019-04-30 14:28 ` YueHaibing
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=20190430140907.GA19422@nautica \
--to=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=yuehaibing@huawei.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 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).