From: Sergey Vlasov <vsu@altlinux.ru>
To: Pekka J Enberg <penberg@cs.Helsinki.FI>
Cc: Phillip Susi <psusi@cfl.rr.com>,
Peter Osterlund <petero2@telia.com>,
linux-kernel@vger.kernel.org, bfennema@falcon.csc.calpoly.edu,
Christoph Hellwig <hch@lst.de>, Al Viro <viro@ftp.linux.org.uk>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC][PATCH] UDF filesystem uid fix
Date: Tue, 14 Feb 2006 14:36:17 +0300 [thread overview]
Message-ID: <20060214143617.3c0719b0.vsu@altlinux.ru> (raw)
In-Reply-To: <Pine.LNX.4.58.0602140916230.15339@sbz-30.cs.Helsinki.FI>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
On Tue, 14 Feb 2006 09:28:30 +0200 (EET) Pekka J Enberg wrote:
> Yes, I agree that the current code is broken. I was talking about what the
> semantics should be and that your patch doesn't quite get us there. Do you
> disagree with that? The UDF specification I am looking at [1] says that -1
> is used by operating systems that do not support uid/gid to denote an
> invalid id (although ECMA-167 doesn't seem to have such rule), which is
> why I think it's an bad idea for Linux to ever write it on disk. Instead,
> we should always write the proper id on disk unless it was invalid in the
> first place and we did not explicity change it (via chown, for example).
Storing uid/gid values on the filesystem is not always good. Imagine
that you need to work with the same removable media on different
machines, where you have accounts with different uids; in this case
uid/gid values stored on one machine have no meaning everywhere else.
It would be good to have a mount option for UDF which turns off the
uid/gid handling completely and shows all files on the filesystem with
uid/gid specified by mount options.
See also the recent thread "Filesystem for mobile hard drive":
http://lkml.org/lkml/2006/2/12/64
> 1. http://www.osta.org/specs/pdf/udf260.pdf
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-14 11:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 18:17 [RFC][PATCH] UDF filesystem uid fix Peter Osterlund
2006-02-13 9:49 ` Pekka Enberg
2006-02-13 16:51 ` Phillip Susi
2006-02-14 7:28 ` Pekka J Enberg
2006-02-14 11:36 ` Sergey Vlasov [this message]
2006-02-14 15:54 ` Phillip Susi
2006-02-15 7:31 ` Pekka Enberg
2006-02-15 15:55 ` Phillip Susi
2006-02-15 17:31 ` Pekka Enberg
2006-02-15 18:48 ` Phillip Susi
2006-02-15 20:28 ` Pekka Enberg
2006-03-04 23:19 ` Phillip Susi
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=20060214143617.3c0719b0.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--cc=akpm@osdl.org \
--cc=bfennema@falcon.csc.calpoly.edu \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.Helsinki.FI \
--cc=petero2@telia.com \
--cc=psusi@cfl.rr.com \
--cc=viro@ftp.linux.org.uk \
/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.