From: Greg KH <gregkh@linuxfoundation.org>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: ntfs3@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] fs/ntfs3: Fix case when index is reused during tree transformation
Date: Tue, 23 Apr 2024 07:55:42 -0700 [thread overview]
Message-ID: <2024042318-radio-concept-9a0b@gregkh> (raw)
In-Reply-To: <20240423144155.10219-1-almaz.alexandrovich@paragon-software.com>
On Tue, Apr 23, 2024 at 05:41:54PM +0300, Konstantin Komarov wrote:
> Fixes: 82cae269cfa95 ("fs/ntfs3: Add initialization of super block")
> Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
> Cc: stable@vger.kernel.org
> ---
> fs/ntfs3/index.c | 6 ++++++
> 1 file changed, 6 insertions(+)
I know I can't take patches without any changelog text, and odds are you
shouldn't either...
thanks,
greg k-h
next prev parent reply other threads:[~2024-04-23 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 14:41 [PATCH] fs/ntfs3: Fix case when index is reused during tree transformation Konstantin Komarov
2024-04-23 14:55 ` Greg KH [this message]
2024-05-16 12:00 ` [PATCH v2] " Konstantin Komarov
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=2024042318-radio-concept-9a0b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 NNTP newsgroup(s).