From: Greg KH <gregkh@linuxfoundation.org>
To: xu xin <cgel.zte@gmail.com>
Cc: anton@tuxera.com, linux-ntfs-dev@lists.sourceforge.net,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
xu.xin16@zte.com.cn, linux-fsdevel@vger.kernel.org
Subject: Re: Bug report: ntfs_read_block may crash system
Date: Thu, 23 Jun 2022 09:55:10 +0200 [thread overview]
Message-ID: <YrQcXg89eO0Y/pgZ@kroah.com> (raw)
In-Reply-To: <20220623033635.973929-1-xu.xin16@zte.com.cn>
On Thu, Jun 23, 2022 at 03:36:35AM +0000, xu xin wrote:
> >From Zeal Robot <zealci@zte.com.cn>
>
> Hi! Zeal Robot found a potential risky bug about NTFS under the help of syzkaller.
> This will cause OS crash when CONFIG_NTFS_FS is set and panic_on_oops is on.
Do you have a proposed fix for this as you can easily reproduce this?
And it looks like you need root permisions for this, right?
thanks,
greg k-h
next prev parent reply other threads:[~2022-06-23 7:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 3:36 Bug report: ntfs_read_block may crash system xu xin
2022-06-23 3:51 ` [PATCH] fs/ntfs: fix BUG_ON of ntfs_read_block() cgel.zte
2022-06-23 7:57 ` Greg KH
2022-06-23 8:57 ` CGEL
2022-06-23 7:57 ` Greg KH
2022-06-23 8:59 ` CGEL
2022-06-23 7:55 ` Greg KH [this message]
2022-06-23 9:49 ` [PATCH v2] " cgel.zte
2022-06-23 17:08 ` Eric Biggers
2022-06-24 2:33 ` Namjae Jeon
2022-06-24 3:55 ` CGEL
[not found] ` <7FBC6FD2-5D60-4EB8-96D5-A6014D271950@tuxera.com>
2022-06-24 14:37 ` Namjae Jeon
2022-06-24 15:26 ` Anton Altaparmakov
2022-07-05 7:47 ` CGEL
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 3:28 Bug report: ntfs_read_block may crash system xu xin
2022-06-23 3:27 xu xin
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=YrQcXg89eO0Y/pgZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anton@tuxera.com \
--cc=cgel.zte@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=stable@vger.kernel.org \
--cc=xu.xin16@zte.com.cn \
/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