From: Max <max@enpas.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] tty: Register device *after* creating the cdev for a tty
Date: Wed, 28 May 2025 22:31:15 +0900 [thread overview]
Message-ID: <bcbc2f6f-9935-415c-ac79-f839afe6204d@enpas.org> (raw)
In-Reply-To: <2025052801-human-aversion-3518@gregkh>
On 5/28/25 17:23, Greg Kroah-Hartman wrote:
> As 0-day points out, I think this adds a new locking issue :(
>
> But it's really hard to detect this, as you are doing both a revert and
> a change in the same commit. Can you make this as 2 patches, one that
> does the revert which would be "easy" to review, and the second one that
> does the new fix? That way we can detect what is going on easier.
Done!
Thanks for reviewing this, I've scratched my head about this locking for
a while, and just when I thought I had used a suitable lock... Well,
that's where maintainers (and now automation) come in :)
>> Fixes: 6a7e6f78c235 ("tty: close race between device register and open")
>> Signed-off-by: Max Staudt <max@enpas.org>
>
> You also forgot to add cc: stable on this :(
Done. I wasn't sure whether this needs to go to -stable, but since
you're the maintainer for both tty and stable, I figured you'd make a
choice anyway.
Thanks,
Max
prev parent reply other threads:[~2025-05-28 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 11:25 Max Staudt
2025-05-28 7:06 ` kernel test robot
2025-05-28 8:23 ` Greg Kroah-Hartman
2025-05-28 13:31 ` Max [this message]
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=bcbc2f6f-9935-415c-ac79-f839afe6204d@enpas.org \
--to=max@enpas.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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®