From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: compat-wireless + Linux 2.6.26.8 testing results
Date: Wed, 17 Feb 2010 23:23:37 -0500 [thread overview]
Message-ID: <1266467017.3065.62.camel@mj> (raw)
In-Reply-To: <43e72e891002161651w4718431dqaf258151241f72fc@mail.gmail.com>
On Tue, 2010-02-16 at 16:51 -0800, Luis R. Rodriguez wrote:
> FWIW the two globals can be seen here:
>
> simple_release_fs(&debugfs_mount, &debugfs_mount_count);
>
> Not sure how to deal with that.
I think the safest approach would be to reimplement
debugfs_remove_recursive() using only debugfs_remove(). It would only
use the debugfs internals to find the children. I would even avoid
looking for siblings.
The idea is to descend the directory structure from the top (i.e. the
directory to be removed) to look for a child that is a file or an empty
directory and remove it. Then start from the top and do the same until
the top directory has no children. Then remove the top directory.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-02-18 5:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 2:10 compat-wireless updated for 2.6.33-rc8, 2.6.32.8 and next-20100212 Luis R. Rodriguez
2010-02-14 5:10 ` compat-wireless + Linux 2.6.26.8 testing results Pavel Roskin
2010-02-16 21:23 ` Luis R. Rodriguez
2010-02-16 22:12 ` Pavel Roskin
2010-02-16 22:59 ` Luis R. Rodriguez
2010-02-17 0:45 ` Luis R. Rodriguez
2010-02-17 0:51 ` Luis R. Rodriguez
2010-02-18 4:23 ` Pavel Roskin [this message]
2010-02-18 6:15 ` Pavel Roskin
2010-02-18 18:30 ` Luis R. Rodriguez
2010-02-20 0:21 ` Pavel Roskin
2010-02-20 2:37 ` Luis R. Rodriguez
2010-02-18 3:44 ` Pavel Roskin
2010-02-18 18:29 ` Luis R. Rodriguez
2010-02-18 19:18 ` Luis R. Rodriguez
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=1266467017.3065.62.camel@mj \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).