From: Louis Rilling <Louis.Rilling@kerlabs.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [BUGFIX][PATCH v2 0/2] configfs: Fix cleanup after mkdir() failure
Date: Wed, 16 Jul 2008 19:56:54 +0200 [thread overview]
Message-ID: <20080716175654.GA19577@hawkmoon.kerlabs.com> (raw)
In-Reply-To: <20080716172703.GA18105@ca-server1.us.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]
On Wed, Jul 16, 2008 at 10:27:03AM -0700, Joel Becker wrote:
> On Wed, Jul 16, 2008 at 03:08:21PM +0200, Louis Rilling wrote:
> > There is still a few things in flight:
> > - error handling in config_*_init_type_name(): has rather low priority in my
> > TODO list, will come back to it probably in a few weeks.
>
> I thought we did this already. Perhaps I didn't include it?
> Did we have another change to make?
You requested me to move a BUG_ON() earlier (before the actual memory
allocation), and to update documentation. I'm quite in a hurry on other things,
so I'm delaying this (especially the documentation part for which I feel like a
new paragraph is needed).
>
> > - a small locking cleanup in configfs_rmdir(): will do at the same time as
> > lockdep stuff.
>
> What sort of change? I suppose I'll see it when it arrives.
You may look at the retry loop in configfs_rmdir() and see that locks need only
to be taken inside the loop, not outside. This would result in fewer lines for
exactly the same behavior.
> I figure this new stuff will probably miss the .27 window, but
> it sounds like that's fine - nothing too serious, and it will make .28.
Sorry for not being responsive enough. As mentioned above, I have more urgent
things to work on right now.
Thanks,
Louis
--
Dr Louis Rilling Kerlabs
Skype: louis.rilling Batiment Germanium
Phone: (+33|0) 6 80 89 08 23 80 avenue des Buttes de Coesmes
http://www.kerlabs.com/ 35700 Rennes
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-07-16 17:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 14:56 Louis Rilling
2008-07-04 14:56 ` [BUGFIX][PATCH v2 1/2] configfs: Prevent userspace from creating new entries under attaching directories Louis Rilling
2008-07-11 20:02 ` Joel Becker
2008-07-04 14:56 ` [BUGFIX][PATCH v2 2/2] configfs: Lock new directory inodes before removing on cleanup after failure Louis Rilling
2008-07-11 20:05 ` Joel Becker
2008-07-04 16:32 ` [BUGFIX][PATCH v2 0/2] configfs: Fix cleanup after mkdir() failure Louis Rilling
2008-07-06 1:03 ` Joel Becker
2008-07-11 22:07 ` Joel Becker
2008-07-11 22:52 ` Andrew Morton
2008-07-11 23:37 ` Joel Becker
2008-07-16 13:08 ` Louis Rilling
2008-07-16 17:27 ` Joel Becker
2008-07-16 17:56 ` Louis Rilling [this message]
2008-07-16 20:43 ` 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=20080716175654.GA19577@hawkmoon.kerlabs.com \
--to=louis.rilling@kerlabs.com \
--cc=Joel.Becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.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
all inboxes | Powered by JetHome®