The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: wingc@engin.umich.edu (Christopher Allen Wing)
Cc: sentry21@cdslash.net, linux-kernel@vger.kernel.org,
	tytso@mit.edu (Theodore Y. Ts'o)
Subject: Re: Weird ext2fs immortal directory bug (all-in-one)
Date: Thu, 26 Jul 2001 17:10:27 -0600 (MDT)	[thread overview]
Message-ID: <200107262310.f6QNASE21283@lynx.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.33.0107261312450.6405-100000@bayarea.engin.umich.edu> from "Christopher Allen Wing" at Jul 26, 2001 01:21:01 PM

Chris Wing writes:
> At the very least, ext2 fsck should complain about ext2 attributes set for
> symlinks or device files... I have had this same problem myself many times
> on machines with bad SCSI termination- I end up with unremovable device
> files thanks to a bogus immutable bit and have to use debugfs to get rid
> of them.

I checked, and at least recent versions of e2fsck complain/fix immutable
flags on device files, fifos, and sockets.  The below check disallows
immutable or append-only flags on symlinks (on the grounds that it is not
possible to set these legally).

Now what I need to do is also add an e2fsck test case for this...

Cheers, Andreas
===========================================================================
--- 1.56/e2fsck/pass1.c	Thu Jul 19 14:31:24 2001
+++ edited/e2fsck/pass1.c	Thu Jul 26 16:18:59 2001
@@ -559,6 +563,7 @@
 			check_size(ctx, &pctx);
 			ctx->fs_blockdev_count++;
 		} else if (LINUX_S_ISLNK (inode.i_mode)) {
+			check_immutable(ctx, &pctx);
 			ctx->fs_symlinks_count++;
 			if (!inode.i_blocks) {
 				if (inode.i_size_high ||

-- 
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/

  parent reply	other threads:[~2001-07-26 23:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-26 14:37 Weird ext2fs immortal directory bug sentry21
2001-07-26 15:02 ` Richard B. Johnson
2001-07-26 15:04   ` sentry21
2001-07-26 15:32     ` Dan Podeanu
2001-07-26 15:37       ` sentry21
2001-07-26 15:48         ` Richard B. Johnson
2001-07-26 15:50           ` sentry21
2001-07-26 16:05             ` Richard B. Johnson
2001-07-26 16:10             ` Horst von Brand
2001-07-26 15:34     ` Sven Vermeulen
2001-07-26 15:44 ` Daniel Phillips
2001-07-26 17:08   ` Weird ext2fs immortal directory bug (all-in-one) sentry21
2001-07-26 17:21     ` Christopher Allen Wing
2001-07-26 17:25       ` Alan Cox
2001-07-26 18:21       ` Andreas Dilger
2001-07-26 19:11         ` Chris Meadors
2001-07-27  3:17         ` Gerhard Mack
2001-07-26 23:10       ` Andreas Dilger [this message]
2001-07-26 16:22 ` Weird ext2fs immortal directory bug Andreas Dilger

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=200107262310.f6QNASE21283@lynx.adilger.int \
    --to=adilger@turbolinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sentry21@cdslash.net \
    --cc=tytso@mit.edu \
    --cc=wingc@engin.umich.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