public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Phil Sorber <aafes@psu.edu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.15aa1
Date: Sat, 24 Nov 2001 20:39:01 +0100	[thread overview]
Message-ID: <20011124203901.Q1419@athlon.random> (raw)
In-Reply-To: <20011124085028.C1419@athlon.random> <1006629351.1470.8.camel@praetorian>
In-Reply-To: <1006629351.1470.8.camel@praetorian>; from aafes@psu.edu on Sat, Nov 24, 2001 at 02:15:50PM -0500

On Sat, Nov 24, 2001 at 02:15:50PM -0500, Phil Sorber wrote:
> On Sat, 2001-11-24 at 02:50, Andrea Arcangeli wrote:
> > Only in 2.4.15aa1: 00_iput-unmount-corruption-fix-1
> > 
> > 	Fix iput umount corruption.
> 
> Is this the problem that Al put out a patch for yesterday? And is his
> patch been tested and working?

it's an alternate fix (goes back to the pre8 way).

> 
> > Only in 2.4.15aa1: 00_read_super-stale-inode-1
> > 
> > 	If read_super fails avoid lefting stale inodes queued into
> > 	the superblock.
> 
> What is this? How dangerous is it?

pre8 and all previous kernels could left a stale inode if read_super
failed after an iget [see the discussion with Al on l-k]. this patch
should fix it in practice for all fs in the kernel.

Andrea

  parent reply	other threads:[~2001-11-24 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-24  7:50 2.4.15aa1 Andrea Arcangeli
2001-11-24  9:45 ` 2.4.15aa1 Paulo J. Matos aka PDestroy
2001-11-24 10:05   ` 2.4.15aa1 Andrea Arcangeli
2001-11-24 19:15 ` 2.4.15aa1 Phil Sorber
2001-11-24 19:34   ` 2.4.15aa1 Russell King
2001-11-24 19:39   ` Andrea Arcangeli [this message]
2001-11-26 16:14 ` 2.4.15aa1 bill davidsen

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=20011124203901.Q1419@athlon.random \
    --to=andrea@suse.de \
    --cc=aafes@psu.edu \
    --cc=linux-kernel@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