All of lore.kernel.org
 help / color / mirror / Atom feed
From: forrest whitcher <fw@fwsystems.com>
To: "Stephen D. Smalley" <sds@epoch.ncsc.mil>
Cc: selinux@tycho.nsa.gov
Subject: Re: Kernel Oops from afsd under the selinux kernel
Date: Tue, 3 Dec 2002 16:45:30 -0500	[thread overview]
Message-ID: <20021203164530.48a2f1dd.fw@fwsystems.com> (raw)
In-Reply-To: <200212032008.PAA26482@moss-shockers.ncsc.mil>

Thanks!

removing the #ifndef _SELINUX_KERNEL_PATCH_ -- #endif ca line 650++ indeed 
solves it -- is this adding significant overhead? .. should I patch afsd
to call alloc_inode() so the test isn't being added to all calls?

forrest


On Tue, 3 Dec 2002 15:08:28 -0500 (EST) (unchecked - local sync NTPstrat4)
"Stephen D. Smalley" <sds@epoch.ncsc.mil> did inscribe thusly:

> 
> > I'm getting the following Oops running on a redhat 7.1 system with the
> > LSM/selinux patches. kernel 2.4.19. The system runs well in enforcing
> > mode (however this test is in non-enforcing mode because I can't really 
> > do the policy changes until I have a working afsd.
> 
> You might try the attached patch to see if it helps.  The AFS code might
> bypass alloc_inode() when allocating inodes, in which case the inode
> would not have an allocated security structure upon entry to inode_doinit.
> 
> --
> Stephen Smalley, NSA
> sds@epoch.ncsc.mil
> 

--
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.

  reply	other threads:[~2002-12-03 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 20:08 Kernel Oops from afsd under the selinux kernel Stephen D. Smalley
2002-12-03 21:45 ` forrest whitcher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-04 14:31 Stephen D. Smalley
2002-12-03 18:50 forrest whitcher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021203164530.48a2f1dd.fw@fwsystems.com \
    --to=fw@fwsystems.com \
    --cc=sds@epoch.ncsc.mil \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.