From: Markus Elfring <Markus.Elfring@web.de>
To: Jiasheng Jiang <jiashengjiangcool@gmail.com>, ntfs3@lists.linux.dev
Cc: stable@vger.kernel.org, kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Subject: Re: [PATCH v2] fs/ntfs3: Fix infinite loop in hdr_find_split due to zero-sized entry
Date: Mon, 19 Jan 2026 10:48:47 +0100 [thread overview]
Message-ID: <3a4eaee4-ff01-48b7-bfdb-a127c60d5064@web.de> (raw)
In-Reply-To: <20260118190145.41997-1-jiashengjiangcool@gmail.com>
…
> This patch adds a sanity check …
Thanks for another contribution.
* Does anything hinder to follow a corresponding wording requirement?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.19-rc5#n94
* Can it be helpful to append parentheses to function names?
Regards,
Markus
prev parent reply other threads:[~2026-01-19 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65bf90b1-8806-4f8c-b7e7-d90193d28e88@web.de>
2026-01-18 19:01 ` [PATCH v2] fs/ntfs3: Fix infinite loop in hdr_find_split due to zero-sized entry Jiasheng Jiang
2026-01-19 6:37 ` Greg KH
2026-01-19 9:48 ` Markus Elfring [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=3a4eaee4-ff01-48b7-bfdb-a127c60d5064@web.de \
--to=markus.elfring@web.de \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=jiashengjiangcool@gmail.com \
--cc=kernel-janitors@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