From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Eric Farman <farman@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v9 00/10] s390/vfio_ccw fixes
Date: Tue, 28 Jul 2026 10:53:43 -0400 [thread overview]
Message-ID: <93e1e75a-3036-47cc-a142-eff9b43630d7@linux.ibm.com> (raw)
In-Reply-To: <20260728033022.2658232-1-farman@linux.ibm.com>
On 7/27/26 11:30 PM, Eric Farman wrote:
> This series addresses some pre-existing issues found in the
> s390 vfio_ccw (DASD passthrough) driver.
>
> Patches 1-6 are identical to v6/v7/v8
> Patches 7-10 have minor changes compared to v7/v8
>
> v1: https://lore.kernel.org/r/20260714232208.1683788-1-farman@linux.ibm.com/
> v2: https://lore.kernel.org/r/20260720201931.976660-1-farman@linux.ibm.com/
> v3: https://lore.kernel.org/r/20260723174751.1180334-1-farman@linux.ibm.com/
> v4: https://lore.kernel.org/r/20260725152705.3958100-1-farman@linux.ibm.com/
> v5: https://lore.kernel.org/r/20260726040129.2946151-1-farman@linux.ibm.com/
> v6: https://lore.kernel.org/r/20260726172153.1818056-1-farman@linux.ibm.com/
> v7: https://lore.kernel.org/r/20260727192230.2715207-1-farman@linux.ibm.com/
> v8: https://lore.kernel.org/r/20260728013509.1551753-1-farman@linux.ibm.com/
> v8->v9:
> - [MR] Added r-b (thank you!)
> - [MR] Commit/comment message improvements
> - [MR/sashiko] Re-add workqueue cleanup to vfio_ccw_mdev_release_dev, in the
> form of a flush_work() call
Thanks Eric.
I think at this point the big issues are resolved, and this already is a
significant improvement overall.
We've also identified a few things (here and off-list) that would be
reasonable tackled as follow-ons, such as a well-defined lock hierarchy
and identifying reasonable places to add lockdep assertions.
Thanks,
Matt
>
> Eric Farman (10):
> s390/vfio_ccw: free all memory if cp_init() fails
> s390/vfio_ccw: limit the number of channel program segments
> s390/vfio_ccw: fix out of bounds check on CCW array
> s390/vfio_ccw: ensure first IDAW remains constant
> s390/vfio_ccw: calculate idal length based on idaw type
> s390/vfio_ccw: ensure index for read/write regions are within range
> s390/vfio_ccw: cancel existing workqueues
> s390/vfio_ccw: move cp cleanup out of not operational
> s390/vfio_ccw: selectively expand io_mutex
> s390/vfio_ccw: implement a crw lock
>
> drivers/s390/cio/vfio_ccw_async.c | 16 +++++++
> drivers/s390/cio/vfio_ccw_chp.c | 31 ++++++++++--
> drivers/s390/cio/vfio_ccw_cp.c | 74 +++++++++++++++++++++--------
> drivers/s390/cio/vfio_ccw_cp.h | 10 ++++
> drivers/s390/cio/vfio_ccw_drv.c | 21 +++++++-
> drivers/s390/cio/vfio_ccw_fsm.c | 8 +++-
> drivers/s390/cio/vfio_ccw_ops.c | 39 +++++++++++++--
> drivers/s390/cio/vfio_ccw_private.h | 10 +++-
> 8 files changed, 176 insertions(+), 33 deletions(-)
>
prev parent reply other threads:[~2026-07-28 14:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 3:30 [PATCH v9 00/10] s390/vfio_ccw fixes Eric Farman
2026-07-28 3:30 ` [PATCH v9 01/10] s390/vfio_ccw: free all memory if cp_init() fails Eric Farman
2026-07-28 4:03 ` sashiko-bot
2026-07-28 3:30 ` [PATCH v9 02/10] s390/vfio_ccw: limit the number of channel program segments Eric Farman
2026-07-28 3:52 ` sashiko-bot
2026-07-28 3:30 ` [PATCH v9 03/10] s390/vfio_ccw: fix out of bounds check on CCW array Eric Farman
2026-07-28 3:59 ` sashiko-bot
2026-07-28 3:30 ` [PATCH v9 04/10] s390/vfio_ccw: ensure first IDAW remains constant Eric Farman
2026-07-28 3:59 ` sashiko-bot
2026-07-28 3:30 ` [PATCH v9 05/10] s390/vfio_ccw: calculate idal length based on idaw type Eric Farman
2026-07-28 4:00 ` sashiko-bot
2026-07-28 3:30 ` [PATCH v9 06/10] s390/vfio_ccw: ensure index for read/write regions are within range Eric Farman
2026-07-28 4:02 ` sashiko-bot
2026-07-28 3:30 ` [PATCH v9 07/10] s390/vfio_ccw: cancel existing workqueues Eric Farman
2026-07-28 4:02 ` sashiko-bot
2026-07-28 3:30 ` [PATCH v9 08/10] s390/vfio_ccw: move cp cleanup out of not operational Eric Farman
2026-07-28 4:01 ` sashiko-bot
2026-07-28 14:48 ` Matthew Rosato
2026-07-28 3:30 ` [PATCH v9 09/10] s390/vfio_ccw: selectively expand io_mutex Eric Farman
2026-07-28 4:05 ` sashiko-bot
2026-07-28 14:48 ` Matthew Rosato
2026-07-28 3:30 ` [PATCH v9 10/10] s390/vfio_ccw: implement a crw lock Eric Farman
2026-07-28 4:05 ` sashiko-bot
2026-07-28 14:45 ` [PATCH v9 00/10] s390/vfio_ccw fixes Christian Borntraeger
2026-07-28 14:53 ` Matthew Rosato [this message]
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=93e1e75a-3036-47cc-a142-eff9b43630d7@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.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