From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Sytse Wielinga <s.b.wielinga@student.utwente.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH for testing] cow behaviour for hard links
Date: Fri, 12 Mar 2004 19:29:12 +0100 [thread overview]
Message-ID: <20040312182912.GB7087@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200403121849.03505.s.b.wielinga@student.utwente.nl>
This is assuming we keep current design.
On Fri, 12 March 2004 18:48:57 +0100, Sytse Wielinga wrote:
>
> I have made some pretty thorough changes to your patch though. You can find
> the patch attached to this email.
> Things I've changed:
>
> - moved break_cow_link from dentry_open in open.c to get_write_access in
> namei.c. Putting it in dentry_open thoroughly breaks things, as it's too late
> to save files from being truncated, for example.
True, good catch.
> - made something from the mess you made of ext2/ext3 inode flags :-P
Good. Both variants of my mess worked, so I left it for the moment.
> - removed inheritance, as it's not useful in any way, not expected and breaks
> linking of files with S_COWLINK set.
Not useful? Without inheritance, I have to manually add the flag for
every file/directory I add. Each time I forget, writes go to both
files and I notice the mess weeks later. Naa, that's where we're now
and why I created the patch in the first place.
What we do need, though, is a new errno. -EMLINK is close, but still
wrong.
> - made a go at supporting reiserfs, but failed... my changes are in the
> patch, could somebody please have a look and tell me what I've missed?
No clue, don't care. :)
> - fcntl_setcow now spins a spinlock
Not the only lock I missed. Good.
Jörn
--
He who knows that enough is enough will always have enough.
-- Lao Tsu
next prev parent reply other threads:[~2004-03-12 18:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 19:34 Jörn Engel
2004-03-10 19:35 ` [Program " Jörn Engel
2004-03-10 21:34 ` [PATCH " Jamie Lokier
2004-03-10 22:17 ` Jörn Engel
2004-03-10 23:07 ` Sytse Wielinga
2004-03-10 23:46 ` Sytse Wielinga
2004-03-12 17:48 ` Sytse Wielinga
2004-03-12 18:18 ` Jörn Engel
2004-03-12 18:29 ` Jörn Engel [this message]
2004-03-13 13:43 ` Pavel Machek
2004-03-13 19:48 ` Jörn Engel
2004-03-13 21:03 ` Pavel Machek
2004-03-15 7:45 ` Jamie Lokier
2004-03-15 10:27 ` Jörn Engel
2004-03-13 22:14 ` Jörn Engel
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=20040312182912.GB7087@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=s.b.wielinga@student.utwente.nl \
/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®