Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
	carlos@systemhalted.org, linux-parisc@vger.kernel.org
Subject: Re: [git patches] parisc bug fixes for 2.6.25
Date: Mon, 17 Mar 2008 10:52:36 -0400	[thread overview]
Message-ID: <20080317145236.GC3904@phobos.i.cabal.ca> (raw)
In-Reply-To: <20080317143859.589684E7B@hiauly1.hia.nrc.ca>

On Mon, Mar 17, 2008 at 10:38:58AM -0400, John David Anglin wrote:
> > On Sun, Mar 16, 2008 at 02:22:20PM -0400, Carlos O'Donell wrote:
> > > On Sun, Mar 16, 2008 at 1:35 PM, Kyle McMartin <kyle@mcmartin.ca> wrote:
> > > > The following changes since commit cdeeeae056a429e729ae9e914fa8142ee45bee93:
> > > >   Linus Torvalds (1):
> > > >         Linux 2.6.25-rc5
> > > 
> > > Thanks!
> > > 
> > > What hardware is this known to boot on? I want to update my base
> > > kernel for userspace testing, currently 2.6.20.
> > > 
> > 
> > no idea. it booted on my rp3440 and c8k
> 
> It also boots on my c3750 (32-bit kernel).  However, sshd still is doing
> wierd stuff.  Here's another example.
> 
> Mar 17 10:28:11 xxxxxx sshd[22586]: fatal: Privilege separation user sshd does not exist
> 

I don't see this... what is the machine running? I'm concerned maybe one
of the new syscalls is being used in glibc or something.

> This security bug leaves the system wide open to being compromised, so
> I'm not going to use it.  I like 2.6.22.19 + Kyle's compat_sys_getdents
> and irq.c patches.
> 

  reply	other threads:[~2008-03-17 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 17:35 [git patches] parisc bug fixes for 2.6.25 Kyle McMartin
2008-03-16 18:22 ` Carlos O'Donell
2008-03-16 19:21   ` Kyle McMartin
2008-03-17 14:38     ` John David Anglin
2008-03-17 14:52       ` Kyle McMartin [this message]
2008-03-17 15:23         ` John David Anglin
2008-03-17 17:53         ` John David Anglin
2008-03-17 18:54           ` John David Anglin
2008-03-17 23:43             ` John David Anglin

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=20080317145236.GC3904@phobos.i.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=carlos@systemhalted.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=linux-parisc@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox