[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140929193823.GJ6835@localhost>
Date: Mon, 29 Sep 2014 15:38:23 -0400
From: Bob Copeland <me@...copeland.com>
To: Fabian Frederick <fabf@...net.be>
Cc: linux-kernel@...r.kernel.org,
linux-karma-devel@...ts.sourceforge.net,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH V2 resend] FS/OMFS: block number sanity check during
fill_super operation
On Mon, Sep 29, 2014 at 07:07:08PM +0200, Fabian Frederick wrote:
> This patch defines maximum block number to 2^31.
> It also converts bitmap_size and array_size to
> unsigned int in omfs_get_imap
>
> Suggested-By: Linus Torvalds <torvalds@...ux-foundation.org>
> Suggested-By: Bob Copeland <me@...copeland.com>
> Cc: Linus Torvalds <torvalds@...ux-foundation.org>
> Cc: Bob Copeland <me@...copeland.com>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
> Signed-off-by: Fabian Frederick <fabf@...net.be>
> ---
> This is untested.
Acked-by: Bob Copeland <me@...copeland.com>
I also gave it a quick test. For just plain corruption of s_num_blocks,
there's a later check that one would normally hit since the number is
stored in a second place, and we compare them. But if both
omfs_rb->r_num_blocks and sbi->s_num_blocks are the same insane number, I
agree we should give up here.
--
Bob Copeland %% www.bobcopeland.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists