linux-kernel - Re: [PATCH 4.9 000/105] 4.9.55-stable review

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:   Thu, 12 Oct 2017 12:39:52 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Shuah Khan <shuahkh@....samsung.com>
Cc:     lucien.xin@...il.com, "davem@...emloft.net" <davem@...emloft.net>,
        linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, linux@...ck-us.net,
        patches@...nelci.org, ben.hutchings@...ethink.co.uk,
        stable@...r.kernel.org
Subject: Re: [PATCH 4.9 000/105] 4.9.55-stable review

On Wed, Oct 11, 2017 at 04:54:51PM -0600, Shuah Khan wrote:
> On 10/11/2017 06:56 AM, Greg Kroah-Hartman wrote:
> > On Tue, Oct 10, 2017 at 06:58:40PM -0600, Shuah Khan wrote:
> >> On 10/10/2017 01:49 PM, Greg Kroah-Hartman wrote:
> >>> This is the start of the stable review cycle for the 4.9.55 release.
> >>> There are 105 patches in this series, all will be posted as a response
> >>> to this one.  If anyone has any issues with these being applied, please
> >>> let me know.
> >>>
> >>> Responses should be made by Thu Oct 12 19:24:56 UTC 2017.
> >>> Anything received after that time might be too late.
> >>>
> >>> The whole patch series can be found in one patch at:
> >>> 	kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.55-rc1.gz
> >>> or in the git tree and branch at:
> >>>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.9.y
> >>> and the diffstat can be found below.
> >>>
> >>> thanks,
> >>>
> >>> greg k-h
> >>>
> >>
> >> Compiled and booted. Networking is dead. I will bisect tomorrow and
> >> let you know what I find.
> >>
> >> r8169 is the suspect perhaps or some other change that affects it.
> >> Anyway more on this tomorrow.
> > 
> > Odd, let me know if you find anything.
> > 
> 
> git bisect came up with the following:
> 
> # first bad commit: [830e3de48a789f8d294a0d1461600f958afddde4]
> ip6_gre: skb_push ipv6hdr before packing the header in ip6gre_header
> 
> However, reverting this commit didn't work either. I might have to
> start bisect again. Update for now in case David or Xin Long can
> think of something that could possibly lead this failure. There are
> a few more patches in this space.

What is the symptom of the networking failure?  No networking device?
No dhcp request?  ipv4 or ipv6?  Differences in dmesg?

thanks,

greg k-h