public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Andreas Dilger <adilger@sun.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Sami Liedes <sliedes@cc.hut.fi>,
	Andrew Morton <akpm@linux-foundation.org>,
	bugme-daemon@bugzilla.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 11266] New: unable to handle kernel paging request in ext2_free_blocks
Date: Tue, 19 Aug 2008 11:13:39 +0200	[thread overview]
Message-ID: <20080819091339.GE14799@duck.suse.cz> (raw)
In-Reply-To: <20080819032410.GE3392@webber.adilger.int>

On Mon 18-08-08 21:24:10, Andreas Dilger wrote:
> On Aug 18, 2008  22:21 +0530, Aneesh Kumar wrote:
> > > +static int ext2_block_in_group(struct super_block *sb,
> > > +			unsigned int block_group, ext2_fsblk_t block)
> > > +{
> > > +	if (block < ext2_group_first_block_no(sb, block_group))
> > > +		return 0;
> > > +	if (block >= ext2_group_first_block_no(sb, block_group) +
> > > +	    EXT2_BLOCKS_PER_GROUP(sb))
> > > +		return 0;
> > > +	return 1;
> > > +}
> > > +
> > >  /*
> > >   * Read the bitmap for a given block_group,and validate the
> > >   * bits for block/inode/inode tables are set in the bitmaps
> > > @@ -129,6 +140,24 @@ read_block_bitmap(struct super_block *sb, unsigned int block_group)
> > >  	desc = ext2_get_group_desc(sb, block_group, NULL);
> > >  	if (!desc)
> > >  		return NULL;
> > > +	if (!ext2_block_in_group(sb, block_group,
> > > +				le32_to_cpu(desc->bg_block_bitmap)) ||
> > > +	    !ext2_block_in_group(sb, block_group,
> > > +				le32_to_cpu(desc->bg_inode_bitmap)) ||
> > > +	    !ext2_block_in_group(sb, block_group,
> > > +				le32_to_cpu(desc->bg_inode_table)) ||
> > > +	    !ext2_block_in_group(sb, block_group,
> > > +				le32_to_cpu(desc->bg_inode_table) +
> > > +				EXT2_SB(sb)->s_itb_per_group - 1)) {
> 
> Isn't equivalent checking done in ext2_check_descriptors()?  It would make
> sense to abstract out the "check one group and return error" code and use
> it in both places.
  Actually yes, it is. Good point. Sami, is it the case that you have
mounted the filesystem, then intentionally corrupted it and after that
the kernel oopsed (as opposed to first corrupting the filesystem image and
mounting it after that)? That would explain how corrupted values could get
to read_block_bitmap() even though ext2_check_descriptors() checked them.

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2008-08-19  9:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11266-10286@http.bugzilla.kernel.org/>
2008-08-07 17:52 ` [Bugme-new] [Bug 11266] New: unable to handle kernel paging request in ext2_free_blocks Andrew Morton
     [not found] ` <0K5800031SEDU2@smtp02.hut-mail>
2008-08-07 20:07   ` Sami Liedes
2008-08-07 20:28     ` Sami Liedes
2008-08-18 14:58       ` Jan Kara
2008-08-18 16:51         ` Aneesh Kumar K.V
2008-08-19  3:24           ` Andreas Dilger
2008-08-19  9:13             ` Jan Kara [this message]
2008-08-19 10:51               ` Sami Liedes
2008-08-20 10:25                 ` Jan Kara
2008-08-20 13:29                   ` Sami Liedes
2008-08-20 19:07                   ` Andreas Dilger
2008-11-02  5:27                     ` Sami Liedes
2008-08-19 21:43         ` Sami Liedes

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=20080819091339.GE14799@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sliedes@cc.hut.fi \
    /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