Linux s390 Architecture development
 help / color / mirror / Atom feed
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>,
	stable@vger.kernel.org
Subject: Re: [PATCH v3 2/8] s390/vfio_ccw: limit the number of channel program segments
Date: Fri, 24 Jul 2026 11:54:21 -0400	[thread overview]
Message-ID: <8e4c0105-e2f4-4ff8-9b8a-ca4db31a4a66@linux.ibm.com> (raw)
In-Reply-To: <20260723174751.1180334-3-farman@linux.ibm.com>

On 7/23/26 1:47 PM, Eric Farman wrote:
> The processing of channel programs, and the CCWs within them, is done
> recursively. As such, there is an arbitrary (but not architectural)
> limit to the number of CCWs that can exist in a single channel program.
> 
> The vfio-ccw logic breaks these channel programs into segments whenever
> it encounters a Transfer-In-Channel (TIC) CCW, and the combined number
> of segments count towards the global limit. Impose an equivalent limit
> to the number of segments until such logic can be made non-recursive.
> 

At a future point if/when this is made non-recursive, we should at that
time keep limits with sane defaults in-place but at also consider making
it kernel-configurable (like the vfio dma limit).

...

>   * struct channel_program - manage information for channel program
>   * @ccwchain_list: list head of ccwchains
> @@ -38,6 +43,7 @@ struct channel_program {
>  	union orb orb;
>  	bool initialized;
>  	struct ccw1 *guest_cp;
> +	int ccwchain_count;

Nit: Unsigned?

Regardless:

Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>

>  };
>  
>  int cp_init(struct channel_program *cp, union orb *orb);


  parent reply	other threads:[~2026-07-24 15:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 17:47 [PATCH v3 0/8] s390/vfio_ccw fixes Eric Farman
2026-07-23 17:47 ` [PATCH v3 1/8] s390/vfio_ccw: free all memory if cp_init() fails Eric Farman
2026-07-23 18:31   ` sashiko-bot
2026-07-24 15:02   ` Matthew Rosato
2026-07-23 17:47 ` [PATCH v3 2/8] s390/vfio_ccw: limit the number of channel program segments Eric Farman
2026-07-23 18:26   ` sashiko-bot
2026-07-24 15:54   ` Matthew Rosato [this message]
2026-07-23 17:47 ` [PATCH v3 3/8] s390/vfio_ccw: fix out of bounds check on CCW array Eric Farman
2026-07-23 18:22   ` sashiko-bot
2026-07-24 16:49   ` Matthew Rosato
2026-07-24 17:53     ` Eric Farman
2026-07-23 17:47 ` [PATCH v3 4/8] s390/vfio_ccw: ensure first IDAW remains constant Eric Farman
2026-07-23 18:29   ` sashiko-bot
2026-07-23 20:38     ` Eric Farman
2026-07-24 17:51       ` Matthew Rosato
2026-07-24 17:13   ` Matthew Rosato
2026-07-23 17:47 ` [PATCH v3 5/8] s390/vfio_ccw: calculate idal length based on idaw type Eric Farman
2026-07-23 18:23   ` sashiko-bot
2026-07-24 17:38   ` Matthew Rosato
2026-07-23 17:47 ` [PATCH v3 6/8] s390/vfio_ccw: ensure index for read/write regions are within range Eric Farman
2026-07-23 18:30   ` sashiko-bot
2026-07-24 19:01   ` Matthew Rosato
2026-07-24 19:51     ` Eric Farman
2026-07-23 17:47 ` [PATCH v3 7/8] s390/vfio_ccw: implement a channel program mutex Eric Farman
2026-07-23 18:32   ` sashiko-bot
2026-07-24 20:18   ` Matthew Rosato
2026-07-23 17:47 ` [PATCH v3 8/8] s390/vfio_ccw: implement a crw lock Eric Farman
2026-07-23 18:34   ` sashiko-bot
2026-07-24 20:44   ` Matthew Rosato

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=8e4c0105-e2f4-4ff8-9b8a-ca4db31a4a66@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 \
    --cc=stable@vger.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