[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7d2eab46-bad4-3e28-50e7-92a34e22ecd8@huaweicloud.com>
Date: Tue, 20 Jan 2026 19:41:10 +0800
From: Li Nan <linan666@...weicloud.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: arnd@...db.de, linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk,
wanghai38@...wei.com, "yi.zhang@...wei.com" <yi.zhang@...wei.com>,
"yangerkun@...wei.com" <yangerkun@...wei.com>
Subject: Re: [PATCH v2] char: lp: Fix NULL pointer dereference of cad
在 2026/1/20 17:23, Greg KH 写道:
> On Tue, Jan 20, 2026 at 03:55:47PM +0800, Li Nan wrote:
>>> And how was this tested?
>>
>> We found this issue during fuzzing in QEMU.
>> Based on the root cause, I got the following reproducer:
>
> QEMU is not real hardware :)
>
> Do you really still use parallel port hardware in the real world? or
> is this just an accidemic exercise of a fuzzing tool?
>
Yes, the issue was first found in QEMU.
We do have some parallel port hardware for testing, as this module was
used by our customers in the past, though we are not sure if it is still
in active use today. This work is mainly part of routine maintenance.
> thanks,
>
> greg k-h
--
Thanks,
Nan
Powered by blists - more mailing lists