Am Wed, 4 Sep 2019 14:19:23 +0200 schrieb Jan Beulich <[email protected]>:
> On 04.09.2019 11:37, Olaf Hering wrote: > > Maybe just the lack of b49225dc9df336405292dc08862b4c7c9d887bd6 in vendor > > binaries... > But this change was only to deal with the bogus log message. > The handling was still correct (and the option was being > honored). I also can't see how this would be different now. Is that true? My interpretation of the code path is that no colon and nothing after a size value will lead to EINVAL. With this change any unknown string will cause EINVAL. Olaf
pgp2Xnvx_54Ro.pgp
Description: Digitale Signatur von OpenPGP
_______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
