Why Ext2/3 needs immutable attribute?

Why not simply unset the write bit for all three groups of users? 
That seems to be enough to prevent file modification.

Immutable seems to only add one more protection level in case of
misconfiguration on standard access right bits.  Is that right?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: Why Ext2/3 needs immutable attribute?
  - From: dean gaudet <[email protected]>
- Re: Why Ext2/3 needs immutable attribute?
  - From: Bernd Eckenfels <[email protected]>
- Re: Why Ext2/3 needs immutable attribute?
  - From: Willy Tarreau <[email protected]>

Prev by Date: Re: Poor I/O Performance with MegaRaid SATA 150-4; bug or feature?
Next by Date: Re: Why Ext2/3 needs immutable attribute?
Previous by thread: [PATCH] Changing RT priority in kernel 2.6 without CAP_SYS_NICE
Next by thread: Re: Why Ext2/3 needs immutable attribute?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]