public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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 17:42:34 -0400	[thread overview]
Message-ID: <673ebb5e-80fa-f4d5-1fbd-59e8a27e0f86@redhat.com> (raw)
In-Reply-To: <CAJ3xEMj4Q0Y1OsEqJaoEpWjitaLDy0G8qmLBrPo30JCc596Kyw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

On 05/18/2016 04:36 PM, Or Gerlitz wrote:
> On Wed, May 18, 2016 at 10:59 PM, Doug Ledford <dledford@redhat.com> wrote:
>> On 05/18/2016 03:47 PM, Or Gerlitz wrote:
> 
>>> 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.
> 
> I mean on the original patch when you added your maintainer S.O.B

Because of an issue of confusion.  Red Hat had an internal CVE assigned,
but I didn't know I could put that on here.  There wasn't an assigned
MITRE CVE yet.  Then people noticed the patch, someone requested a CVE
on the mitre list, and another one got assigned.  Red Hat has since
dropped their internal CVE and adopted the mitre CVE.  That probably
would have been avoided had I known to put Red Hat's internal CVE on there.


-- 
Doug Ledford <dledford@redhat.com>
              GPG KeyID: 0E572FDD



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

  reply	other threads:[~2016-05-18 21:42 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
2016-05-18 20:36             ` Or Gerlitz
2016-05-18 21:42               ` Doug Ledford [this message]
  -- 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=673ebb5e-80fa-f4d5-1fbd-59e8a27e0f86@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