lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 08 May 2017 13:08:24 +0200
From:   Bjørn Mork <bjorn@...k.no>
To:     "Baxter\, Jim" <jim_baxter@...tor.com>
Cc:     <linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        Oliver Neukum <oliver@...kum.org>
Subject: Re: [PATCH V1 1/1] net: cdc_ncm: Fix TX zero padding

"Baxter, Jim" <jim_baxter@...tor.com> writes:

> Bjørn Mork <bjorn@...k.no> writes:
>> 
>> Ouch! Thanks for finding this.  This should go to the stable queue as
>> well.
>> 
>> Reviewed-by: Bjørn Mork <bjorn@...k.no>
>> 
>
> Do I need to submit this to the stable queue myself?

No, davem will handle that.

That is, assuming that you had posted this to netdev in the first
place... Sorry, I just assumed you did without verifying it when I
replied.  You will have to repost the patch to the appropriate
recepients.  Use

 scripts/get_maintainer.pl drivers/net/usb/cdc_ncm.c

for that.  Feel free to include my Reviewed-by tag. And if you mark the
patch for "stable" somewhere outside the commit message, then davem will
pick that up and add it to his stable queue in patchwork. I don't know
if there is any officially documented way to do this, but a "stable" tag
inside the [] brackets in the subject, or a comment below the --- marker,
usually works fine.

Note that the "Cc: stable..." method isn't used for netdev patches. See
https://www.kernel.org/doc/Documentation/networking/netdev-FAQ.txt


Bjørn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ