mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Yousef Alhouseen <alhouseenyousef@gmail.com>
Cc: <ntfs3@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>,
	<syzbot+4b4ec878e25fafefa70f@syzkaller.appspotmail.com>
Subject: Re: [PATCH] ntfs3: reject empty iomap before reading its LCN
Date: Wed, 16 Sep 2026 13:09:34 +0200	[thread overview]
Message-ID: <9294cf71-dddc-49bd-90c0-29fbcbc2815b@paragon-software.com> (raw)
In-Reply-To: <20260630211743.50400-1-alhouseenyousef@gmail.com>

On 6/30/26 23:17, Yousef Alhouseen wrote:

> attr_data_get_block() can return success with a zero run length when no
> cached or on-disk mapping covers a read VCN. In that case it does not
> initialize the LCN output.
>
> Check the returned length before comparing the LCN against the special
> mapping values. This preserves the existing -EINVAL result for an empty
> mapping without passing an uninitialized LCN to the comparisons.
>
> Fixes: ecbb433f9a8e ("fs/ntfs3: fold file size handling into ntfs_set_size()")
> Reported-by: syzbot+4b4ec878e25fafefa70f@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=4b4ec878e25fafefa70f
> Cc: stable@vger.kernel.org
> Signed-off-by: Yousef Alhouseen <alhouseenyousef@gmail.com>
> ---
>   fs/ntfs3/inode.c | 7 ++-----
>   1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/fs/ntfs3/inode.c b/fs/ntfs3/inode.c
> index c43101cc064d..a428f03a695d 100644
> --- a/fs/ntfs3/inode.c
> +++ b/fs/ntfs3/inode.c
> @@ -777,6 +777,8 @@ static int ntfs_iomap_begin(struct inode *inode, loff_t offset, loff_t length,
>          if (err) {
>                  return err;
>          }
> +       if (!clen)
> +               return -EINVAL;
>
>          if (lcn == EOF_LCN) {
>                  /* request out of file. */
> @@ -811,11 +813,6 @@ static int ntfs_iomap_begin(struct inode *inode, loff_t offset, loff_t length,
>                  return 0;
>          }
>
> -       if (!clen) {
> -               /* broken file? */
> -               return -EINVAL;
> -       }
> -
>          iomap->bdev = inode->i_sb->s_bdev;
>          iomap->offset = offset;
>          iomap->length = ((loff_t)clen << cluster_bits) - off;
> --
> 2.55.0

Hello,

Sorry for the delay.
Your patch is applied, thank you.

Regards,
Konstantin


      reply	other threads:[~2026-09-16 11:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 21:17 Yousef Alhouseen
2026-09-16 11:09 ` Konstantin Komarov [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=9294cf71-dddc-49bd-90c0-29fbcbc2815b@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=alhouseenyousef@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+4b4ec878e25fafefa70f@syzkaller.appspotmail.com \
    /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®