From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH] debugfs: Fix corrupted loop in debugfs_remove_recursive
Date: Tue, 10 Jun 2014 13:23:02 -0700 [thread overview]
Message-ID: <20140610202302.GB20499@kroah.com> (raw)
In-Reply-To: <20140610093357.7ef3792b@gandalf.local.home>
On Tue, Jun 10, 2014 at 09:33:57AM -0400, Steven Rostedt wrote:
> On Mon, 9 Jun 2014 14:06:07 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > [ I'm currently running my tests on it now, and so far, after a few
> > hours it has yet to blow up. I'll run it for 24 hours which it never
> > succeeded in the past. ]
>
> I ran with this patch on three boxes all night, one for 24 hours. No
> problems. I stopped the tests, removed the patch, ran the test on the
> same boxes and they all crashed within an hour.
>
> This patch definitely fixes the bug.
>
> The test I ran was:
>
> while :; do
> ./ftrace-test-mkinstances || break
> ./ftrace-test-mkinstances-2 || break
> done
>
> Note, the tests expect debugfs to be mounted at /debug.
Well, those are some broken tests :)
Anyway, thanks for the patch, I'll queue it up after 3.16-rc1 is out.
greg k-h
next prev parent reply other threads:[~2014-06-10 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 18:06 [RFC][PATCH] debugfs: Fix corrupted loop in debugfs_remove_recursive Steven Rostedt
2014-06-10 13:33 ` Steven Rostedt
2014-06-10 20:23 ` Greg Kroah-Hartman [this message]
2014-06-10 20:22 ` Steven Rostedt
2014-06-10 20:33 ` Greg Kroah-Hartman
2014-06-30 15:53 ` Steven Rostedt
2014-06-30 16:26 ` Greg Kroah-Hartman
2014-06-12 10:43 ` Al Viro
2014-06-12 16:08 ` Greg Kroah-Hartman
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=20140610202302.GB20499@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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.