mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: "O.Sezer" <sezeroz@ttnet.net.tr>,
	jbaron@redhat.com, alan@lxorguk.ukuu.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.28-rc1
Date: Thu, 28 Oct 2004 08:01:37 -0200	[thread overview]
Message-ID: <20041028100137.GI4815@logos.cnet> (raw)
In-Reply-To: <20041027025222.GB9375@ip68-4-98-123.oc.oc.cox.net>

On Tue, Oct 26, 2004 at 07:52:22PM -0700, Barry K. Nathan wrote:
> On Tue, Oct 26, 2004 at 05:02:44PM +0300, O.Sezer wrote:
> > There are many lost/forgotten patches posted here on lkml. Since 2.4.28
> > is near and 2.4 is going into "deep maintainance" mode soon, I gathered
> > a short list of some of them.  There, sure, are many more of them,  but
> > here it goes.
> > I think they deserve a re-review and re-consideration for inclusion.
> [snip]
> 
> Here's another one:
> Jason Baron: 2.4.28-pre3 tty/ldisc fixes
> http://marc.theaimsgroup.com/?l=linux-kernel&m=109604869516678&w=2
> 
> AFAICT the above patch is the fix for:
> CAN-2004-0814: Linux terminal layer races
> http://marc.theaimsgroup.com/?l=bugtraq&m=109837405025108&w=2
> 
> This patch seems to be working fine for me, but I don't know if anyone
> else has really tested it at all, nor do I know (one way or the other)
> if the security issues are serious enough to apply this for 2.4.28-rc
> and not 2.4.29-pre. Also, I'm running on a single-processor system with
> no HyperThreading, so if there are any SMP-related issues then I have no
> way of experiencing them.
> 
> Anyway, since it's a security fix (unless I'm mistaken), I guess it's
> worth considering for inclusion...

Hi Barry,

I think this should be applied as well. The next 
-pre makes me more comfortable.

Jason, Alan?

  reply	other threads:[~2004-10-28 12:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 14:02 O.Sezer
2004-10-26 20:33 ` Marcelo Tosatti
2004-10-26 23:28   ` Dave Jones
2004-10-27 12:40   ` O.Sezer
2004-10-27 14:29     ` Dave Jones
2004-10-27 15:29       ` O.Sezer
2004-10-27 18:58         ` Dave Jones
2004-10-28  9:54     ` Marcelo Tosatti
2004-10-28 13:28       ` O.Sezer
2004-10-28 14:29         ` O.Sezer
2004-10-28  1:19   ` Pete Zaitcev
2004-10-28  4:26   ` Jeff Garzik
2004-10-28 12:53   ` Russell King
2004-11-11 18:30   ` Roger Luethi
2004-10-27  2:52 ` Barry K. Nathan
2004-10-28 10:01   ` Marcelo Tosatti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-22 18:59 Marcelo Tosatti
2004-10-22 22:14 ` Jan Engelhardt
2004-10-23 10:43   ` Marcelo Tosatti
2004-10-23 19:54     ` Jan Engelhardt
2004-10-23 13:30 ` Paul Fulghum
2004-10-23 11:39   ` Marcelo Tosatti

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=20041028100137.GI4815@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=barryn@pobox.com \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sezeroz@ttnet.net.tr \
    /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

Powered by JetHome