From: liubaolin <liubaolin12138@163.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: hyc.lee@gmail.com, ntfs@lists.linux.dev,
linux-kernel@vger.kernel.org, Baolin Liu <liubaolin@kylinos.cn>
Subject: Re: [PATCH v2 0/5] ntfs: fix incorrect error codes returned to callers
Date: Sat, 5 Sep 2026 18:56:14 +0800 [thread overview]
Message-ID: <f841b07c-d2e7-4547-a833-101e2ff80af8@163.com> (raw)
In-Reply-To: <CAKYAXd9V_rPOaoy2keiWxeJOf2Op=zr=c36hgJug6m+HUDhv2g@mail.gmail.com>
在 2026/9/4 22:22, Namjae Jeon 写道:
> On Fri, Sep 4, 2026 at 6:01 PM Baolin Liu <liubaolin12138@163.com> wrote:
>>
>> From: Baolin Liu <liubaolin@kylinos.cn>
>>
>> Changes in v2:
>> - Patch 2: Fixed ntfs_extent_inode_open() to use ERR_PTR() instead of NULL,
>> so it can properly propagate error codes (suggested by maintainer).
>> Updated ntfs_inode_attach_all_extents() to use IS_ERR()/PTR_ERR() to
>> preserve the actual error code from ntfs_extent_inode_open().
>> - Patches 1, 3, 4, 5: No code changes, added Reviewed-by tag from Hyunchul Lee
>>
>> Five places in fs/ntfs/ return the wrong error code: a real errno is
>> replaced by -1 or by a hardcoded substitute, so callers and userspace see
>> something unrelated to what actually went wrong. The fixes are
>> independent of each other.
>>
>> Patch 1 is different from the rest: there the error is not just
>> mislabelled, it is not seen as an error at all. -1 is what a normal
>> comparison returns for "collates before", so ntfs_ie_lookup() acts on it
>> as a tree-descent hint, and a malformed entry in $Reparse/$R or $ObjId/$O
>> is silently treated as a lookup miss instead of being reported.
>>
>> Patch 2 fixes ntfs_extent_inode_open() which had two bugs: it treated
>> map_mft_record() failure as success, and returned NULL for all errors
>> (losing error information). Now it returns ERR_PTR() with the actual
>> error code (-EIO, -ENOMEM, -EINVAL).
>>
>> Patch 3 fixes a -1 return in inode.c that reaches userspace as EPERM.
>> It loses ENOSPC among others, so a full volume misreports create(),
>> mkdir() and link().
>>
>> Patches 4 and 5 restore errors that are already available as an ERR_PTR.
>> Both collapse -ENOMEM into something else, so an allocation failure is
>> misreported.
>>
>> No control flow is changed; every callee already returned these codes.
>>
>> Based on ntfs-next (0fecc393f206).
>>
>> Baolin Liu (5):
>> ntfs: return -EINVAL from ntfs_collate_ntofs_ulongs() on bad length
>> ntfs: fix error handling in ntfs_extent_inode_open and propagate errors
>> ntfs: preserve the truncate error in ntfs_enlarge_attribute()
>> ntfs: propagate the map_mft_record() error in ntfs_attrlist_entry_add()
>> ntfs: propagate the ntfs_attr_iget() error in update_reparse_data()
> Applied them to #ntfs-next except 0002 patch("ntfs: fix error handling
> in ntfs_extent_inode_open and propagate errors").
> Thanks!
Hi Namjae,
Thanks for applying them.I'll send the 0002 patch alone as v3.
Thanks,
Baolin.
prev parent reply other threads:[~2026-09-05 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 9:00 Baolin Liu
2026-09-04 9:00 ` [PATCH v2 1/5] ntfs: return -EINVAL from ntfs_collate_ntofs_ulongs() on bad length Baolin Liu
2026-09-04 9:00 ` [PATCH v2 2/5] ntfs: fix error handling in ntfs_extent_inode_open and propagate errors Baolin Liu
2026-09-04 14:20 ` Namjae Jeon
2026-09-05 10:50 ` liubaolin
2026-09-04 9:00 ` [PATCH v2 3/5] ntfs: preserve the truncate error in ntfs_enlarge_attribute() Baolin Liu
2026-09-04 9:00 ` [PATCH v2 4/5] ntfs: propagate the map_mft_record() error in ntfs_attrlist_entry_add() Baolin Liu
2026-09-04 9:00 ` [PATCH v2 5/5] ntfs: propagate the ntfs_attr_iget() error in update_reparse_data() Baolin Liu
2026-09-04 14:22 ` [PATCH v2 0/5] ntfs: fix incorrect error codes returned to callers Namjae Jeon
2026-09-05 10:56 ` liubaolin [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=f841b07c-d2e7-4547-a833-101e2ff80af8@163.com \
--to=liubaolin12138@163.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubaolin@kylinos.cn \
--cc=ntfs@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®