From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: v9fs-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [GIT PULL] 9p updates for 5.3
Date: Fri, 12 Jul 2019 10:04:46 +0200 [thread overview]
Message-ID: <20190712080446.GA19400@nautica> (raw)
Hi Linus,
Here is a 9p update for 5.3, just a couple of fixes that have been
sitting here for too long as I missed the 5.2 merge window.
I have two more patches that I didn't have time to test early enough for
this but also are plain details fix, please let me know if you would
prefer having me send a pull request for -rc2 after a week in -next or
if I should just wait until the next window.
There's little risk but I'm usually rather conservative on this.
The following changes since commit 5908e6b738e3357af42c10e1183753c70a0117a9:
Linux 5.0-rc8 (2019-02-24 16:46:45 -0800)
are available in the git repository at:
git://github.com/martinetd/linux tags/9p-for-5.3
for you to fetch changes up to 80a316ff16276b36d0392a8f8b2f63259857ae98:
9p/xen: Add cleanup path in p9_trans_xen_init (2019-05-15 13:00:07
+0000)
----------------------------------------------------------------
9p pull request for inclusion in 5.13
Two small fixes to properly cleanup the 9p transports list if virtio/xen
module initialization fail.
9p might otherwise try to access memory from a module that failed to
register got freed.
----------------------------------------------------------------
YueHaibing (2):
9p/virtio: Add cleanup path in p9_virtio_init
9p/xen: Add cleanup path in p9_trans_xen_init
net/9p/trans_virtio.c | 8 +++++++-
net/9p/trans_xen.c | 8 +++++++-
2 files changed, 14 insertions(+), 2 deletions(-)
next reply other threads:[~2019-07-12 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 8:04 Dominique Martinet [this message]
2019-07-13 0:40 ` [GIT PULL] 9p updates for 5.3 pr-tracker-bot
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=20190712080446.GA19400@nautica \
--to=asmadeus@codewreck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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).