linux-kernel - Re: [PATCH] serial: core: Fix double fetch in uart_throttle/uart

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAOPYjvZYAxo=-H2eeJ8mHjx4af=TetbtZ_54-iX2cokzEHFeaA@mail.gmail.com>
Date: Sat, 13 Jan 2024 02:52:42 +0800
From: Gui-Dong Han <2045gemini@...il.com>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Jiri Slaby <jirislaby@...nel.org>, 
	Tony Lindgren <tony@...mide.com>, l.sanfilippo@...bus.com, john.ogness@...utronix.de, 
	tglx@...utronix.de, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
	LKML <linux-kernel@...r.kernel.org>, linux-serial <linux-serial@...r.kernel.org>, 
	baijiaju1990@...look.com, stable@...r.kernel.org
Subject: Re: [PATCH] serial: core: Fix double fetch in uart_throttle/uart_unthrottle

Hi

I apologize for any issues and lack of clarity in my previous patch.
In patch v2, I've revised the fix to use local variables instead of
locks and improved the description to clearly explain the harm and
potential for concurrency.

The patch was developed and tested on linux-next, not Linux 5.17. My
reference to 5.17 was due to a project I'm working on, which involves
kernel static analysis and a comparison with earlier studies that
support up to Linux 5.17. Therefore, I initially ran my tool on 5.17
to filter potential bugs that are still unaddressed in the upstream.
Then I worked on linux-next to develop and test the patch. I
understand this might have caused misunderstandings, and I'll aim for
clearer communication in future submissions.

Thanks,
Han