On Fri, 19 Dec 2014 12:13:50 +0300 Dmitry Monakhov <[email protected]> wrote:
> --- a/Documentation/filesystems/fiemap.txt
> +++ b/Documentation/filesystems/fiemap.txt
> @@ -196,7 +196,8 @@ struct fiemap_extent_info {
> };
>
> It is intended that the file system should not need to access any of this
> -structure directly.
> +structure directly. Filesystem handlers should be tolerant to signals and
> return
> +EINTR once fatal signal received.
Thanks. I was concerned about userspace effects and back-compatibility
issues, because I'd misread fatal_signal_pending() as signal_pending().
Because it uses fatal_signal_pending(), the effects of this change
should be indiscernible to userspace, yes?
I'm now wondering if the above doc update is unneeded and incorrect.
Is it likely that the fs handler (fiemap_fill_next_extent) will ever
consume a large amount of time? If not then we can leave the logic in
__generic_block_fiemap() and not bother callees.
The fix only addresses filesystems which use generic_block_fiemap().
Presumably ocfs2, btrfs, nilfs2, lustre and xfs remain vulnerable to
the problem you identified?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
