Re: kernel BUG at fs/dcache.c:648! with v3.11-7890-ge5c832d

[Linus Torvalds]

On Tue, Sep 10, 2013 at 6:48 PM, Waiman Long <waiman.long@xxxxxx> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/