[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AP6AfgBTJ12KMCuulosf7Kqq.3.1765286666213.Hmail.2200013188@stu.pku.edu.cn>
Date: Tue, 9 Dec 2025 21:24:26 +0800 (GMT+08:00)
From: Tianyu Li <2200013188@....pku.edu.cn>
To: Ian Abbott <abbotti@....co.uk>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
hsweeten <hsweeten@...ionengravers.com>,
xujiakai2025 <xujiakai2025@...as.ac.cn>,
"zhaoruilin22@...ls.ucas.ac.cn" <zhaoruilin22@...ls.ucas.ac.cn>
Subject: Re: [BUG] Drivers/8255: Page fault in comedi_8255.c
Hi Ian,
Thank you for the detailed explanation — that clarifies the situation very well.
You mentioned that in linux-next the 8255 driver now returns an error immediately when reserving an I/O port region fails, which would also avoid the crash during fuzzing. I would like to take a closer look at that change.
> One thing that will affect the fuzzing tests is that the "8255" driver
> in "linux-next" now returns an error as soon as it fails to reserve any
> I/O port region, so unless the special base addresses (0x100 etc.)
> appear early in the list before the conflicting base addresses, it won't
> crash.
Could you please point me to the specific commit or patch where this improvement was introduced (a commit hash or link would be perfect if convenient)? This would help me better understand the context and verify the behavior on my side.
Thanks again for your guidance — I really appreciate your help.
Best regards,
Tianyu Li
Powered by blists - more mailing lists