From: Simon Horman <horms@kernel.org>
To: Gui-Dong Han <2045gemini@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
3chas3@gmail.com, linux-atm-general@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
baijiaju1990@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] atm/fore200e: Fix possible data race in fore200e_open()
Date: Fri, 14 Nov 2025 12:05:27 +0000 [thread overview]
Message-ID: <aRcbB5PekC9kR96d@horms.kernel.org> (raw)
In-Reply-To: <CAOPYjvbEbrU6qOewg4Ddc8CBDjmXous=PbgFF+5cQHf98Jtftw@mail.gmail.com>
On Tue, Nov 11, 2025 at 08:47:14PM +0800, Gui-Dong Han wrote:
> Hi Jakub and Simon,
>
> I was organizing my emails and noticed this v2 patch from January.
> Simon kindly provided a "Reviewed-by" tag for it.
>
> It seems this patch may have been overlooked and was not merged.
> I checked the current upstream tree, and the data race in
> fore200e_open() (accessing fore200e->available_cell_rate
> without the rate_mtx lock in the error path) still exists.
>
> Could you please take another look and consider this patch for merging?
Hi,
January was a long time ago, so I guess this slipped through the cracks somehow.
I would suggest reposting it to have it considered for merging.
I'd also explicitly target the patch at net. Something like this:
Subject: [PATCH REPOST net v2] ...
And feel free to include my Reviewed-by tag.
prev parent reply other threads:[~2025-11-14 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 2:37 [PATCH v2] atm/fore200e: Fix possible data race in fore200e_open() Gui-Dong Han
2025-01-22 9:46 ` Simon Horman
2025-01-23 15:12 ` Jakub Kicinski
2025-01-24 0:50 ` Gui-Dong Han
2025-11-11 12:47 ` Gui-Dong Han
2025-11-14 12:05 ` Simon Horman [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=aRcbB5PekC9kR96d@horms.kernel.org \
--to=horms@kernel.org \
--cc=2045gemini@gmail.com \
--cc=3chas3@gmail.com \
--cc=baijiaju1990@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.