mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: Linux kernel development list <linux-kernel@vger.kernel.org>,
	Linux FS development list <linux-fsdevel@vger.kernel.org>,
	Alexander Viro <aviro@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [linux-lvm] EXT2-fs panic (device lvm(58,0)):
Date: Fri, 23 Mar 2001 01:39:14 +0000	[thread overview]
Message-ID: <20010323013914.M7756@redhat.com> (raw)
In-Reply-To: <200103072035.f27KZ5V20201@webber.adilger.net>
In-Reply-To: <200103072035.f27KZ5V20201@webber.adilger.net>; from adilger@turbolinux.com on Wed, Mar 07, 2001 at 01:35:05PM -0700

Hi,

On Wed, Mar 07, 2001 at 01:35:05PM -0700, Andreas Dilger wrote:

> The only remote possibility is in ext2_free_blocks() if block+count
> overflows a 32-bit unsigned value.  Only 2 places call ext2_free_blocks()
> with a count != 1, and ext2_free_data() looks to be OK.  The other
> possibility is that i_prealloc_count is bogus - that is it!  Nowhere
> is i_prealloc_count initialized to zero AFAICS.
> 
Did you ever push this to Alan and/or Linus?  This looks pretty
important!

Cheers,
 Stephen

> ==========================================================================
> diff -ru linux/fs/ext2/ialloc.c.orig linux/fs/ext2/ialloc.c
> --- linux/fs/ext2/ialloc.c.orig	Fri Dec  8 18:35:54 2000
> +++ linux/fs/ext2/ialloc.c	Wed Mar  7 12:22:11 2001
> @@ -432,6 +444,8 @@
>  	inode->u.ext2_i.i_file_acl = 0;
>  	inode->u.ext2_i.i_dir_acl = 0;
>  	inode->u.ext2_i.i_dtime = 0;
> +	inode->u.ext2_i.i_prealloc_count = 0;
>  	inode->u.ext2_i.i_block_group = i;
>  	if (inode->u.ext2_i.i_flags & EXT2_SYNC_FL)
>  		inode->i_flags |= S_SYNC;
> diff -ru linux/fs/ext2/inode.c.orig linux/fs/ext2/inode.c
> --- linux/fs/ext2/inode.c.orig	Tue Jan 16 01:29:29 2001
> +++ linux/fs/ext2/inode.c	Wed Mar  7 12:05:47 2001
> @@ -1048,6 +1038,8 @@
>  			(((__u64)le32_to_cpu(raw_inode->i_size_high)) << 32);
> 	}
>  	inode->i_generation = le32_to_cpu(raw_inode->i_generation);
> +	inode->u.ext2_i.i_prealloc_count = 0;
>  	inode->u.ext2_i.i_block_group = block_group;
>  
>  	/*

  reply	other threads:[~2001-03-23  1:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07 20:35 Andreas Dilger
2001-03-23  1:39 ` Stephen C. Tweedie [this message]
2001-03-23  2:04   ` Alexander Viro
2001-03-23  5:48     ` Andreas Dilger
2001-03-23 11:44       ` Alexander Viro
2001-03-23 19:11         ` Andreas Dilger

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=20010323013914.M7756@redhat.com \
    --to=sct@redhat.com \
    --cc=adilger@turbolinux.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=aviro@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®