public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Jirka Kosina <jikos@jikos.cz>
Cc: Giuliano Pochini <pochini@shiny.it>, linux-kernel@vger.kernel.org
Subject: Re: FW: Linux kernel file offset pointer races
Date: Mon, 09 Aug 2004 10:33:15 +0200	[thread overview]
Message-ID: <411736CB.2040607@bio.ifi.lmu.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0408051228400.2791@twin.jikos.cz>

Jirka Kosina wrote:

> It hasn't been discussed here, but at 
> http://linux.bkbits.net:8080/linux-2.4/gnupatch@411064f7uz3rKDb73dEb4vCqbjEIdw 
> you can find a patchset fixing (some of) the mentioned problems. This 
> patchset is from 2.4.27-rc5

So this is for 2.4. What about 2.6? Distributors like RedHat have patched
their 2.6.7 kernel accordingly, but I haven't found anything similar in
the kernel tree from kernel.org. Do you know if there is any a fix for
the 2.6 tree, too?

cu,
Frank

-- 
Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik    Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17           Phone: +49 89 2180-4049
80333 Muenchen, Germany       Fax:   +49 89 2180-99-4049


  parent reply	other threads:[~2004-08-09  8:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  8:42 FW: Linux kernel file offset pointer races Giuliano Pochini
2004-08-05 10:30 ` Jirka Kosina
2004-08-07 17:15   ` Marcelo Tosatti
2004-08-11 14:26     ` Andrey Savochkin
2004-08-11 21:14       ` Marcelo Tosatti
2004-08-12  7:55         ` Andrey Savochkin
2004-08-12 13:53           ` Marcelo Tosatti
2004-08-09  8:33   ` Frank Steiner [this message]
2004-08-09 14:45     ` Alan Cox
2004-08-09 16:50       ` Jonathan Corbet
2004-08-09 17:24         ` Linus Torvalds
2004-08-10  6:08       ` Frank Steiner
2004-08-05 20:34 ` Alan Cox

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=411736CB.2040607@bio.ifi.lmu.de \
    --to=fsteiner-mail@bio.ifi.lmu.de \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pochini@shiny.it \
    /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