On Wed, Aug 12, 2015 at 10:18:37AM -0700, Jaegeuk Kim wrote: > > 1041 err = read_node_page(apage, READA); > > 1042 f2fs_put_page(apage, err ? 1 : 0); > > > > In the old code we took errors into consideration but now we treat them > > as LOCKED_PAGE. Is that intentional? A lot of the other callers in > > that patch still check for errors... > > This is just for read-ahead node page function. > So, yes, if it returns LOCKED_PAGE or any error, the page must be unlocked > via f2fs_put_page(1). > Otherwise, end_io will unlock the page. > > Hmm, any workaround to avoid that warning? >
No, it's fine. Just ignore it. regards, dan carpenter ------------------------------------------------------------------------------ _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
