From: Jiri Slaby <jirislaby@gmail.com>
To: Jiri Slaby <jslaby@suse.cz>,
npiggin@kernel.dk, Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: OOPS in configfs when doing d_delete
Date: Fri, 27 May 2011 23:12:22 +0200 [thread overview]
Message-ID: <4DE013B6.9070801@gmail.com> (raw)
In-Reply-To: <20110518195842.GB5898@noexit.corp.google.com>
On 05/18/2011 09:58 PM, Joel Becker wrote:
> On Thu, May 12, 2011 at 11:34:29AM +0200, Jiri Slaby wrote:
>> On 02/22/2011 10:14 AM, Joel Becker wrote:
>>> On Mon, Feb 21, 2011 at 11:47:09AM +0100, Jiri Slaby wrote:
>>>>> I think you're right about the superfluous test, but I need more
>>>>> investigation to see what's going on. Thanks for the report.
>>>>> What was causing attach_group() to fail? Do you know?
>>>>
>>>> Dunno, I just modprobe'd the configfs example from Doc dir
>>>> (configfs_example_macros).
>>>
>>> I'm going to revisit the failed example (which shouldn't fail, I
>>> would think). Can you try the following patch to safely handle the
>>> failure rather than crashing the kernel?
>>>
>>> Joel
>>
>> Hi, what's the status of this? (It's verified to work some time ago.)
>
> The runtime fix is queued up for mainline. I'll be looking at
> the example code fix for the next merge window.
The fixes for the examples were merged today after being some time in
the -mm tree.
thanks,
--
js
next prev parent reply other threads:[~2011-05-27 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 10:20 OOPS in configfs when doing d_delete Jiri Slaby
2011-02-21 10:44 ` Joel Becker
2011-02-21 10:47 ` Jiri Slaby
2011-02-22 9:14 ` Joel Becker
2011-03-01 22:42 ` Jiri Slaby
2011-05-12 9:34 ` Jiri Slaby
2011-05-18 19:58 ` Joel Becker
2011-05-27 21:12 ` Jiri Slaby [this message]
2011-05-27 21:13 ` Joel Becker
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=4DE013B6.9070801@gmail.com \
--to=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--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.