From: Naman Jain <namjain@linux.microsoft.com>
To: "K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
Saurabh Sengar <ssengar@linux.microsoft.com>,
Naman Jain <namjain@linux.microsoft.com>
Subject: [PATCH 0/2] Drivers: vmbus: Fix rescind handling in uio_hv_generic
Date: Thu, 22 Aug 2024 16:39:10 +0530 [thread overview]
Message-ID: <20240822110912.13735-1-namjain@linux.microsoft.com> (raw)
Fix a few issues in rescind handling in uio_hv_generic driver.
Patches are based on linux-next-rc4 tip.
Steps to reproduce issue:
* Probe uio_hv_generic driver and create channels to use fcopy
* Disable the guest service on host and then Enable it.
or
* repeatedly do cat "/dev/uioX" on the device created for fcopy.
Naman Jain (1):
Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic
Saurabh Sengar (1):
uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind
drivers/hv/vmbus_drv.c | 1 +
drivers/uio/uio_hv_generic.c | 10 +++++++++-
2 files changed, 10 insertions(+), 1 deletion(-)
base-commit: 469f1bad3c1c6e268059f78c0eec7e9552b3894c
--
2.34.1
next reply other threads:[~2024-08-22 11:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 11:09 Naman Jain [this message]
2024-08-22 11:09 ` [PATCH 1/2] uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind Naman Jain
2024-08-24 3:09 ` Greg Kroah-Hartman
2024-08-25 2:51 ` Michael Kelley
2024-08-26 5:31 ` Naman Jain
2024-08-22 11:09 ` [PATCH 2/2] Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic Naman Jain
2024-08-24 3:09 ` Greg Kroah-Hartman
2024-08-25 2:57 ` Michael Kelley
2024-08-26 5:31 ` Naman Jain
2024-08-26 5:40 ` Michael Kelley
2024-08-26 5:44 ` Naman Jain
2024-08-27 18:24 ` Saurabh Singh Sengar
2024-08-28 14:53 ` Michael Kelley
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=20240822110912.13735-1-namjain@linux.microsoft.com \
--to=namjain@linux.microsoft.com \
--cc=decui@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ssengar@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--cc=wei.liu@kernel.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