From: Greg KH <gregkh@linuxfoundation.org>
To: Tahera Fahimi <taherafahimi@linux.microsoft.com>
Cc: stable@vger.kernel.org, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, raminwo0202@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, apais@linux.microsoft.com
Subject: Re: [PATCH V1] xfrm: prevent policy_hthresh.work from racing with netns teardown
Date: Fri, 21 Aug 2026 06:25:45 +0200 [thread overview]
Message-ID: <2026082106-widget-steed-ece0@gregkh> (raw)
In-Reply-To: <20260820211418.1409602-1-taherafahimi@linux.microsoft.com>
On Thu, Aug 20, 2026 at 02:14:18PM -0700, Tahera Fahimi wrote:
> [ Upstream commit 29fe3a61bcdce398ee3955101c39f89c01a8a77e ]
No it is not :(
prev parent reply other threads:[~2026-08-21 4:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 21:14 [PATCH V1] xfrm: prevent policy_hthresh.work from racing with netns teardown Tahera Fahimi
2026-08-21 4:25 ` Greg KH [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=2026082106-widget-steed-ece0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=apais@linux.microsoft.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raminwo0202@gmail.com \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=taherafahimi@linux.microsoft.com \
/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.