Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752743Ab3CVABv (ORCPT ); Thu, 21 Mar 2013 20:01:51 -0400 Received: from mail-ve0-f177.google.com ([209.85.128.177]:38755 "EHLO mail-ve0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751813Ab3CVABt (ORCPT ); Thu, 21 Mar 2013 20:01:49 -0400 MIME-Version: 1.0 In-Reply-To: References: <20130321192935.GY21522@ZenIV.linux.org.uk> <20130321202635.GA16406@redhat.com> <20130321203639.GC16406@redhat.com> <20130321204704.GZ21522@ZenIV.linux.org.uk> <20130321210255.GD16406@redhat.com> <20130321221256.GA30620@redhat.com> <20130321233630.GE21522@ZenIV.linux.org.uk> Date: Thu, 21 Mar 2013 17:01:49 -0700 X-Google-Sender-Auth: Ba3URKzKc35s455kZBPoV4k01bI Message-ID: Subject: Re: VFS deadlock ? From: Linus Torvalds To: Al Viro Cc: Dave Jones , Linux Kernel , "Eric W. Biederman" 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: 1028 Lines: 23 On Thu, Mar 21, 2013 at 4:58 PM, Linus Torvalds wrote: > > So yes, it's against the rules, and we get that deadlock right now, > but one solution would be to just allow this particular case. The > patch for the deadlock looks dead simple: It should go without saying that that whitespace-damaged patch is entirely untested. But especially since we need to back-port whatever fix, it would be good if we could make the fix be something as simple as this. Because I don't believe we really want to backport some big network-namespace reorganization. This is, of course, all assuming that hardlinked directories are ok if we can just guarantee the absence of loops. If there's some other reason why they'd be problematic, we're screwed. 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/