From: Doug Ledford <dledford@redhat.com>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: Greg KH <greg@kroah.com>,
stable@vger.kernel.org,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH] IB/security: Restrict use of the write() interface
Date: Wed, 18 May 2016 15:59:21 -0400 [thread overview]
Message-ID: <8496b72b-c6ac-4d71-48c1-80d48991b6ca@redhat.com> (raw)
In-Reply-To: <CAJ3xEMjrNUYPmxSBm6J-w+3gr6Uv60tN-Y00=o4dk1aS9yEYuA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
On 05/18/2016 03:47 PM, Or Gerlitz wrote:
> On Wed, May 18, 2016 at 10:05 PM, Doug Ledford <dledford@redhat.com> wrote:
>> On 05/18/2016 02:59 PM, Or Gerlitz wrote:
>>> On Wed, May 18, 2016 at 8:57 PM, Doug Ledford <dledford@redhat.com> wrote:
>>>> On 05/18/2016 01:20 PM, Greg KH wrote:
>>>
>>>>> I don't understand, is this only for 3.14.x?
>>>
>>>> Yes.
>>>
>>> Wait, any reason not to apply it on all stable kernels?
>>
>> It already is.
>
> Is there a special reason you didn't add the CVE number to the change-log?
I didn't write the commit change log. I used the commit change log from
the original patch that didn't fail to apply.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2016-05-18 19:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 16:58 [PATCH] IB/security: Restrict use of the write() interface Doug Ledford
2016-05-18 17:20 ` Greg KH
2016-05-18 17:57 ` Doug Ledford
2016-05-18 18:59 ` Or Gerlitz
2016-05-18 19:05 ` Doug Ledford
2016-05-18 19:47 ` Or Gerlitz
2016-05-18 19:59 ` Doug Ledford [this message]
2016-05-18 20:36 ` Or Gerlitz
2016-05-18 21:42 ` Doug Ledford
-- strict thread matches above, loose matches on Subject: below --
2016-05-18 16:46 [PATCH] IB/security: restrict " Doug Ledford
2016-05-18 20:40 ` Kamal Mostafa
2016-05-21 5:32 ` Greg KH
2016-05-18 16:41 Doug Ledford
2016-05-18 20:42 ` Kamal Mostafa
2016-05-18 21:40 ` Doug Ledford
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=8496b72b-c6ac-4d71-48c1-80d48991b6ca@redhat.com \
--to=dledford@redhat.com \
--cc=gerlitz.or@gmail.com \
--cc=greg@kroah.com \
--cc=linux-rdma@vger.kernel.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox