All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Wood <timothy@hallcomp.com>
To: Stephen Smalley <sds@tislabs.com>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: network and module problems
Date: 25 Jan 2002 09:36:21 -0500	[thread overview]
Message-ID: <1011969383.1945.1.camel@phobos> (raw)
In-Reply-To: <Pine.GSO.4.33.0201241340360.28970-100000@raven>

[-- Attachment #1: Type: text/plain, Size: 2190 bytes --]

On Thu, 2002-01-24 at 13:58, Stephen Smalley wrote:
> 
> On 24 Jan 2002, Timothy Wood wrote:
> 
> > Cannot send dump request: Connection refused
> 
> Did you enable Netlink support when you configured the kernel?
> What release of SELinux are you using?

Yes. 2001121010 (according to the tarball)

> 
> > module and by building it straight into the kernel.  Which brings me to
> > the module problem.  Dmesg shows that it finds the nic but I never see
> > the module as being loaded when I run lsmod and when I try to insmod it
> > I get an error saying that it can't locate the card on the console and
> > avc errors in the system log.
> 
> If you build the module into the kernel, it won't show up in lsmod.
> What AVC errors are being logged?  Did you run insmod after logging
> into the sysadm_r role?  Also, is your kernel in permissive mode or
> enforcing mode?

I realise that.  I merely brought it up in regards to the time when the
network was built as a module.  

kernel: avc: denied { read } for pid=268 exe=/sbin/insmod
path=/etc/modules.conf.vm dev=08:01 ino=213709
scontext=system-U:system_r:kmod_t
tcontext=system_u:object_r:etc_runtime_t tclass=lnk_file

that is one of the errors.  if you want an entire boot log I can provide
that.  Yes I did try insmoding after I logged in as an administrator and
thats when the I get the error telling me that it can't locate the card
despite the fact that dmesg shows it was found during boot.  I really
don't think this is a problem the network driver as the loopback (lo)
interface is never raised either.  The dump request thing looks like the
root of the problem since it occurs if I try to raise either the eth0 or
lo interfaces.  The system boots into permissive mode and I usually
leave it there.

> 
> > I'm also running this on ext3 if that might have something to do with it
> > since I know ext3 isn't properly supported yet.  Anyhow, any ideas are
> > welcome and I can reload this machine if the need arises.  Thanks.
> 
> ext3 works fine.  It was only an issue when ext3 support wasn't in the
> mainstream kernel.

Ah, I see.  Thanks for the clarification.

Timothy,

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-01-25 14:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-24 17:15 network and module problems Timothy Wood
2002-01-24 18:58 ` Stephen Smalley
2002-01-25 14:36   ` Timothy Wood [this message]
2002-01-25 14:56     ` Stephen Smalley
2002-01-25 15:03     ` Paul Krumviede
2002-01-25 16:35       ` Timothy Wood
2002-01-25 17:22         ` Paul Krumviede
2002-01-25 17:47         ` Stephen Smalley
2002-01-25 17:56           ` Stephen Smalley
2002-01-25 18:22           ` Paul Krumviede
2002-01-25 18:54             ` Stephen Smalley
2002-01-25 18:49       ` Timothy Wood
2002-01-25 19:04         ` Stephen Smalley
2002-01-25 23:22           ` Timothy Wood
2002-01-28 13:57             ` Stephen Smalley

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=1011969383.1945.1.camel@phobos \
    --to=timothy@hallcomp.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=sds@tislabs.com \
    /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.