From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH 2/7] omfs: add inode routines
Date: 27 Mar 2008 07:13:50 +0100
Message-ID: <87k5jon17l.fsf@basil.nowhere.org>
References: <1206578760-9050-2-git-send-email-me@bobcopeland.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
To: Bob Copeland <me@bobcopeland.com>
Return-path: <linux-kernel-owner+glk-linux-kernel-3=40m.gmane.org-S1758094AbYC0GOG@vger.kernel.org>
In-Reply-To: <1206578760-9050-2-git-send-email-me@bobcopeland.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

Bob Copeland <me@bobcopeland.com> writes:
> +
> +	bitmap_size = (sbi->s_num_blocks + 7) / 8;
> +	array_size = (bitmap_size + sb->s_blocksize - 1) / sb->s_blocksize;
> +
> +	sbi->s_imap_size = array_size;
> +	sbi->s_imap = kzalloc(array_size * sizeof(unsigned long), GFP_KERNEL);


If the array can be really 300k you should probably have a vmalloc fallback
here.

-Andi