summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2006-09-20 11:50:46 +0000
committerJim Meyering <jim@meyering.net>2006-09-20 11:50:46 +0000
commit05ce3b298641e2ccc5f668e9e769644371090b80 (patch)
treee65c4b5f9b081e49f81b54857765ff257c4246a8 /src
parent1671b056a54d1148205801b1faa37abb1bb5467a (diff)
downloadcoreutils-05ce3b298641e2ccc5f668e9e769644371090b80.tar.xz
Fix the 2006-09-18 bug differently.
* src/chmod.c: (process_file): Upon FTS_NS for a top-level file, tell fts_read to stat the file again, in case it has become accessible since the initial fts_open call. * src/chown-core.c (change_file_owner): Likewise.
Diffstat (limited to 'src')
-rw-r--r--src/chmod.c13
-rw-r--r--src/chown-core.c13
2 files changed, 26 insertions, 0 deletions
diff --git a/src/chmod.c b/src/chmod.c
index 29611366c..7858c0a66 100644
--- a/src/chmod.c
+++ b/src/chmod.c
@@ -193,6 +193,19 @@ process_file (FTS *fts, FTSENT *ent)
return true;
case FTS_NS:
+ /* For a top-level file or directory, this FTS_NS (stat failed)
+ indicator is determined at the time of the initial fts_open call.
+ With programs like chmod, chown, and chgrp, that modify
+ permissions, it is possible that the file in question is
+ accessible when control reaches this point. So, if this is
+ the first time we've seen the FTS_NS for this file, tell
+ fts_read to stat it "again". */
+ if (ent->fts_level == 0 && ent->fts_number == 0)
+ {
+ ent->fts_number = 1;
+ fts_set (fts, ent, FTS_AGAIN);
+ return true;
+ }
error (0, ent->fts_errno, _("cannot access %s"), quote (file_full_name));
ok = false;
break;
diff --git a/src/chown-core.c b/src/chown-core.c
index 39cb34d8b..dbd3e52d8 100644
--- a/src/chown-core.c
+++ b/src/chown-core.c
@@ -267,6 +267,19 @@ change_file_owner (FTS *fts, FTSENT *ent,
break;
case FTS_NS:
+ /* For a top-level file or directory, this FTS_NS (stat failed)
+ indicator is determined at the time of the initial fts_open call.
+ With programs like chmod, chown, and chgrp, that modify
+ permissions, it is possible that the file in question is
+ accessible when control reaches this point. So, if this is
+ the first time we've seen the FTS_NS for this file, tell
+ fts_read to stat it "again". */
+ if (ent->fts_level == 0 && ent->fts_number == 0)
+ {
+ ent->fts_number = 1;
+ fts_set (fts, ent, FTS_AGAIN);
+ return true;
+ }
error (0, ent->fts_errno, _("cannot access %s"), quote (file_full_name));
ok = false;
break;