The application for this change is to allow a userspace
RAID metadata handler to check the state of an array without causing any
memory allocations. Thus not causing writeback to a raid array that might
be blocked waiting for userspace to take action.
Although that sounds like a rather, umm, optimistic application. I guess
if everything's mlocked you might get lucky.
Cc: NeilBrown <neilb@xxxxxxx>
Cc: Tejun Heo <htejun@xxxxxxxxx>
Signed-off-by: Dan Williams <dan.j.williams@xxxxxxxxx>
Has this been tested with pread()? That should work - doing an lseek+read
is plain dopey.
Can we now remove need_read_fill? Not if we want to support
open+lseek+read, I guess - this initial read might not be at offset
zero.