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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 28 Nov 2017 15:27:23 -0500
From:   Dennis Dalessandro <dennis.dalessandro@...el.com>
To:     Jason Gunthorpe <jgg@...pe.ca>,
        Bart Van Assche <Bart.VanAssche@....com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        "xavier_huwei@....com" <xavier_huwei@....com>,
        "linuxarm@...wei.com" <linuxarm@...wei.com>,
        "xavier.huwei@...wei.com" <xavier.huwei@...wei.com>,
        "xavier.huwei@....com" <xavier.huwei@....com>,
        "leon@...nel.org" <leon@...nel.org>,
        "dledford@...hat.com" <dledford@...hat.com>
Subject: Re: [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver

On 11/28/2017 2:33 PM, Jason Gunthorpe wrote:
> On Tue, Nov 28, 2017 at 06:50:44PM +0000, Bart Van Assche wrote:
>> On Tue, 2017-11-28 at 11:39 -0700, Jason Gunthorpe wrote:
>>> On Tue, Nov 28, 2017 at 08:20:09AM -0500, Dennis Dalessandro wrote:
>>>> I could resubmit just the series, or you could just pick the 4 driver
>>>> patches from patchworks whatever is easiest.
>>>
>>> I marked them in patchworks, but can you review the commit messages
>>> and make sure you think Linus will see them as rc material too?
>>
>> My understanding is that the rc stage is intended primarily for fixes for
>> bugs introduced during the merge window. For all patches that do not fix
>> bugs introduced during the merge window it should be evaluated carefully
>> whether or not these are important enough to be included in a rc pull request.
> 
> Oh? I thought it was more up to the maintainer discretion within some
> limits. Eg I thought we were running rdma more with the 'if it is OK
> for -stable, then it is OK -rc' kind of mentality?

That's always been my understanding.

> eg -rc is for stablization and bugfixing only, and not restricted only
> to bugs introduced in the latest merge window??

Makes no sense to me to have a hard restriction here. Security fixes, 
panics, and other serious bugs should certainly qualify. Of course that 
is subject to how complex the fix is.

-Denny

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ