From: Johan Hovold <johan@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Qiu-ji Chen <chenqiuji666@gmail.com>,
dtwlin@gmail.com, elder@kernel.org, greybus-dev@lists.linaro.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
baijiaju1990@gmail.com
Subject: Re: [PATCH v3] staging: greybus: uart: Fix atomicity violation in get_serial_info()
Date: Thu, 7 Nov 2024 16:22:41 +0100 [thread overview]
Message-ID: <ZyzbQQGEaBRIRYi1@hovoldconsulting.com> (raw)
In-Reply-To: <2024110724-overbuilt-liquid-3734@gregkh>
On Thu, Nov 07, 2024 at 04:11:00PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Nov 07, 2024 at 07:33:37PM +0800, Qiu-ji Chen wrote:
> > Our static checker found a bug where set_serial_info() uses a mutex, but
> > get_serial_info() does not. Fortunately, the impact of this is relatively
> > minor. It doesn't cause a crash or any other serious issues. However, if a
> > race condition occurs between set_serial_info() and get_serial_info(),
> > there is a chance that the data returned by get_serial_info() will be
> > meaningless.
>
> Trailing whitespace :(
>
> You should fix your editor to highlight this so it doesn't keep showing
> up.
>
> >
> > Signed-off-by: Qiu-ji Chen <chenqiuji666@gmail.com>
> > Fixes: 0aad5ad563c8 ("greybus/uart: switch to ->[sg]et_serial()")
> - You have marked a patch with a "Fixes:" tag for a commit that is in an
> older released kernel, yet you do not have a cc: stable line in the
> signed-off-by area at all, which means that the patch will not be
> applied to any older kernel releases. To properly fix this, please
> follow the documented rules in the
> Documentation/process/stable-kernel-rules.rst file for how to resolve
> this.
The CC-stable tag was left out on purpose (on my request IIRC) as this
is not fixing anything that's really a problem and is basically just
shutting the static checker up.
I believe this was also reflected in the commit message of v2 (even if
"inconsistent" may have been a better word than "meaningless").
Johan
next prev parent reply other threads:[~2024-11-07 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 11:33 Qiu-ji Chen
2024-11-07 15:11 ` Greg KH
2024-11-07 15:22 ` Johan Hovold [this message]
2024-11-11 9:14 ` Dan Carpenter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZyzbQQGEaBRIRYi1@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=baijiaju1990@gmail.com \
--cc=chenqiuji666@gmail.com \
--cc=dtwlin@gmail.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®