[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250330105135.389827-1-ryotkkr98@gmail.com>
Date: Sun, 30 Mar 2025 19:51:35 +0900
From: Ryo Takakura <ryotkkr98@...il.com>
To: gregkh@...uxfoundation.org
Cc: alex@...ti.fr,
aou@...s.berkeley.edu,
bigeasy@...utronix.de,
conor.dooley@...rochip.com,
jirislaby@...nel.org,
john.ogness@...utronix.de,
linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org,
linux-serial@...r.kernel.org,
lkp@...el.com,
oe-kbuild-all@...ts.linux.dev,
palmer@...belt.com,
paul.walmsley@...ive.com,
pmladek@...e.com,
ryotkkr98@...il.com,
samuel.holland@...ive.com,
stable@...r.kernel.org,
u.kleine-koenig@...libre.com
Subject: Re: [PATCH v2 1/2] serial: sifive: lock port in startup()/shutdown() callbacks
Hi Greg,
On Sun, 30 Mar 2025 09:30:27 +0200, Greg KH wrote:
>On Sun, Mar 30, 2025 at 10:16:10AM +0900, Ryo Takakura wrote:
>> startup()/shutdown() callbacks access SIFIVE_SERIAL_IE_OFFS.
>> The register is also accessed from write() callback.
>>
>> If console were printing and startup()/shutdown() callback
>> gets called, its access to the register could be overwritten.
>>
>> Add port->lock to startup()/shutdown() callbacks to make sure
>> their access to SIFIVE_SERIAL_IE_OFFS is synchronized against
>> write() callback.
>>
>> Signed-off-by: Ryo Takakura <ryotkkr98@...il.com>
>> Cc: stable@...r.kernel.org
>> ---
>>
>> Hi,
>>
>> I'm sorry that I wasn't aware of how Cc stable should be done.
>>
>> I added Cc for stable but please tell me if this patch should be
>> resent or if there is any that is missing.
>
>Please resend a v3.
Ok. I'll send v3 shortly ;)
Sincerely,
Ryo Takakura
>thanks,
>
>greg k-h
Powered by blists - more mailing lists