From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Watts Subject: Re: [BUG]: fsnotify oops on 3.5.2 Date: Mon, 27 Aug 2012 15:57:08 -0500 Message-ID: <20120827205706.GA18063@ymail.com> References: <20120826204453.GA10707@ymail.com> <20120827053201.GB27551@yanx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, rostedt@goodmis.org To: Guo Chao Return-path: Content-Disposition: inline In-Reply-To: <20120827053201.GB27551@yanx> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Aug 27, 2012 at 01:32:01PM +0800, Guo Chao wrote: > Problematic instruction seems to be this one: > > 85 73 74 test %esi,0x74(%ebx) Guo: Thank you very much for the very detailed response on the meaning of the oops - it was very educational for me. I did have one question, however. How were you able to identify the relevant section in the source code? > But have no idea how 'struct path' contained a NULL > 'struct vfsmount *' ... ... > As Steven points out, this could be a bug in the overlayfs code. After getting a 2nd oops last night, I rebuilt 3.5.2 w/o overlafs in order to test that theory. Though I am unable to reproduce at will, 2 oopses in 60 hours suggests I should not have to wait too long for a verdict. I will follow-up in a couple of days one way or the other. ~ Andy