linux-kernel - Re: [PATCH 01/11] ext3: Get rid of extenddisksize parameter of ext3_get_blocks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090617102810.GA29931@wotan.suse.de>
Date:	Wed, 17 Jun 2009 12:28:10 +0200
From:	Nick Piggin <npiggin@...e.de>
To:	Jan Kara <jack@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 01/11] ext3: Get rid of extenddisksize parameter of ext3_get_blocks_handle()

On Mon, Jun 15, 2009 at 07:59:48PM +0200, Jan Kara wrote:
> Get rid of extenddisksize parameter of ext3_get_blocks_handle(). This seems to
> be a relict from some old days and setting disksize in this function does not
> make much sence. Currently it was set only by ext3_getblk().  Since the
> parameter has some effect only if create == 1, it is easy to check that the
> three callers which end up calling ext3_getblk() with create == 1 (ext3_append,
> ext3_quota_write, ext3_mkdir) do the right thing and set disksize themselves.
> 
> Signed-off-by: Jan Kara <jack@...e.cz>

I guess something like this should just go in this merge window if
ext3 developers are happy with it? There is no real reason to keep
it with the main patchset is there?


--
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/