From: "Theodore Ts'o" <tytso@mit.edu>
To: Anirudh Rayabharam <mail@anirudhrb.com>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
Dave Kleikamp <shaggy@austin.ibm.com>,
Alex Tomas <alex@clusterfs.com>, Andrew Morton <akpm@osdl.org>,
gregkh@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
syzbot+2dcfeaf8cb49b05e8f1a@syzkaller.appspotmail.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ext4: fix kernel infoleak via ext4_extent_header
Date: Wed, 16 Jun 2021 19:45:34 -0400 [thread overview]
Message-ID: <YMqNHnTofj9fR8IJ@mit.edu> (raw)
In-Reply-To: <20210506185655.7118-1-mail@anirudhrb.com>
On Fri, May 07, 2021 at 12:26:54AM +0530, Anirudh Rayabharam wrote:
> Initialize eh_generation of struct ext4_extent_header to prevent leaking
> info to userspace. Fixes KMSAN kernel-infoleak bug reported by syzbot at:
> http://syzkaller.appspot.com/bug?id=78e9ad0e6952a3ca16e8234724b2fa92d041b9b8
>
> Reported-by: syzbot+2dcfeaf8cb49b05e8f1a@syzkaller.appspotmail.com
> Fixes: a86c61812637 ("[PATCH] ext3: add extent map support")
> Signed-off-by: Anirudh Rayabharam <mail@anirudhrb.com>
Applied, thanks.
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Ts'o" <tytso@mit.edu>
To: Anirudh Rayabharam <mail@anirudhrb.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
Dave Kleikamp <shaggy@austin.ibm.com>,
syzbot+2dcfeaf8cb49b05e8f1a@syzkaller.appspotmail.com,
linux-ext4@vger.kernel.org, Alex Tomas <alex@clusterfs.com>
Subject: Re: [PATCH v2] ext4: fix kernel infoleak via ext4_extent_header
Date: Wed, 16 Jun 2021 19:45:34 -0400 [thread overview]
Message-ID: <YMqNHnTofj9fR8IJ@mit.edu> (raw)
In-Reply-To: <20210506185655.7118-1-mail@anirudhrb.com>
On Fri, May 07, 2021 at 12:26:54AM +0530, Anirudh Rayabharam wrote:
> Initialize eh_generation of struct ext4_extent_header to prevent leaking
> info to userspace. Fixes KMSAN kernel-infoleak bug reported by syzbot at:
> http://syzkaller.appspot.com/bug?id=78e9ad0e6952a3ca16e8234724b2fa92d041b9b8
>
> Reported-by: syzbot+2dcfeaf8cb49b05e8f1a@syzkaller.appspotmail.com
> Fixes: a86c61812637 ("[PATCH] ext3: add extent map support")
> Signed-off-by: Anirudh Rayabharam <mail@anirudhrb.com>
Applied, thanks.
- Ted
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2021-06-16 23:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 18:56 [PATCH v2] ext4: fix kernel infoleak via ext4_extent_header Anirudh Rayabharam
2021-05-06 18:56 ` Anirudh Rayabharam
2021-06-16 23:45 ` Theodore Ts'o [this message]
2021-06-16 23:45 ` Theodore Ts'o
2022-09-08 23:11 ` [PATCH] " eadavis
2022-12-26 14:31 ` How can this fix prevent information from leaking to user space and prevent the kernel from crashing? Lizhi Xu
2022-12-26 14:31 ` Lizhi Xu
2022-12-29 20:30 ` Eric Biggers
2022-12-29 20:30 ` Eric Biggers
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=YMqNHnTofj9fR8IJ@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@osdl.org \
--cc=alex@clusterfs.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@anirudhrb.com \
--cc=shaggy@austin.ibm.com \
--cc=syzbot+2dcfeaf8cb49b05e8f1a@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 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.