From: Greg KH <greg@kroah.com>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Pierre Ossman <drzeus-mmc@drzeus.cx>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] mmc: Export ios settings for a host through debugfs
Date: Sat, 28 Jun 2008 09:43:43 -0700 [thread overview]
Message-ID: <20080628164343.GA11922@kroah.com> (raw)
In-Reply-To: <20080628183736.077263a6@hskinnemo-gx745.norway.atmel.com>
On Sat, Jun 28, 2008 at 06:37:36PM +0200, Haavard Skinnemoen wrote:
> Haavard Skinnemoen <haavard.skinnemoen@atmel.com> wrote:
> > Ok, I'll try. I'm not an FS developer, so I'm sure the below patch is
> > horribly broken in some subtle way, but it does appear to work at least
> > the few times I tried it...
> >
> > Lockdep indeed confirms that something is broken:
>
> Another try. This time I'm taking only one lock at a time, so lockdep
> is happy. Is it still safe?
At first glance, this looks sane, thanks a lot.
> From ee72de0df9a471eb7fbab7827606a2b9a6afe19c Mon Sep 17 00:00:00 2001
> From: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
> Date: Sat, 28 Jun 2008 17:54:15 +0200
> Subject: [PATCH] debugfs: Implement debugfs_remove_recursive()
>
> debugfs_remove_recursive() will remove a dentry and all its children.
> Drivers can use this to zap their whole debugfs tree so that they don't
> need to keep track of every single debugfs dentry they created.
>
> It may fail to remove the whole tree in certain cases:
>
> sh-3.2# rmmod atmel-mci < /sys/kernel/debug/mmc0/ios/clock
> mmc0: card b368 removed
> atmel_mci atmel_mci.0: Lost dma0chan1, falling back to PIO
> sh-3.2# ls /sys/kernel/debug/mmc0/
> ios
>
> But I'm not sure if that case can be handled in any sane manner.
I think we have always been failing this case as I know securityfs also
has this same issue, and the code base is pretty much identical.
So don't worry that this patch caused this issue.
I'll queue it up unless there are any other objections to it.
thanks,
greg k-h
next prev parent reply other threads:[~2008-06-28 16:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 11:09 [PATCH 1/3] mmc: Export internal host state through debugfs Haavard Skinnemoen
2008-06-26 11:09 ` [PATCH 2/3] mmc: Export ios settings for a host " Haavard Skinnemoen
2008-06-26 11:09 ` [PATCH 3/3] mmc: Add per-card debugfs support Haavard Skinnemoen
2008-06-28 13:37 ` Pierre Ossman
2008-06-28 13:48 ` Haavard Skinnemoen
2008-06-28 14:01 ` Pierre Ossman
2008-06-28 14:15 ` Haavard Skinnemoen
2008-06-28 15:22 ` Pierre Ossman
2008-06-28 15:36 ` Haavard Skinnemoen
2008-06-28 16:11 ` Pierre Ossman
2008-06-28 13:34 ` [PATCH 2/3] mmc: Export ios settings for a host through debugfs Pierre Ossman
2008-06-28 13:47 ` Haavard Skinnemoen
2008-06-28 13:59 ` Pierre Ossman
2008-06-28 14:07 ` Haavard Skinnemoen
2008-06-28 15:33 ` Greg KH
2008-06-28 16:08 ` Haavard Skinnemoen
2008-06-28 16:37 ` Haavard Skinnemoen
2008-06-28 16:43 ` Greg KH [this message]
2008-06-28 17:02 ` Haavard Skinnemoen
2008-06-28 13:28 ` [PATCH 1/3] mmc: Export internal host state " Pierre Ossman
2008-06-28 13:37 ` Haavard Skinnemoen
2008-06-28 13:40 ` Pierre Ossman
2008-06-28 13:49 ` Haavard Skinnemoen
2008-06-28 14:23 ` Haavard Skinnemoen
2008-06-28 14:41 ` Haavard Skinnemoen
2008-06-28 15:17 ` Pierre Ossman
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=20080628164343.GA11922@kroah.com \
--to=greg@kroah.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox