netdev - Re: [E1000-devel] ixgbe 4.4.6 detected crash

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>] [day] [month] [year] [list]

Message-ID: <CAKgT0Ufdq=KPpHbVbOPL_m24Y=yU5-TYc2YcCuag6e3T9HfsdA@mail.gmail.com>
Date:   Tue, 1 Nov 2016 11:43:20 -0700
From:   Alexander Duyck <alexander.duyck@...il.com>
To:     Matias Vara <matiasevara@...il.com>
Cc:     "e1000-devel@...ts.sourceforge.net" 
        <e1000-devel@...ts.sourceforge.net>,
        Netdev <netdev@...r.kernel.org>,
        David Miller <davem@...emloft.net>
Subject: Re: [E1000-devel] ixgbe 4.4.6 detected crash

On Tue, Nov 1, 2016 at 8:16 AM, Matias Vara <matiasevara@...il.com> wrote:
> Hi everyone, I am facing an issue with the ixgbe 10G Network card version
> 4.4.6. I am in XenServer which is based on CentOS and the issue only appers
> on FCOE machines. I am getting the following message during crash:
>
> [2016-10-28 09:43:58 UTC] [ 68.789174] kernel BUG at
> /obj/RPM_BUILD_DIRECTORY/driver-intel-ixgbe-4.4.6/src/ixgbe_fcoe.c:440!
>
> Someone knows what is happening?To track this bug, I opened the ticket
> #543. Please go to the ticket for more details.
>
> Thanks in advance, Matias.

I just replied to your bug but I will reply here as well.

The 4.4 kernel has a bug that is fixed by the following commit:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=224516b3a798

I would recommend back-porting it into your kernel and we probably
need to have this queued up for linux-stable as well.

>From what I can tell I overlooked adding the following which should
have probably been included in the original patch.
Fixes: a6e544b0a88b ("flow_dissector: Jump to exit code in __skb_flow_dissect")

Thanks.

- Alex