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: Refactoring and bugfix
Date: Fri, 30 Dec 2022 15:23:04 +0400 [thread overview]
Message-ID: <b06828df-f9b9-1c5d-d6db-05839bad7016@paragon-software.com> (raw)
This series contains various fixes and refactoring for ntfs3.
Konstantin Komarov (5):
fs/ntfs3: Add null pointer checks
fs/ntfs3: Improved checking of attribute's name length
fs/ntfs3: Check for extremely large size of $AttrDef
fs/ntfs3: Restore overflow checking for attr size in mi_enum_attr
fs/ntfs3: Refactoring of various minor issues
fs/ntfs3/bitmap.c | 3 ++-
fs/ntfs3/frecord.c | 2 +-
fs/ntfs3/fsntfs.c | 22 ++++++++++++++--------
fs/ntfs3/index.c | 10 ++++++----
fs/ntfs3/inode.c | 8 +++++++-
fs/ntfs3/namei.c | 2 +-
fs/ntfs3/ntfs.h | 3 ---
fs/ntfs3/record.c | 5 +++++
fs/ntfs3/super.c | 10 +++++++++-
9 files changed, 45 insertions(+), 20 deletions(-)
--
2.34.1
next reply other threads:[~2022-12-30 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 11:23 Konstantin Komarov [this message]
2022-12-30 11:23 ` [PATCH 1/5] fs/ntfs3: Add null pointer checks Konstantin Komarov
2022-12-30 11:25 ` [PATCH 2/5] fs/ntfs3: Improved checking of attribute's name length Konstantin Komarov
2022-12-30 11:25 ` [PATCH 3/5] fs/ntfs3: Check for extremely large size of $AttrDef Konstantin Komarov
2022-12-30 11:26 ` [PATCH 4/5] fs/ntfs3: Restore overflow checking for attr size in mi_enum_attr Konstantin Komarov
2022-12-30 11:27 ` [PATCH 5/5] fs/ntfs3: Refactoring of various minor issues 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=b06828df-f9b9-1c5d-d6db-05839bad7016@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;
as well as URLs for NNTP newsgroup(s).