From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Tom Zanussi <zanussi@us.ibm.com>,
ltt-dev@shafik.org, Michel Dagenais <michel.dagenais@polymtl.ca>,
Douglas Niehaus <niehaus@eecs.ku.edu>
Subject: Re: [PATCH 1/11] LTTng-core 0.5.111 : Relay+DebugFS (DebugFS fix)
Date: Wed, 20 Sep 2006 08:21:30 -0400 [thread overview]
Message-ID: <20060920122130.GB25639@Krystal> (raw)
In-Reply-To: <20060917160705.GB6326@suse.de>
* Greg KH (gregkh@suse.de) wrote:
> On Sat, Sep 16, 2006 at 03:51:03AM -0400, Mathieu Desnoyers wrote:
> > 1 - DebugFS stalled dentry patch
> > DebugFS seems to keep a stalled dentry when a process is in a directory that is
> > being removed. Force a differed deletion.
> > patch-2.6.17-lttng-core-0.5.111-debugfs.diff
> >
> >
> > OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
> > Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
>
> > --- a/fs/debugfs/inode.c
> > +++ b/fs/debugfs/inode.c
> > @@ -266,6 +266,7 @@ EXPORT_SYMBOL_GPL(debugfs_create_dir);
> > void debugfs_remove(struct dentry *dentry)
> > {
> > struct dentry *parent;
> > + int ret = 0;
> >
> > if (!dentry)
> > return;
> > @@ -278,9 +279,10 @@ void debugfs_remove(struct dentry *dentr
> > if (debugfs_positive(dentry)) {
> > if (dentry->d_inode) {
> > if (S_ISDIR(dentry->d_inode->i_mode))
> > - simple_rmdir(parent->d_inode, dentry);
> > + ret = simple_rmdir(parent->d_inode, dentry);
> > else
> > - simple_unlink(parent->d_inode, dentry);
> > + ret = simple_unlink(parent->d_inode, dentry);
> > + if(ret) d_delete(dentry);
>
> Are you saying that perhaps all other users of simple_unlink() are also
> broken like this? If so, why not just fix simple_unlink()?
>
I don't think that libfs is fundamentally broken, as simple_unlink always
returns 0 but simple_rmdir may fail if !simple_empty(dentry). I think that the
decision of what to do in such situation is "simply" left to the caller.
But you probably know more than I do on that matter.
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2006-09-20 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-16 7:51 [PATCH 1/11] LTTng-core 0.5.111 : Relay+DebugFS (DebugFS fix) Mathieu Desnoyers
2006-09-17 16:07 ` Greg KH
2006-09-20 12:21 ` Mathieu Desnoyers [this message]
2006-09-18 1:21 ` Karim Yaghmour
2006-09-19 13:04 ` Christoph Hellwig
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=20060920122130.GB25639@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@redhat.com \
--cc=niehaus@eecs.ku.edu \
--cc=tglx@linutronix.de \
--cc=zanussi@us.ibm.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 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.