From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <ntfs3@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>
Subject: [PATCH 0/5] fs/ntfs3: Bugfix
Date: Mon, 29 Jan 2024 11:06:39 +0300 [thread overview]
Message-ID: <dedce962-d48d-41d6-bbbf-e95c66daba80@paragon-software.com> (raw)
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
fs/ntfs3/attrib.c | 4 ++--
fs/ntfs3/dir.c | 2 +-
fs/ntfs3/file.c | 13 ++++++++-----
fs/ntfs3/frecord.c | 10 +++++-----
fs/ntfs3/fslog.c | 14 ++++++++------
fs/ntfs3/fsntfs.c | 24 ++++++++++++++++++++++++
fs/ntfs3/index.c | 8 ++++----
fs/ntfs3/inode.c | 2 +-
fs/ntfs3/ntfs_fs.h | 14 +-------------
fs/ntfs3/record.c | 2 +-
10 files changed, 55 insertions(+), 38 deletions(-)
--
2.34.1
next reply other threads:[~2024-01-29 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 8:06 Konstantin Komarov [this message]
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 ` [PATCH 0/5] fs/ntfs3: Bugfix Linux regression tracking (Thorsten Leemhuis)
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=dedce962-d48d-41d6-bbbf-e95c66daba80@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@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