From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Mark Brown <broonie@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-next@vger.kernel.org>
Subject: Re: Missing signoff in the ntfs3 tree
Date: Thu, 23 Jul 2026 16:56:30 +0200 [thread overview]
Message-ID: <3b593ff9-02ab-4ff2-abff-d689e28e59c2@paragon-software.com> (raw)
In-Reply-To: <6bfccbc7-2b99-47ce-bc50-9cbb95b8969c@sirena.org.uk>
On 7/21/26 02:08, Mark Brown wrote:
> On Wed, Jul 15, 2026 at 12:08:16PM +0100, Mark Brown wrote:
>> Commit
>>
>> f023839df8010 ("fs/ntfs3: fix out-of-bounds read of INDEX_ROOT in reparse/objid init")
>>
>> is missing a Signed-off-by from its author
> This issue is still present today.
I see. I'll fix it, thanks.
Regards,
Konstantin
prev parent reply other threads:[~2026-07-23 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 11:08 Missing signoff in the ntfs3 tree Mark Brown
2026-07-15 16:54 ` Konstantin Komarov
2026-07-15 17:10 ` Mark Brown
2026-07-21 0:08 ` Mark Brown
2026-07-23 14:56 ` Konstantin Komarov [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=3b593ff9-02ab-4ff2-abff-d689e28e59c2@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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