Re: [PATCH] ext4: memory leakage in ext4_discard_preallocations

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: tytso
Date: Thursday, March 18, 2010 - 10:46 am

>  		ext4_get_group_no_and_offset(sb, pa->pa_pstart, &group, NULL);

Hmm, I'm not sure that BUG() is appropriate here.  If there is an
I/O error reading the block bitmap, #1, retrying isn't going to help,
and #2, bringing down the entire system just because of an I/O error
in reading the block bitmap doesn't seem right.

Right now, if there is a problem, we just end up leaving the
preallocated list on the inode.  Does that cause problems later on
down the line which you have observed?

					- Ted


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] ext4: memory leakage in ext4_discard_prealloca ..., tytso, (Thu Mar 18, 10:46 am)
Re: [PATCH] ext4: memory leakage in ext4_discard_prealloca ..., Aneesh Kumar K. V, (Fri Mar 26, 1:37 am)