From: Greg KH <gregkh@linuxfoundation.org>
To: Ashwin H <ashwinh@vmware.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
Steven Rostedt <srostedt@vmware.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"stable@kernel.org" <stable@kernel.org>,
Srivatsa Bhat <srivatsab@vmware.com>
Subject: Re: [PATCH v4.19.x] make 'user_access_begin()' do 'access_ok()'
Date: Wed, 13 May 2020 08:34:55 +0200 [thread overview]
Message-ID: <20200513063455.GA752913@kroah.com> (raw)
In-Reply-To: <89DE19F6-4CB0-4324-A630-C8574C8D591C@vmware.com>
On Wed, May 13, 2020 at 06:13:17AM +0000, Ashwin H wrote:
> This patch fixes CVE-2018-20669 in 4.19 tree.
Ok, but what does that mean for us?
You need to say why you are sending a patch, otherwise we will guess
wrong.
greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Ashwin H <ashwinh@vmware.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
Steven Rostedt <srostedt@vmware.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"stable@kernel.org" <stable@kernel.org>,
Srivatsa Bhat <srivatsab@vmware.com>
Subject: Re: [Intel-gfx] [PATCH v4.19.x] make 'user_access_begin()' do 'access_ok()'
Date: Wed, 13 May 2020 08:34:55 +0200 [thread overview]
Message-ID: <20200513063455.GA752913@kroah.com> (raw)
In-Reply-To: <89DE19F6-4CB0-4324-A630-C8574C8D591C@vmware.com>
On Wed, May 13, 2020 at 06:13:17AM +0000, Ashwin H wrote:
> This patch fixes CVE-2018-20669 in 4.19 tree.
Ok, but what does that mean for us?
You need to say why you are sending a patch, otherwise we will guess
wrong.
greg k-h
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Ashwin H <ashwinh@vmware.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@kernel.org" <stable@kernel.org>,
Srivatsa Bhat <srivatsab@vmware.com>,
"srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
Steven Rostedt <srostedt@vmware.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v4.19.x] make 'user_access_begin()' do 'access_ok()'
Date: Wed, 13 May 2020 08:34:55 +0200 [thread overview]
Message-ID: <20200513063455.GA752913@kroah.com> (raw)
In-Reply-To: <89DE19F6-4CB0-4324-A630-C8574C8D591C@vmware.com>
On Wed, May 13, 2020 at 06:13:17AM +0000, Ashwin H wrote:
> This patch fixes CVE-2018-20669 in 4.19 tree.
Ok, but what does that mean for us?
You need to say why you are sending a patch, otherwise we will guess
wrong.
greg k-h
next prev parent reply other threads:[~2020-05-13 6:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 1:49 [PATCH v4.19.x] make 'user_access_begin()' do 'access_ok()' ashwin-h
2020-05-13 1:49 ` ashwin-h
2020-05-13 1:49 ` [Intel-gfx] " ashwin-h
2020-05-13 5:55 ` Greg KH
2020-05-13 5:55 ` Greg KH
2020-05-13 5:55 ` [Intel-gfx] " Greg KH
2020-05-13 6:13 ` Ashwin H
2020-05-13 6:13 ` Ashwin H
2020-05-13 6:13 ` [Intel-gfx] " Ashwin H
2020-05-13 6:34 ` Greg KH [this message]
2020-05-13 6:34 ` Greg KH
2020-05-13 6:34 ` [Intel-gfx] " Greg KH
2020-05-13 17:08 ` Ashwin H
2020-05-13 17:08 ` Ashwin H
2020-05-13 17:08 ` [Intel-gfx] " Ashwin H
2020-05-27 15:31 ` Greg KH
2020-05-27 15:31 ` Greg KH
2020-05-27 15:31 ` [Intel-gfx] " Greg KH
2020-05-28 7:30 ` Ashwin H
2020-05-28 7:30 ` Ashwin H
2020-05-28 7:30 ` [Intel-gfx] " Ashwin H
2020-05-28 11:20 ` Ashwin H
2020-05-28 11:20 ` Ashwin H
2020-05-28 11:20 ` [Intel-gfx] " Ashwin H
2020-05-13 15:29 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
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=20200513063455.GA752913@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ashwinh@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=srivatsa@csail.mit.edu \
--cc=srivatsab@vmware.com \
--cc=srostedt@vmware.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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.