From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [git pull] a couple of fixes
Date: Wed, 18 May 2022 16:43:10 +0000 [thread overview]
Message-ID: <YoUiHhz1NsTbN5Vo@zeniv-ca.linux.org.uk> (raw)
vhost race fix + percpu_ref_init-caused cgroup double-free fix
(the latter had manifested as buggered struct mount refcounting -
those are also using percpu data structures, but anything that does
percpu allocations could be hit)
The following changes since commit feb9c5e19e913b53cb536a7aa7c9f20107bb51ec:
Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost (2022-05-10 11:15:05 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes
for you to fetch changes up to fb4554c2232e44d595920f4d5c66cf8f7d13f9bc:
Fix double fget() in vhost_net_set_backend() (2022-05-18 12:33:51 -0400)
----------------------------------------------------------------
Al Viro (2):
percpu_ref_init(): clean ->percpu_count_ref on failure
Fix double fget() in vhost_net_set_backend()
drivers/vhost/net.c | 15 +++++++--------
lib/percpu-refcount.c | 1 +
2 files changed, 8 insertions(+), 8 deletions(-)
next reply other threads:[~2022-05-18 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 16:43 Al Viro [this message]
2022-05-19 0:07 ` [git pull] a couple of fixes Linus Torvalds
2022-05-19 0:35 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2018-02-10 1:18 Al Viro
2016-03-10 19:15 Al Viro
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=YoUiHhz1NsTbN5Vo@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=torvalds@linux-foundation.org \
/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