netdev - Re: stable/linux-4.10.y build: 203 builds: 3 failed, 200 passed, 3 errors, 5 warnings (v4.10.16)

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:   Mon, 15 May 2017 06:57:51 -0700
From:   Eric Dumazet <edumazet@...gle.com>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     "kernelci.org bot" <bot@...nelci.org>,
        Kernel Build Reports Mailman List 
        <kernel-build-reports@...ts.linaro.org>,
        gregkh <gregkh@...uxfoundation.org>, stable@...r.kernel.org,
        Networking <netdev@...r.kernel.org>
Subject: Re: stable/linux-4.10.y build: 203 builds: 3 failed, 200 passed, 3
 errors, 5 warnings (v4.10.16)

On Mon, May 15, 2017 at 6:55 AM, Arnd Bergmann <arnd@...db.de> wrote:
> On Mon, May 15, 2017 at 3:39 PM, Eric Dumazet <edumazet@...gle.com> wrote:
>> On Mon, May 15, 2017 at 5:57 AM, Arnd Bergmann <arnd@...db.de> wrote:
>>> On Sun, May 14, 2017 at 3:48 PM, kernelci.org bot <bot@...nelci.org> wrote:
>>>
>>>  int sock_setsockopt(struct socket *sock, int level, int op,
>>>
>>> This commit is not marked 'Cc: stable' upstream, but is referenced
>>> in the one that was backported and looks like it might be appropriate
>>> for stable as well. Eric, can you clarify?
>>>
>>
>> Hi Arnd
>>
>> Yes, it looks like stable would need this small extract from 158f323b9868,
>> removing the parameter from sock_edemux macro
>
> Ok, and the rest of 158f323b9868 should not go into stable, right?
>

I do not believe this is a stable candidate.

A stable candidate coming from me would have a Fixes: tag