From: Valdis.Kletnieks@vt.edu
To: Ludwig Nussel <ludwig.nussel@suse.de>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] implement uid mount option for ext2 and ext3
Date: Thu, 23 Jul 2009 17:23:41 -0400 [thread overview]
Message-ID: <10655.1248384221@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 23 Jul 2009 13:36:29 +0200." <1248348991-849-1-git-send-email-ludwig.nussel@suse.de>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
On Thu, 23 Jul 2009 13:36:29 +0200, Ludwig Nussel said:
> The following two patches (for 2.6.31-rc4) therefore implement the
> uid mount option for ext2 and ext3 to make them actually useful on
> removable media. My implementation just writes uid 0 to disk for
> files that are owned by the specified user.
I'm certain this will end up violating the Principle of Least Surprise.
For instance - you have UID 500 on 2 systems. Mount on old system, create a
file - it's owned by 500. Take it to a new system, mount it, watch it get
smashed to 0 because it's owned by "you". Take it back to the old system, and
hey, you can't edit your file because it's not owned by 500 anymore...
Hint: This *same exact* problem has been an issue for NFS for at least 25
years. Might want to think about (a) why Yellow Pages (and later LDAP) was
developed, and (b) why NFS "root squash" traditionally maps to "nobody" rather
than a usable UID.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-07-23 21:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 11:36 Ludwig Nussel
2009-07-23 11:36 ` [PATCH 1/2] implement uid mount option for ext2 Ludwig Nussel
2009-07-23 11:36 ` [PATCH 2/2] implement uid mount option for ext3 Ludwig Nussel
2009-07-23 14:37 ` [PATCH 0/2] implement uid mount option for ext2 and ext3 Randy Dunlap
2009-07-23 21:23 ` Valdis.Kletnieks [this message]
2009-07-24 10:23 ` Ludwig Nussel
2009-07-30 9:07 ` Pavel Machek
2009-07-24 10:30 ` [PATCH 0/2] implement uid mount option for ext2 and ext3, try 2 Ludwig Nussel
2009-07-24 10:30 ` [PATCH 1/2] implement uid mount option for ext2 Ludwig Nussel
2009-07-24 10:30 ` [PATCH 2/2] implement uid mount option for ext3 Ludwig Nussel
2009-07-24 16:52 ` [PATCH 1/2] implement uid mount option for ext2 Andreas Dilger
2009-07-24 18:58 ` John Stoffel
2009-07-24 23:16 ` Jamie Lokier
2009-07-27 14:56 ` John Stoffel
2009-07-25 15:44 ` Ludwig Nussel
2009-07-27 19:14 ` Andreas Dilger
2009-07-28 7:50 ` Ludwig Nussel
2009-07-28 11:01 ` [PATCH 0/2] implement uid mount option for ext2 and ext3, try 3 Ludwig Nussel
2009-07-28 11:01 ` [PATCH 1/2] implement uid and gid mount options for ext2 Ludwig Nussel
2009-07-28 11:01 ` [PATCH 2/2] implement uid and gid mount options for ext3 Ludwig Nussel
2009-07-28 18:11 ` [PATCH 0/2] implement uid mount option for ext2 and ext3, try 3 Andreas Dilger
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=10655.1248384221@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludwig.nussel@suse.de \
/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®