public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Duncan Sands <duncan.sands@math.u-psud.fr>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org, Alexander Viro <viro@math.psu.edu>
Subject: Re: 2.5.8-pre3 & ext3: cannot chown
Date: Thu, 11 Apr 2002 20:53:50 +0200	[thread overview]
Message-ID: <E16vjhf-0000ad-00@baldrick> (raw)
In-Reply-To: <E16vYXu-0000HV-00@baldrick> <3CB538FE.B97F200E@zip.com.au>

On Thursday 11 April 2002 9:19 am, Andrew Morton wrote:
> Duncan Sands wrote:
> > The subject just about says it all.  After 12 hours
> > of uptime running 2.5.8-pre3 on an ext3 partition,
> > I noticed that changing the owner of a file had no
> > effect.  Rebooting with 2.4.18, there was no problem
> > in using chown.
>
> How does this look?

It looks good: with this patch I can now chown and chgrp
as usual.

Thanks for fixing this,

Duncan.

> --- linux-2.5.8-pre3/fs/open.c	Tue Apr  9 18:16:40 2002
> +++ 25/fs/open.c	Thu Apr 11 00:15:09 2002
> @@ -524,11 +524,11 @@ static int chown_common(struct dentry *
>  		goto out;
>  	newattrs.ia_valid =  ATTR_CTIME;
>  	if (user != (uid_t) -1) {
> -		newattrs.ia_valid =  ATTR_UID;
> +		newattrs.ia_valid |= ATTR_UID;
>  		newattrs.ia_uid = user;
>  	}
>  	if (group != (gid_t) -1) {
> -		newattrs.ia_valid =  ATTR_GID;
> +		newattrs.ia_valid |= ATTR_GID;
>  		newattrs.ia_gid = group;
>  	}
>  	if (!S_ISDIR(inode->i_mode))
>
> -

      parent reply	other threads:[~2002-04-11 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11  6:59 2.5.8-pre3 & ext3: cannot chown Duncan Sands
2002-04-11  7:19 ` Andrew Morton
2002-04-11 14:29   ` Alexander Viro
2002-04-11 18:53   ` Duncan Sands [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=E16vjhf-0000ad-00@baldrick \
    --to=duncan.sands@math.u-psud.fr \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.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