Hi,
Can you apply these three patches, one for each of the 5.10, 5.15, and 5.18 stable tree? Doesn't fix any issues of concern, just ensures that we -EINVAL when invalid fields are set in the sqe for these opcodes. This brings it up to par with 5.19 and newer.
Thanks!
On 6/30/22 2:45 PM, Jens Axboe wrote:
Hi,
Can you apply these three patches, one for each of the 5.10, 5.15, and 5.18 stable tree? Doesn't fix any issues of concern, just ensures that we -EINVAL when invalid fields are set in the sqe for these opcodes. This brings it up to par with 5.19 and newer.
Just a reminder on this one, thanks!
On 7/4/22 7:26 AM, Jens Axboe wrote:
On 6/30/22 2:45 PM, Jens Axboe wrote:
Hi,
Can you apply these three patches, one for each of the 5.10, 5.15, and 5.18 stable tree? Doesn't fix any issues of concern, just ensures that we -EINVAL when invalid fields are set in the sqe for these opcodes. This brings it up to par with 5.19 and newer.
Just a reminder on this one, thanks!
Disregard, mid-air collision on emails. Thanks for queueing them up.
On Thu, Jun 30, 2022 at 02:45:53PM -0600, Jens Axboe wrote:
Hi,
Can you apply these three patches, one for each of the 5.10, 5.15, and 5.18 stable tree? Doesn't fix any issues of concern, just ensures that we -EINVAL when invalid fields are set in the sqe for these opcodes. This brings it up to par with 5.19 and newer.
All now queued up, thanks.
greg k-h
linux-stable-mirror@lists.linaro.org
-
Greg Kroah-Hartman -
Jens Axboe