All of lore.kernel.org
 help / color / mirror / Atom feed
From: "ismail dönmez" <ismail.donmez@gmail.com>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	James Morris <jmorris@redhat.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.8.1-mm1 Tty problems?
Date: Wed, 18 Aug 2004 16:27:35 +0300	[thread overview]
Message-ID: <2a4f155d04081806272275a2c0@mail.gmail.com> (raw)
In-Reply-To: <41235417.9080602@microgate.com>

On Wed, 18 Aug 2004 08:05:27 -0500, Paul Fulghum <paulkf@microgate.com> wrote:
> Stephen Smalley wrote:
> > I find that puzzling, given that flush_unauthorized_files is only called
> > if the process is changing SIDs on exec, and running less certainly
> > doesn't involve a SID transition (at least for any policy that I have
> > seen).  I tried the sequence shown with 2.6.8.1-mm1 with SELinux enabled
> > and disabled, and did not see the behavior he describes.  Is the bug
> > reproducible?  Was he running with SELinux enabled or disabled?  What
> > policy did he have loaded?
> 
> According to Ismail:
> * The problem is reproducible.
> * SELinux is disabled.
> * With the patch the problem occurs.
> * With the patch reversed, the problem went away.
> 
> Unfortunately, this appears to be mixed up with
> another 2.6.8.1-mm1 change causing udev to garble
> the creation of /dev/tty and pty devices.
> 
> Applying/reversing the controlling-tty patch in isolation
> creates/corrects the symptom with the less program,
> so there seems to be some relation.
> 
> --
> Paul Fulghum
> paulkf@microgate.com
> 


The problem ended up as a problem in Slackware's default udev.rules
file. Now I'm running vanilla -mm1 and everything works. Thank you all
for your attention!

Cheers,
ismail


-- 
Time is what you make of it

      reply	other threads:[~2004-08-18 13:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 14:08 2.6.8.1-mm1 Tty problems? ismail dönmez
2004-08-17 18:01 ` Paul Fulghum
     [not found]   ` <2a4f155d0408171116688a87f1@mail.gmail.com>
     [not found]     ` <4122501B.7000106@microgate.com>
2004-08-17 19:00       ` ismail dönmez
2004-08-17 19:31         ` Paul Fulghum
2004-08-17 19:37           ` ismail dönmez
2004-08-17 19:43           ` ismail dönmez
2004-08-17 20:05             ` Paul Fulghum
2004-08-17 20:52               ` ismail dönmez
2004-08-18  6:22               ` Olaf Hering
2004-08-18  6:34                 ` ismail dönmez
2004-08-18  6:42                   ` Olaf Hering
2004-08-18 18:58                     ` Martin Schlemmer
2004-08-19 17:28                       ` Tonnerre
2004-08-19 19:24                         ` Martin Schlemmer
2004-08-19 19:24                           ` Olaf Hering
2004-08-19 19:46                             ` Martin Schlemmer
2004-08-17 21:30             ` Martin Schlemmer
2004-08-17 21:04         ` Paul Fulghum
2004-08-17 21:36           ` Martin Schlemmer
2004-08-18  5:44             ` ismail dönmez
2004-08-18 18:43               ` Martin Schlemmer
2004-08-26 23:02               ` Greg KH
2004-08-17 21:00 ` Paul Fulghum
2004-08-18 12:22   ` Stephen Smalley
2004-08-18 13:05     ` Paul Fulghum
2004-08-18 13:27       ` ismail dönmez [this message]

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=2a4f155d04081806272275a2c0@mail.gmail.com \
    --to=ismail.donmez@gmail.com \
    --cc=akpm@osdl.org \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulkf@microgate.com \
    --cc=sds@epoch.ncsc.mil \
    /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.