Re: 2.4.29 Oops while setting the effective mask

On Tue, 8 Feb 2005 19:30:23 +0100
Michael Guntsche <[email protected]> wrote:

> Hi everyone,
> 
> I recently upgraded to 2.4.29 and tought I'd give the ACL patches a
> try.
>  After applying them and fixing a little glitch in the patch (the
> ext3_exit_acl  function was missing) I started playing around with it.
> Setting additional rights for user or group worked without a problem.
<snip>

Replying to my own mail, pah ;)
I should have tested it some more before writing the first bugreport.
I found out that it doesn't matter what you do 
a subsequent change to an already modified file (adding or removing a
user/group to a file that already has an ACL) leads to a panic.

I tried the following things.

	* Add a user to a file	
		* Add another user -> kernel oops
		* Delete the file -> kernel oops
		* Change the effective mask -> kernel oops

The process that oopses differs too. Once it is squid the other time sysklogd

The file itself really is borked after this. If I try to delete it
after the reboot I get another kernel oops. To be able to remove it I have
to mount the filesystem with "noacl".


Hope that helps,
Michael


	
_______________________________________________
acl-devel mailing list
[email protected]
http://acl.bestbits.at/mailman/listinfo/acl-devel