Return-Path: linux-nfs-owner@vger.kernel.org Received: from mailhub.sw.ru ([195.214.232.25]:3902 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932331Ab2AKRXh (ORCPT ); Wed, 11 Jan 2012 12:23:37 -0500 Message-ID: <4F0DC582.6030805@parallels.com> Date: Wed, 11 Jan 2012 21:23:14 +0400 From: Stanislav Kinsbursky MIME-Version: 1.0 To: Trond Myklebust CC: "linux-nfs@vger.kernel.org" , Pavel Emelianov , "neilb@suse.de" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , James Bottomley , "bfields@fieldses.org" , "davem@davemloft.net" , "devel@openvz.org" Subject: Re: [PATCH 0/5] NFS: create blocklayout pipe per network namesapce context References: <20111129090754.20730.64567.stgit@localhost6.localdomain6> <1325285705.10984.4.camel@lade.trondhjem.org> <1325797111.11084.22.camel@lade.trondhjem.org> <4F0C35F3.7060508@parallels.com> <1326299003.17212.7.camel@lade.trondhjem.org> In-Reply-To: <1326299003.17212.7.camel@lade.trondhjem.org> Content-Type: text/plain; charset=UTF-8; format=flowed Sender: linux-nfs-owner@vger.kernel.org List-ID: 11.01.2012 20:23, Trond Myklebust пишет: > On Tue, 2012-01-10 at 16:58 +0400, Stanislav Kinsbursky wrote: >> 06.01.2012 00:58, Trond Myklebust пишет: >>> The second problem that was highlighted was the fact that as they stand >>> today, these patchsets do not allow for bisection. When we hit the Oops, >>> I had Bryan try to bisect where the problem arose. He ended up pointing >>> at the patch "SUNRPC: handle RPC client pipefs dentries by network >>> namespace aware routine", which is indeed the cause, but which is one of >>> the _dependencies_ for all the PipeFS notifier patches that fix the >>> problem. >>> >> >> I'm confused here. Does this means, that I have to fix patch "SUNRPC: handle RPC >> client pipefs dentries by network namespace aware routine" to make it able to >> bisect? > > What I mean is that currently, I have various ways to Oops the kernel > when I apply "SUNRPC: handle RPC client pipefs dentries by network > namespace aware routine" before all these other followup patches are > applied. > > One way to could fix this, might be to add dummy versions of > rpc_pipefs_notifier_register()/unregister() so that "NFS: idmap PipeFS > notifier introduced" and the other such patches can be applied without > compilation errors or Oopses before the "handle RPC client pipefs > dentries..." patch is applied. The latter could then enable the real > rpc_pipefs_notifier_register()/.... > > The point is to not have these patches add _known_ bugs to the kernel at > any point, so that someone who is trying to track down an unknown bug > via "git bisect" doesn't have to also cope with these avoidable > issues... > Ok, thanks for explanation. I've sent rebased "v2" of the patch set, contains updated patch "SUNRPC: handle RPC client pipefs dentries by network namespace aware routine", which, I believe, fixes oops, spotted by Bryan (it was caused by excessive call of rpc_put_mount() on PipeFS dentries unlink). So, if I'm not mistaken here, there's no need in implementing of dummy versions of rpc_pipefs_notifier_(un)register() or any other dummy stuff. BTW, it looks like that in last 2 days I've sent all updates to the issues you pointed out. If not, please, ping me once more. -- Best regards, Stanislav Kinsbursky