af402ab2b0
if ore_write() fails, we would unlock the pages of pcol, which is now empty, rather than pcol_copy which owns the pages when ore_write() is called. this means that no pages will actually be unlocked (pcol.nr_pages == 0) and the writing process (more accurately, the syncing process) will hang waiting for a writeback notification that never comes. moreover, if ore_write() fails, pcol_free() is called for pcol, whereas pcol_copy is the object owning the ore_io_state, thus leaking the ore_io_state. [Boaz] I have simplified Idan's original patch a bit, everything else still holds Signed-off-by: Idan Kedar <idank@tonian.com> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com> |
||
---|---|---|
.. | ||
BUGS | ||
common.h | ||
dir.c | ||
exofs.h | ||
file.c | ||
inode.c | ||
Kbuild | ||
Kconfig | ||
Kconfig.ore | ||
namei.c | ||
ore_raid.c | ||
ore_raid.h | ||
ore.c | ||
super.c | ||
symlink.c | ||
sys.c |