From: Pavel Machek <pavel@ucw.cz>
To: Theodore Tso <tytso@mit.edu>, Bodo Eggert <7eggert@gmx.de>,
Artem Bityutskiy <dedekind@yandex.ru>,
Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: replace() system call needed (was Re: EXT4-ish "fixes" in UBIFS)
Date: Wed, 1 Apr 2009 22:52:01 +0200 [thread overview]
Message-ID: <20090401205201.GI17808@elf.ucw.cz> (raw)
In-Reply-To: <20090401000657.GH15063@mit.edu>
On Tue 2009-03-31 20:06:57, Theodore Tso wrote:
> On Tue, Mar 31, 2009 at 11:27:33PM +0200, Bodo Eggert wrote:
> > This can be done using implicit logic:
> >
> > ->E.g. on close(), mark inodes without being sync()ed as poisoned.
> > (I can think of more sophisticated logic, but ...)
> > ->On completing the inode with the delayed allocations, unpoison it.
> > ->Don't commit rename()s if the corresponding inode is poisoned.
>
> Send us patches if you think it's that easy to do what you are
> proposing. I assure it's not easy.
Well, implementing replace() syscall would be quite easy. Would you
want such a patch?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-04-01 20:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ckjPq-2Dl-15@gated-at.bofh.it>
[not found] ` <cl2jy-65z-1@gated-at.bofh.it>
[not found] ` <cl2CZ-6q2-21@gated-at.bofh.it>
[not found] ` <cl2N9-6Bj-9@gated-at.bofh.it>
2009-03-31 21:27 ` replace() system call needed (was Re: EXT4-ish "fixes" in UBIFS) Bodo Eggert
2009-04-01 0:06 ` Theodore Tso
2009-04-01 20:52 ` Pavel Machek [this message]
2009-04-01 22:58 ` Bodo Eggert
2009-03-27 12:48 EXT4-ish "fixes" in UBIFS Artem Bityutskiy
2009-03-29 12:26 ` replace() system call needed (was Re: EXT4-ish "fixes" in UBIFS) Pavel Machek
2009-03-29 12:42 ` Artem Bityutskiy
2009-03-29 12:50 ` Pavel Machek
2009-03-29 13:00 ` Artem Bityutskiy
2009-03-29 13:02 ` Pavel Machek
2009-03-29 13:07 ` Artem Bityutskiy
2009-03-29 13:22 ` Andreas T.Auer
2009-03-29 13:55 ` Artem Bityutskiy
2009-03-29 13:40 ` Pavel Machek
2009-03-29 13:57 ` Artem Bityutskiy
2009-03-29 14:00 ` Pavel Machek
2009-03-30 17:19 ` Ric Wheeler
2009-03-30 22:11 ` Pavel Machek
2009-03-29 13:01 ` Andreas T.Auer
2009-03-29 13:06 ` Artem Bityutskiy
2009-03-30 15:58 ` Diego Calleja
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=20090401205201.GI17808@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=7eggert@gmx.de \
--cc=Artem.Bityutskiy@nokia.com \
--cc=dedekind@yandex.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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