From: Waiman Long <waiman.long@hp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mace Moneta <moneta.mace@gmail.com>,
Josh Boyer <jwboyer@gmail.com>, Al Viro <viro@zeniv.linux.org.uk>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at fs/dcache.c:648! with v3.11-7890-ge5c832d
Date: Tue, 10 Sep 2013 21:48:54 -0400 [thread overview]
Message-ID: <522FCC06.3090907@hp.com> (raw)
In-Reply-To: <CA+55aFzFWbCGqaGe1BbuBY_j+0xK-UfYEJddjSWriufs0Q5PmQ@mail.gmail.com>
On 09/10/2013 04:25 PM, Linus Torvalds wrote:
> On Tue, Sep 10, 2013 at 12:57 PM, Mace Moneta<moneta.mace@gmail.com> wrote:
>> The (first) patch looks good; no recurrence. It has only taken 3-5 minutes
>> before, and I've been up for about half an hour now.
> Ok, good. It's pushed out.
>
> Al, your third pile of VFS stuff is also merged. Waiman, that means
> that your RCU path creation stuff is in. What else did you have
> pending for scalability?
>
> Linus
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. Then all the
name lookup and translation code can use the new primitives as they
don't change any of the protected structures. This will prevent one
sequence number check failure from cascading into a series of failures
because of the sequence number change. I will have a patch ready by
tomorrow morning.
Regards,
Longman
next prev parent reply other threads:[~2013-09-11 1:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 17:14 kernel BUG at fs/dcache.c:648! with v3.11-7890-ge5c832d Josh Boyer
2013-09-10 17:33 ` Linus Torvalds
2013-09-10 17:39 ` Josh Boyer
2013-09-10 17:47 ` Linus Torvalds
2013-09-10 18:25 ` Linus Torvalds
[not found] ` <CAMfhy93EoDohCrV+ykj6b+R9QSCTdiPtvSpJpe3SH=ot_1LWMg@mail.gmail.com>
2013-09-10 18:32 ` Linus Torvalds
[not found] ` <CAMfhy92u1GFvTrO+8SNp8hoEBEHcd7Z-3mw+79rv8+2yYqa+ow@mail.gmail.com>
[not found] ` <CAMfhy90vEu2_hfoOnzB+ZOit4HNmKex2WObmztcY7R4+PBwd7w@mail.gmail.com>
2013-09-10 20:25 ` Linus Torvalds
2013-09-10 21:51 ` Josh Boyer
2013-09-11 1:48 ` Waiman Long [this message]
2013-09-11 3:22 ` Linus Torvalds
2013-09-11 3:56 ` Al Viro
2013-09-11 4:12 ` Linus Torvalds
2013-09-10 18:43 ` Al Viro
2013-09-10 19:01 ` Linus Torvalds
2013-09-10 19:13 ` Al Viro
2013-09-10 19:27 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=522FCC06.3090907@hp.com \
--to=waiman.long@hp.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moneta.mace@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.