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: Reworking symlink functions
Date: Tue, 5 Oct 2021 19:43:30 +0300 [thread overview]
Message-ID: <98a166e4-f894-8bff-9479-05ef5435f1ed@paragon-software.com> (raw)
If length of symlink > 255, then we tried to convert
length of symlink +- some random number.
So main theme is removing 255 symbols limit in ntfs_utf16_to_nls.
Other bug - we haven't always returned correct size of symlink,
so we save it now in ntfs_create_inode.
Many commits affected, so no fixes tag.
This series fixes xfstest generic/423.
Konstantin Komarov (5):
fs/ntfs3: Rework ntfs_utf16_to_nls
fs/ntfs3: Refactor ntfs_readlink_hlp
fs/ntfs3: Refactor ntfs_create_inode
fs/ntfs3: Refactor ni_parse_reparse
fs/ntfs3: Refactor ntfs_read_mft
fs/ntfs3/dir.c | 19 +++----
fs/ntfs3/frecord.c | 9 ++--
fs/ntfs3/inode.c | 124 +++++++++++++++++++++------------------------
fs/ntfs3/ntfs_fs.h | 4 +-
4 files changed, 74 insertions(+), 82 deletions(-)
--
2.33.0
next reply other threads:[~2021-10-05 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 16:43 Konstantin Komarov [this message]
2021-10-05 16:47 ` [PATCH 1/5] fs/ntfs3: Rework ntfs_utf16_to_nls Konstantin Komarov
2021-10-17 8:10 ` Kari Argillander
2021-10-05 16:47 ` [PATCH 2/5] fs/ntfs3: Refactor ntfs_readlink_hlp Konstantin Komarov
2021-10-05 16:47 ` [PATCH 3/5] fs/ntfs3: Refactor ntfs_create_inode Konstantin Komarov
2021-10-05 16:48 ` [PATCH 4/5] fs/ntfs3: Refactor ni_parse_reparse Konstantin Komarov
2021-10-05 16:48 ` [PATCH 5/5] fs/ntfs3: Refactor ntfs_read_mft 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=98a166e4-f894-8bff-9479-05ef5435f1ed@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
all inboxes | Powered by JetHome®