mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	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: Sat, 04 Mar 2006 18:19:35 -0500	[thread overview]
Message-ID: <440A2087.4020908@cfl.rr.com> (raw)
In-Reply-To: <43F37773.5030203@cfl.rr.com>

Finally got around to completing that patch.  Take a look and let me know if it looks good.  I posted it in the thread entitled "[PATCH] udf: fix uid/gid options and add uid/gid=ignore and forget options".  

Phillip Susi wrote:
> Pekka Enberg wrote:
>> Yeah, sounds much better to me. However, I am wondering if we can
>> actually drop the nosave/save cases completely. Wouldn't we get the same
>> semantics by letting uid/gid specify the default id and make the ignore
>> case look like we're always reading -1 from disk, and never writing out
>> any ids? So as a desktop user, you mount with "uid=", "gid=", and
>> "force" passed as mount option and it works as expected.
> 
> True, that would work.  It would require the addition of another mount 
> option though, so I wonder, is that really needed?  What problem with 
> the current patch would this solve?  Is there really a need to save real 
> ids to the disk with the current uid option and no force?  Keep in mind 
> that udf is meant for removable media where the uids aren't going to 
> make any sense in another system.
> 
> 
> Maybe I'm just being lazy though... I'll dig back into it and try to 
> submit a new patch with the force option by this weekend.
> 


      parent reply	other threads:[~2006-03-04 23:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 18:17 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
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 [this message]

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=440A2087.4020908@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome