From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
ntfs3@lists.linux.dev
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH 0/5] fs/ntfs3: Bugfix
Date: Sun, 11 Feb 2024 13:31:09 +0100 [thread overview]
Message-ID: <bdea4053-b978-489d-a4a2-927685eee4a8@leemhuis.info> (raw)
In-Reply-To: <dedce962-d48d-41d6-bbbf-e95c66daba80@paragon-software.com>
On 29.01.24 09:06, Konstantin Komarov wrote:
>
> This series contains various fixes for ntfs3.
>
> Konstantin Komarov (5):
> fs/ntfs3: Prevent generic message "attempt to access beyond end of
> device"
> fs/ntfs3: Use i_size_read and i_size_write
> fs/ntfs3: Correct function is_rst_area_valid
> fs/ntfs3: Fixed overflow check in mi_enum_attr()
> fs/ntfs3: Update inode->i_size after success write into compressed
> file
Thx for working on these patches that recently hit mainline.
The last patch listed above afaics (I might be wrong there!) is a fix
for https://bugzilla.kernel.org/show_bug.cgi?id=218180 (~"data added to
a newly created file that uses compression only becomes visible after a
remount or a forced cache drop"). That regression from the 6.2 days
sounds somewhat concerning, hence allow me to ask: do you plan to submit
this fix for backporting to the 6.7.y and 6.6.y series? If not: do you
think it should be save to include those there?
Side not, while at it: are any of the other patches maybe also worth
backporting?
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
prev parent reply other threads:[~2024-02-11 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 8:06 [PATCH 0/5] fs/ntfs3: Bugfix Konstantin Komarov
2024-01-29 8:07 ` [PATCH 1/5] fs/ntfs3: Prevent generic message "attempt to access beyond end of device" Konstantin Komarov
2024-01-29 8:08 ` [PATCH 2/5] fs/ntfs3: Use i_size_read and i_size_write Konstantin Komarov
2024-01-29 8:08 ` [PATCH 3/5] fs/ntfs3: Correct function is_rst_area_valid Konstantin Komarov
2024-01-29 8:09 ` [PATCH 4/5] fs/ntfs3: Fixed overflow check in mi_enum_attr() Konstantin Komarov
2024-01-29 8:09 ` [PATCH 5/5] fs/ntfs3: Update inode->i_size after success write into compressed file Konstantin Komarov
2024-02-11 12:31 ` Linux regression tracking (Thorsten Leemhuis) [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=bdea4053-b978-489d-a4a2-927685eee4a8@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=regressions@lists.linux.dev \
/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).