From: Greg KH <gregkh@linuxfoundation.org>
To: Hagar Hemdan <hagarhem@amazon.com>
Cc: stable@vger.kernel.org, felix <fuzhen5@huawei.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>
Subject: Re: [PATCH 4.14] SUNRPC: Fix RPC client cleaned up the freed pipefs dentries
Date: Tue, 16 Jul 2024 15:08:33 +0200 [thread overview]
Message-ID: <2024071616-unsliced-tactics-fb0b@gregkh> (raw)
In-Reply-To: <20240715131257.22428-1-hagarhem@amazon.com>
On Mon, Jul 15, 2024 at 01:12:57PM +0000, Hagar Hemdan wrote:
> From: felix <fuzhen5@huawei.com>
>
> [ Upstream commit bfca5fb4e97c46503ddfc582335917b0cc228264 ]
You mean 4.19, not 4.14, right? 4.14 is long-end-of-life.
thanks,
greg k-h
prev parent reply other threads:[~2024-07-16 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 13:12 [PATCH 4.14] SUNRPC: Fix RPC client cleaned up the freed pipefs dentries Hagar Hemdan
2024-07-16 13:08 ` 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=2024071616-unsliced-tactics-fb0b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=fuzhen5@huawei.com \
--cc=hagarhem@amazon.com \
--cc=stable@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox