Disable the kernacc() check in mtx_validate() until such time that kernacc

does not require Giant.

This means that we may miss panics on a class of mutex programming bugs,
but only if running with a Chernobyl setting of debug-flags.

Spotted by:	Pete Carah <pete@ns.altadena.net>
This commit is contained in:
Poul-Henning Kamp 2002-10-25 08:40:20 +00:00
parent 15cd62721a
commit fa669ab7b8
2 changed files with 10 additions and 0 deletions

View File

@ -858,6 +858,10 @@ void
mtx_validate(struct mtx *m)
{
/*
* XXX: When kernacc() does not require Giant we can reenable this check
*/
#ifdef notyet
/*
* XXX - When kernacc() is fixed on the alpha to handle K0_SEG memory properly
* we can re-enable the kernacc() checks.
@ -873,6 +877,7 @@ mtx_validate(struct mtx *m)
VM_PROT_READ | VM_PROT_WRITE))
panic("Can't read and write to mutex %p", m);
#endif
#endif
}
#endif

View File

@ -858,6 +858,10 @@ void
mtx_validate(struct mtx *m)
{
/*
* XXX: When kernacc() does not require Giant we can reenable this check
*/
#ifdef notyet
/*
* XXX - When kernacc() is fixed on the alpha to handle K0_SEG memory properly
* we can re-enable the kernacc() checks.
@ -873,6 +877,7 @@ mtx_validate(struct mtx *m)
VM_PROT_READ | VM_PROT_WRITE))
panic("Can't read and write to mutex %p", m);
#endif
#endif
}
#endif