lkml.org 
[lkml]   [1999]   [Sep]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Possible inode.c problem for EXT2
On Fri, 24 Sep 1999, Mike Black wrote:

>Also, in fs/buffer.c in the call "init_buffer" the bh->b_size and
>bh->b_rsector are not initialized. So, if one of the "bh =" calls has an

bh->b_size is initialized before putting the buffer in the freelist.
b_rsector is initialized by ll_rw_block itself in function of the b_size
and of the b_blocknr (before calling make_request that is the one
complaining about beyond ...).

>error in inode.c then bh->b_rsector is quite likely to contain random data
>and will (possibly) die on the next ll_rw_block call. In my case I was

It's ll_rw_block that will set b_rsector.

>could use some cleaning up. I would initialize bh->b_rsector and bh->b_size

The initialization of such values is enforced by design.

Are you using software raid with some additional patches?

Andrea



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:2.601 / U:0.004 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site