Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932704Ab3CHAVQ (ORCPT ); Thu, 7 Mar 2013 19:21:16 -0500 Received: from mail-ve0-f173.google.com ([209.85.128.173]:57715 "EHLO mail-ve0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759872Ab3CHAVO (ORCPT ); Thu, 7 Mar 2013 19:21:14 -0500 MIME-Version: 1.0 In-Reply-To: <20130307223610.GA2494@redhat.com> References: <20130307213819.GB19543@redhat.com> <20130307220333.GA31039@redhat.com> <20130307223610.GA2494@redhat.com> Date: Thu, 7 Mar 2013 16:21:13 -0800 X-Google-Sender-Auth: -SycsNo9jTdi7R0RZf72hisQni0 Message-ID: Subject: Re: pipe_release oops. From: Linus Torvalds To: Dave Jones , Linus Torvalds , Linux Kernel , Al Viro Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 975 Lines: 23 On Thu, Mar 7, 2013 at 2:36 PM, Dave Jones wrote: > > The hits keep on coming.. > > [ 255.609172] BUG: unable to handle kernel NULL pointer dereference at 0000000000000064 > [ 255.610393] IP: [] pipe_release+0x42/0xd0 Ok, I think this is the same issue as your fasync thing. So add a "if (pipe) { }" in pipe_release() too. It's a bit odd, becuse we always allocate an inode->i_pipe whenever we associate the file with any of the pipe operations, so I don't see how that NULL i_pipe happens. But we do have that "free_pipe_info() if there are no readers or writers" logic and I bet that's what triggers this somehow. I just don't see what the exact sequence is. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/