From: Greg KH <gregkh@linuxfoundation.org>
To: Stefan Ghinea <stefan.ghinea@windriver.com>
Cc: stable@vger.kernel.org, Chao Yu <chao@kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [PATCH 6.3 1/1] f2fs: fix to avoid NULL pointer dereference f2fs_write_end_io()
Date: Thu, 20 Jul 2023 20:21:03 +0200 [thread overview]
Message-ID: <2023072048-unjustly-stagnate-85de@gregkh> (raw)
In-Reply-To: <20230719190944.15238-1-stefan.ghinea@windriver.com>
On Wed, Jul 19, 2023 at 10:09:44PM +0300, Stefan Ghinea wrote:
> From: Chao Yu <chao@kernel.org>
>
> commit d8189834d4348ae608083e1f1f53792cfcc2a9bc upstream
6.3.y is long end-of-life, sorry.
prev parent reply other threads:[~2023-07-20 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 19:09 [PATCH 6.3 1/1] f2fs: fix to avoid NULL pointer dereference f2fs_write_end_io() Stefan Ghinea
2023-07-20 18:21 ` 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=2023072048-unjustly-stagnate-85de@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stefan.ghinea@windriver.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