linux-kernel - Re: [PATCH 2/2] xfs: stop using kmalloc in xfs_buf_get

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]

Date:	Wed, 7 Mar 2007 18:15:47 +0100
From:	Christoph Hellwig <hch@....de>
To:	Michael Nishimoto <miken@...mi.com>
Cc:	Christoph Hellwig <hch@....de>, xfs@....sgi.com,
	ecashin@...aid.com, akpm@...l.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] xfs: stop using kmalloc in xfs_buf_get_noaddr

On Wed, Mar 07, 2007 at 09:04:53AM -0800, Michael Nishimoto wrote:
> Incore log buffers are not always a power of two of the page size.
> In particular, when xfs is running over software raid devices, the
> log buffers are allocated to match the size of a stripe.
> 
> However, they are always a multiple of PAGE_SIZE, so we are still safe.

It's not actually about beeing safe - any allocation is still safe
with this patch.  The issue is just that we waste memory because
we round up allocations to the next page size.

The power of two bit is actually wrong in this mail, it was about
another optimization I have that needs some more testing first.

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