[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87cz7aqpxi.fsf@ubik.fi.intel.com>
Date: Thu, 19 Jan 2023 21:34:17 +0200
From: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: mst@...hat.com, jasowang@...hat.com,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, elena.reshetova@...el.com,
kirill.shutemov@...ux.intel.com, Andi Kleen <ak@...ux.intel.com>,
Amit Shah <amit@...nel.org>, Arnd Bergmann <arnd@...db.de>,
alexander.shishkin@...ux.intel.com
Subject: Re: [PATCH v1 1/6] virtio console: Harden multiport against invalid
host input
Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:
> On Thu, Jan 19, 2023 at 08:52:02PM +0200, Alexander Shishkin wrote:
>> Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:
>>
>> > Why did I only get a small subset of these patches?
>>
>> I did what get_maintainer told me. Would you like to be CC'd on the
>> whole thing?
>
> If you only cc: me on a portion of the series, I guess you only want me
> to apply a portion of it? if so, why is it a longer series?
I was expecting that this series will eventually go in via the virtio
maintainers, assuming you can give your acks to the char bits.
Or, I can split off the char bits and send them to you
separately. Whichever makes the most sense.
>> > But, this still feels wrong. Why is this happening here, in init_vqs()
>> > and not in the calling function that already did a bunch of validation
>> > of the ports and the like? Are those checks not enough? if not, fix it
>> > there, don't spread it out all over the place...
>>
>> Good point! And there happens to already be 28962ec595d70 that takes
>> care of exactly this case. I totally missed it.
>
> So this series is not needed? Or just this one?
Just this one.
Regards,
--
Alex
Powered by blists - more mailing lists