From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1162382AbbKTR4r (ORCPT ); Fri, 20 Nov 2015 12:56:47 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:50288 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759959AbbKTR4q (ORCPT ); Fri, 20 Nov 2015 12:56:46 -0500 Date: Fri, 20 Nov 2015 17:56:44 +0000 From: Al Viro To: Christophe Leroy Cc: "linux-kernel@vger.kernel.org" , LinuxPPC-dev , linux-fsdevel , BOUET Serge , BARABAN Luc Subject: Re: Recurring Oops in link_path_walk() Message-ID: <20151120175643.GM22011@ZenIV.linux.org.uk> References: <564F536F.9080109@c-s.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <564F536F.9080109@c-s.fr> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 20, 2015 at 06:07:59PM +0100, Christophe Leroy wrote: > Al, > > We've been running Kernel 3.18 for several monthes on our embedded > boards, and we have a recurring Oops in link_path_walk() > It doesn't happen very often (approximatly once every month on one > board among a set of 50 boards, never the same board). > > Here below is the last oops I got, with kernel 3.18.22. It crashes > at address 0xc00b75ac. Here below is the full desassembly of > link_path_walk() so that you can see exactly the offending line. > > The address it fails at is always the same (link_path_walk+0x414) > but the oopsing data address is each time different. I added all > Oops I got below after the disassembly (on different sub-versions of > 3.18). Looks like garbage in dentry->d_inode, assuming that reconstruction of the mapping of line numbers to addresses is correct... Not sure it is, though; what's more, just how does LR manage to point to the insn right after the call of dput(), of all things?