linux-kernel - Re: selinux troubleshooting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <BANLkTi=Y1TOqU+Pzx0cJ=c0oMxhMptR7=Q@mail.gmail.com>
Date:	Tue, 10 May 2011 13:26:58 -0400
From:	Eric Paris <eparis@...isplace.org>
To:	Mark Leeds <markleeds2@...il.com>
Cc:	linux-kernel@...r.kernel.org, selinux@...ts.fedoraproject.org
Subject: Re: selinux troubleshooting

On Tue, May 10, 2011 at 11:18 AM, Mark Leeds <markleeds2@...il.com> wrote:
> Hello all: I'm a total newbie with the kernel and I've never used this
> list before so excuse me if this is not the correct place to ask this
> question. or if I don't follow the positing directions correctly.
>
> I am running fedora 14.0 and when I do uname - a, I get
>
> Linux localhost.local 2.6.35.10-74.fc14.i686 #1 SMP Thu Dec 23
> 16:17:40 UTC 2010 i686 i686 i386 GNU/Linux
> :/home/markleeds/rpmbuild#
>
> But today I've been trying to run an R  job ( see www.r-project.org
> for details about R )  in the background and
> it just dies without any error messages. well, it does in the sense
> that the operating system hangs and I need to
> shut down the computer by pulling the plug out and putting it back in.
> There's no other way as far as
> I can tell because the computer just freezes essentially.

I'd say you have 2 separate problems.  The first is this problem.  If
your box really is locking up hard like this it's almost certainly
unrelated to the later SELinux denial.  Can we try to see if the
kernel is outputting any kind of traceback or error information?
There are a couple of ways to do this.  Boot into runlevel 3,
reproduce your problem, see if any kernel messages are printed on the
screen.  Set up a remote serial console and capture the console that
way.  Set up netconsole and capture the console that way.  I'd like to
know why the box locked up hard and if it's a kernel problem it
usually gives some indication on the console.

> Then I was poking around to see if I could find any info I went into
> the selinux troubleshooter.
>
> there is a red dot and two yellow dots below it. each says something.
>
> next to the red dot:  "if you do not think /usr/lib/R/bin/exec/R
> should need to map low
> memory in the kernel"

I'm betting this is an unrelated problem and likely something the R
code is doing which is generally seen as a bad idea.  I've cc'd the
fedora selinux list to help with this issue (might I suggest people
responding to this part of the issue drop lkml and people responding
to the hard lockup drop the fedora-selinux-list?)  Might you be
willing to include the output of ausearch -m AVC in a message to the
fedora selinux list?

You can make sure that SELinux is not the cause of your hard lockup by
running (as root) "setenforce 0" before you reproduce the issue.  If
you are still able to make the box lock up this is definitely not
related to SELinux.

Hope we can help!
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/