Date: Tue, 22 Mar 2016 12:12:22 +0100
From: Borislav Petkov <bp@alien8.de>
To: Chris Bainbridge <chris.bainbridge@gmail.com>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
        mchehab@infradead.org, markus@trippelsdorf.de, tony.luck@intel.com
Subject: Re: [BUG] packet loss with PROVE_LOCKING, bisected to EDAC fix
Message-ID: <20160322111222.GC3688@pd.tnic>
References: <20160321214209.GA8480@localhost>
 <20160322053154.GA3688@pd.tnic>
 <20160322091656.GA11313@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20160322091656.GA11313@localhost>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 701
Lines: 19

On Tue, Mar 22, 2016 at 09:16:56AM +0000, Chris Bainbridge wrote:
> Good question. The patch looks pretty innocuous but it is for a lockdep
> issue and the bug only appears when lockdep config options are enabled.
> Could it somehow have broken a lock used to synchronise packet rx?

How? EDAC and net don't have anything in common...

> Reverting over 4.5 does fix the packet loss issue.

Peter makes sense to me. If he's right, if you build a kernel with
CONFIG_EDAC=n and PROVE_LOCKING=y and do your test again, you should
be seeing that packet loss again... because EDAC with the fix won't be
there to disable lockdep.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.