All of lore.kernel.org
 help / color / mirror / Atom feed
From: Siddh Raman Pant <code@siddh.me>
To: "syzbot" <syzbot+5f8dcabe4a3b2c51c607@syzkaller.appspotmail.com>
Cc: "akpm" <akpm@linux-foundation.org>, "anton" <anton@tuxera.com>,
	"chenxiaosong2" <chenxiaosong2@huawei.com>,
	"linux-kernel" <linux-kernel@vger.kernel.org>,
	"linux-ntfs-dev" <linux-ntfs-dev@lists.sourceforge.net>,
	"syzkaller-bugs" <syzkaller-bugs@googlegroups.com>,
	"yin31149" <yin31149@gmail.com>
Subject: Re: [syzbot] KASAN: use-after-free Read in ntfs_attr_find
Date: Fri, 26 Aug 2022 00:04:12 +0530	[thread overview]
Message-ID: <182d6488302.3488c7db67898.4109222238062172240@siddh.me> (raw)
In-Reply-To: <182d6469a5e.4e1cc3b067845.2722724258679993431@siddh.me>

On Fri, 26 Aug 2022 00:02:07 +0530  Siddh Raman Pant  wrote:
> This is incorrect. The issue is caused by:
> 9b75450d6c58 ("fs/ntfs3: Fix memory leak if fill_super failed")
>

Please ignore. I mistook this for another thread.

Extremely sorry,
Siddh

  reply	other threads:[~2022-08-25 18:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 18:25 [syzbot] KASAN: use-after-free Read in ntfs_attr_find syzbot
2022-08-25 18:32 ` Siddh Raman Pant
2022-08-25 18:34   ` Siddh Raman Pant [this message]
2022-08-26 12:27 ` [PATCH] ntfs: change check order " Hawkins Jiawei
2022-08-26 12:32   ` Hawkins Jiawei
2022-08-26 14:16     ` [syzbot] KASAN: use-after-free Read " syzbot
2022-08-26 15:15     ` [PATCH] ntfs: change check order " Dan Carpenter
2022-08-26 15:42       ` Hawkins Jiawei
2022-08-26 15:54         ` Hawkins Jiawei
2022-08-27  6:42         ` Dan Carpenter
2022-08-27  9:02           ` Hawkins Jiawei
2022-08-27 10:58             ` Dan Carpenter
2022-08-28 16:15               ` Hawkins Jiawei
2022-08-27  2:42     ` Andrew Morton
2022-08-27  8:38       ` Hawkins Jiawei
2022-08-27  1:28   ` chenxiaosong (A)
2022-08-27  7:51     ` Hawkins Jiawei
2022-08-27 14:49       ` Hawkins Jiawei
2022-08-29  9:51         ` Dan Carpenter

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=182d6488302.3488c7db67898.4109222238062172240@siddh.me \
    --to=code@siddh.me \
    --cc=akpm@linux-foundation.org \
    --cc=anton@tuxera.com \
    --cc=chenxiaosong2@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=syzbot+5f8dcabe4a3b2c51c607@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yin31149@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.