From: Chris Feist <cfeist@redhat.com>
To: autofs@linux.kernel.org, Ian McLeod <imcleod@redhat.com>
Subject: [PATCH] autofs 4.1.4 no-unlink patch
Date: Mon, 11 Jul 2005 14:43:02 -0500 [thread overview]
Message-ID: <42D2CBC6.200@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Ian,
We've been hearing some reports of autofs removing entire home directories
when mounts expire. It appears that this could be some sort of race condition
in the walk_tree code, where when the function starts the directory is
unmounted and then autofs unlinks files in the the directory that is supposed
to be umounted. I've attached a patch to the rm_unwanted_fn which adds some
additional checks before we unlink anything, and it prevents autofs from
unlinking files (since I'm pretty sure that autofs never creates a regular
file). Let me know what you think.
Thanks,
Chris
[-- Attachment #2: autofs-4.1.4-no-unlink-upstream --]
[-- Type: text/plain, Size: 1264 bytes --]
--- autofs-4.1.4/daemon/automount.c.no-unlink 2005-07-11 13:28:57.000000000 -0500
+++ autofs-4.1.4/daemon/automount.c 2005-07-11 13:50:46.000000000 -0500
@@ -216,16 +216,38 @@ static int walk_tree(const char *base, i
static int rm_unwanted_fn(const char *file, const struct stat *st, int when, void *arg)
{
int rmsymlink = *(int *) arg;
+ struct stat newst;
if (when == 0) {
if (st->st_dev != ap.dev)
return 0;
- } else {
- info("rm_unwanted: %s\n", file);
- if (S_ISDIR(st->st_mode))
- rmdir(file);
- else if (!S_ISLNK(st->st_mode) || rmsymlink)
- unlink(file);
+ return 1;
+ }
+
+ if (lstat(file, &newst)) {
+ crit ("rm_unwanted: unable to stat file, possible race "
+ "condition.");
+ return 0;
+ }
+
+ if (newst.st_dev != ap.dev) {
+ crit ("rm_unwanted: file %s has the wrong device, possible "
+ "race condition.",file);
+ return 0;
+ }
+
+ if (S_ISDIR(newst.st_mode)) {
+ if (rmdir(file)) {
+ info ("rm_unwanted: unable to remove directory"
+ " %s", file);
+ return 0;
+ }
+ } else if (S_ISREG(newst.st_mode)) {
+ crit ("rm_unwanted: attempting to remove files from a mounted "
+ "directory.");
+ return 0;
+ } else if (S_ISLNK(newst.st_mode) && rmsymlink) {
+ unlink(file);
}
return 1;
[-- Attachment #3: Type: text/plain, Size: 140 bytes --]
_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
next reply other threads:[~2005-07-11 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 19:43 Chris Feist [this message]
2005-07-12 16:30 ` [PATCH] autofs 4.1.4 no-unlink patch Ian Kent
2005-07-12 18:33 ` Jeff Moyer
2005-07-13 6:06 ` Ian Kent
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=42D2CBC6.200@redhat.com \
--to=cfeist@redhat.com \
--cc=autofs@linux.kernel.org \
--cc=imcleod@redhat.com \
/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.