• James W Carter (jwcart2@epoch.ncsc.mil) wrote:
  > I found a problem with SELinux on a 2.5.44 kernel generating a kernel Oops when
  > running nfsd.
  

Hmm, this is an ugly one. Primarily because it touches into the fs specific code. I don't see a good way to do this any differently aside from introducing a wrapper like f_release that just conditionally calls f->release and ->file_free_security...

BTW, you missed the DTE instance of init_private_file.

thanks,
-chris

-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.