public inbox for ntfs3@lists.linux.dev
 help / color / mirror / Atom feed
From: lei lu <llfamsec@gmail.com>
To: llfamsec@gmail.com
Cc: almaz.alexandrovich@paragon-software.com, lizhi.xu@windriver.com,
	ntfs3@lists.linux.dev,
	syzbot+a426cde6dee8c2884b0b@syzkaller.appspotmail.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH v2] ntfs3: Add bounds checking to mi_enum_attr()
Date: Fri, 23 Aug 2024 21:49:11 +0800	[thread overview]
Message-ID: <20240823134911.211897-1-llfamsec@gmail.com> (raw)
In-Reply-To: <20240823130503.177723-1-llfamsec@gmail.com>

Hi all,

This patch ignores the last attr is just 8 bytes and type field
is ATTR_END. I have already send V2.

  reply	other threads:[~2024-08-23 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 13:05 [PATCH] ntfs3: Add bounds checking to mi_enum_attr() lei lu
2024-08-23 13:49 ` lei lu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-23 13:39 [PATCH v2] " lei lu
2024-08-26  7:06 ` 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=20240823134911.211897-1-llfamsec@gmail.com \
    --to=llfamsec@gmail.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=lizhi.xu@windriver.com \
    --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