[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f6c25172-573e-a7d2-8264-f44f0a5a0a27@redhat.com>
Date: Tue, 26 Jun 2018 07:40:36 +0200
From: Thomas Huth <thuth@...hat.com>
To: Georgi Guninski <guninski@...inski.com>,
Christian Borntraeger <borntraeger@...ibm.com>
Cc: Guenter Roeck <linux@...ck-us.net>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
qemu-s390x <qemu-s390x@...gnu.org>,
qemu-devel <qemu-devel@...gnu.org>,
Cornelia Huck <cohuck@...hat.com>
Subject: Re: s390 qemu boot failure in -next
On 26.06.2018 07:32, Georgi Guninski wrote:
> On Mon, Jun 25, 2018 at 09:27:59AM +0200, Christian Borntraeger wrote:
>> - /* Overwrite parameters in the kernel image, which are "rom" */
>> - strcpy(rom_ptr(KERN_PARM_AREA), ipl->cmdline);
>
>> + strcpy(rom_ptr(KERN_PARM_AREA), ipl->cmdline);
>
> Why not replace strcpy() with strncpy() or snprintf()?
> strcpy() may overflow.
This will be fixed by
https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg04227.html by
adding a check for a valid size.
Thomas
Powered by blists - more mailing lists