From: Greg KH <gregkh@linuxfoundation.org>
To: Lee Jones <lee@kernel.org>
Cc: almaz.alexandrovich@paragon-software.com, stable@vger.kernel.org,
ntfs3@lists.linux.dev, linux-fsdevel@vger.kernel.org,
van fantasy <g1042620637@gmail.com>
Subject: Re: [PATCH 1/1] fs/ntfs3: Check fields while reading
Date: Thu, 20 Jul 2023 19:55:50 +0200 [thread overview]
Message-ID: <2023072022-yahoo-pushy-2b86@gregkh> (raw)
In-Reply-To: <20230717174020.GE1082701@google.com>
On Mon, Jul 17, 2023 at 06:40:20PM +0100, Lee Jones wrote:
> On Mon, 17 Jul 2023, Greg KH wrote:
>
> > On Mon, Jul 17, 2023 at 01:50:13PM +0100, Lee Jones wrote:
> > > commit 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b upstream.
> > >
> > > Added new functions index_hdr_check and index_buf_check.
> > > Now we check all stuff for correctness while reading from disk.
> > > Also fixed bug with stale nfs data.
> > >
> > > Reported-by: van fantasy <g1042620637@gmail.com>
> > > Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
> > > Fixes: 82cae269cfa95 ("fs/ntfs3: Add initialization of super block")
> > > Signed-off-by: Lee Jones <lee@kernel.org>
> > > ---
> >
> > What stable tree(s) is this for?
>
> I thought you had tooling that used the Fixes: tag for this?
Yes, but that tells me how far back to take a patch, but not what a
hand-crafted backport should be applied to :)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-07-20 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 12:50 [PATCH 1/1] fs/ntfs3: Check fields while reading Lee Jones
2023-07-17 13:39 ` Greg KH
2023-07-17 17:40 ` Lee Jones
2023-07-20 17:55 ` 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=2023072022-yahoo-pushy-2b86@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=g1042620637@gmail.com \
--cc=lee@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).