Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753811Ab3IKDW7 (ORCPT ); Tue, 10 Sep 2013 23:22:59 -0400 Received: from mail-vb0-f44.google.com ([209.85.212.44]:65016 "EHLO mail-vb0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753499Ab3IKDW5 (ORCPT ); Tue, 10 Sep 2013 23:22:57 -0400 MIME-Version: 1.0 In-Reply-To: <522FCC06.3090907@hp.com> References: <522FCC06.3090907@hp.com> Date: Tue, 10 Sep 2013 20:22:56 -0700 X-Google-Sender-Auth: weGAlZ8VeNiVMRNueFfsKjJAZJc Message-ID: Subject: Re: kernel BUG at fs/dcache.c:648! with v3.11-7890-ge5c832d From: Linus Torvalds To: Waiman Long Cc: Mace Moneta , Josh Boyer , Al Viro , "Linux-Kernel@Vger. Kernel. Org" 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: 726 Lines: 18 On Tue, Sep 10, 2013 at 6:48 PM, Waiman Long wrote: > > I need to clean up some comments in the code. The other thing that I want to > do is to introduce read_seqlock/read_sequnlock() primitives that do the > locking without incrementing the sequence number. I don't understand. That's the whole *point* of sequence numbers. The read-locker doesn't ever change the number, only the write-locker does. So I don't see what you would change. 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/