linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lizhi Xu <lizhi.xu@windriver.com>
To: <dvyukov@google.com>
Cc: <almaz.alexandrovich@paragon-software.com>,
	<linux-kernel@vger.kernel.org>, <ntfs3@lists.linux.dev>,
	<linux-fsdevel@vger.kernel.org>,
	<syzbot+a426cde6dee8c2884b0b@syzkaller.appspotmail.com>,
	<syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] [ntfs3?] KASAN: slab-out-of-bounds Read in mi_enum_attr
Date: Fri, 5 Jul 2024 21:52:50 +0800	[thread overview]
Message-ID: <20240705135250.3587041-1-lizhi.xu@windriver.com> (raw)
In-Reply-To: <CACT4Y+ZWjUE6-q1YF=ZaPjKgGZBw4JLD1v2DphSgCAVf1RzE8g@mail.gmail.com>

On Thu, 4 Jul 2024 15:44:02 +0200, Dmitry Vyukov wrote: 
> > index 53629b1f65e9..a435df98c2b1 100644
> > --- a/fs/ntfs3/record.c
> > +++ b/fs/ntfs3/record.c
> > @@ -243,14 +243,14 @@ struct ATTRIB *mi_enum_attr(struct mft_inode *mi, struct ATTRIB *attr)
> >                 off += asize;
> >         }
> >
> > -       asize = le32_to_cpu(attr->size);
> > -
> >         /* Can we use the first field (attr->type). */
> >         if (off + 8 > used) {
> >                 static_assert(ALIGN(sizeof(enum ATTR_TYPE), 8) == 8);
> >                 return NULL;
> >         }
> >
> > +       asize = le32_to_cpu(attr->size);
> > +
> >         if (attr->type == ATTR_END) {
> >                 /* End of enumeration. */
> >                 return NULL;
> 
> Hi Lizhi,
> 
> I don't see this fix mailed as a patch. Do you plan to submit it officially?
Hi Dmitry Vyukov,
Here: https://lore.kernel.org/all/20240202033334.1784409-1-lizhi.xu@windriver.com

--
Lizhi

       reply	other threads:[~2024-07-05 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACT4Y+ZWjUE6-q1YF=ZaPjKgGZBw4JLD1v2DphSgCAVf1RzE8g@mail.gmail.com>
2024-07-05 13:52 ` Lizhi Xu [this message]
2024-07-08  6:54   ` [syzbot] [ntfs3?] KASAN: slab-out-of-bounds Read in mi_enum_attr Dmitry Vyukov
2024-07-11  8:27     ` Konstantin Komarov
2024-08-20 10:53       ` lei lu
2024-02-01 15:17 syzbot

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=20240705135250.3587041-1-lizhi.xu@windriver.com \
    --to=lizhi.xu@windriver.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=dvyukov@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=syzbot+a426cde6dee8c2884b0b@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).