Re: [patch 14/23] inodes: Support generic defragmentation

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Christoph Lameter <clameter@...>
Cc: <akpm@...>, <linux-kernel@...>, <linux-mm@...>, Mel Gorman <mel@...>
Date: Wednesday, November 7, 2007 - 6:17 am

On Tue, 6 November 2007 17:11:44 -0800, Christoph Lameter wrote:

What purpose does the return type have?


The fact that all pointers get changed makes me a bit uneasy:
	struct foo_inode v[20];
	...
	fs_get_inodes(..., v, ...);
	...
	v[0].foo_field = bar;
	
No warning, but spectacular fireworks.


NULL is legal here?  Then fs_get_inodes should check for NULL as well
and not add the offset to NULL pointers, I guess.


This linebreak can be removed.


Once more the three-bit I_DIRTY is used like a boolean value.  I don't
hold it against you, specifically.  A general review/cleanup is
necessary for that.

Jörn

-- 
"[One] doesn't need to know [...] how to cause a headache in order
to take an aspirin."
-- Scott Culp, Manager of the Microsoft Security Response Center, 2001
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[patch 14/23] inodes: Support generic defragmentation, Christoph Lameter, (Tue Nov 6, 9:11 pm)
Re: [patch 14/23] inodes: Support generic defragmentation, Jörn, (Wed Nov 7, 6:17 am)
Re: [patch 14/23] inodes: Support generic defragmentation, Christoph Lameter, (Wed Nov 7, 2:40 pm)
Re: [patch 14/23] inodes: Support generic defragmentation, Christoph Lameter, (Wed Nov 7, 3:00 pm)
Re: [patch 14/23] inodes: Support generic defragmentation, Andreas Schwab, (Wed Nov 7, 6:35 am)