[Apparmor-general] Apparmor-general

[Carlos E. R.]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



The Wednesday 2008-01-23 at 12:07 -0800, John Johansen wrote:

>> Do you want me to add this info to the bugzilla?
>>
> yes please.

Done.


>> Wow! I hope this is not a simple coincidence!
>>
> yikes, me too.  If it is apparmor related you should see apparmor reject
> messages near those failures.  What apparmor is doing is failing to revalidate
> the pathname of lazily umounted files (if apparmor has cached the access as
> the first access things are okay).  The reporting bug that resulted in
> the bad inode_permission message does cause a crash or an improper reject
> just a bad message so that isn't the problem at least.

I have no idea.

Anyway, I will try to reproduce the situation with apparmour dissabled. I 
hope to see at least some extra message, if that is what apparmour 
blocked, or, hope of hopes, that the copy process that fails in bug 345039 
does not fail.

But to try that I have to have some spare time, stop tasks, and switch to 
runlevel 3, to minimize damage if the system does crash, so it will be 
somedays till I try.

- -- 
Cheers,
        Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFHl+ALtTMYHG2NR9URAh4sAKCOktiLrbx+GLCHe0yL3Xk7s/OgHgCeL6oS
t3Ekpc0uq4Ky5l2Jq3kx7AI=
=3H+a
-----END PGP SIGNATURE-----