From: Andrew Morton <akpm@linux-foundation.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: arnd@arndb.de, christian@brauner.io, deepa.kernel@gmail.com,
glider@google.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
Oleg Nesterov <oleg@redhat.com>,
syzbot <syzbot+0d602a1b0d8c95bdf299@syzkaller.appspotmail.com>
Subject: Re: KMSAN: kernel-infoleak in copy_siginfo_to_user (2)
Date: Tue, 28 May 2019 12:47:46 -0700 [thread overview]
Message-ID: <20190528124746.ac703cd668ca9409bb79100b@linux-foundation.org> (raw)
In-Reply-To: <87woia5vq3.fsf@xmission.com>
On Tue, 28 May 2019 12:34:28 -0500 ebiederm@xmission.com (Eric W. Biederman) wrote:
> Didn't someone already provide a fix for this one?
>
> I thought I saw that hit your tree a while ago. I am looking in
> ptrace.c and I don't see anything that would have fixed this issue.
I can't find anything which might have addressed this.
> If there isn't a fix in the queue I will take a stab at it.
Thanks.
next prev parent reply other threads:[~2019-05-28 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 10:07 KMSAN: kernel-infoleak in copy_siginfo_to_user (2) syzbot
2019-05-28 17:34 ` Eric W. Biederman
2019-05-28 19:47 ` Andrew Morton [this message]
2019-05-29 1:21 ` [PATCH] signal/ptrace: Don't leak unitialized kernel memory with PTRACE_PEEK_SIGINFO Eric W. Biederman
2019-06-04 18:33 ` Andrei Vagin
2019-06-04 19:42 ` Eric W. Biederman
2019-06-10 19:39 ` 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=20190528124746.ac703cd668ca9409bb79100b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=christian@brauner.io \
--cc=deepa.kernel@gmail.com \
--cc=ebiederm@xmission.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=syzbot+0d602a1b0d8c95bdf299@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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.