summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2018-02-26 12:51:43 +0100
committerJens Axboe <axboe@kernel.dk>2018-02-26 09:05:35 -0700
commitd9c10e5b8863cfb6886d1640386455075c6e979d (patch)
treeae004ec25c97c1db1ff9804f4bb6b147ca85f786 /arch
parentba989a01469d027861e55c8f1121edadef757797 (diff)
downloadlinux-stable-d9c10e5b8863cfb6886d1640386455075c6e979d.tar.gz
linux-stable-d9c10e5b8863cfb6886d1640386455075c6e979d.tar.bz2
linux-stable-d9c10e5b8863cfb6886d1640386455075c6e979d.zip
direct-io: Fix sleep in atomic due to sync AIO
Commit e864f39569f4 "fs: add RWF_DSYNC aand RWF_SYNC" added additional way for direct IO to become synchronous and thus trigger fsync from the IO completion handler. Then commit 9830f4be159b "fs: Use RWF_* flags for AIO operations" allowed these flags to be set for AIO as well. However that commit forgot to update the condition checking whether the IO completion handling should be defered to a workqueue and thus AIO DIO with RWF_[D]SYNC set will call fsync() from IRQ context resulting in sleep in atomic. Fix the problem by checking directly iocb flags (the same way as it is done in dio_complete()) instead of checking all conditions that could lead to IO being synchronous. CC: Christoph Hellwig <hch@lst.de> CC: Goldwyn Rodrigues <rgoldwyn@suse.com> CC: stable@vger.kernel.org Reported-by: Mark Rutland <mark.rutland@arm.com> Tested-by: Mark Rutland <mark.rutland@arm.com> Fixes: 9830f4be159b29399d107bffb99e0132bc5aedd4 Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions