search for: dio_complete

...ck+0x744/0x750 [ 162.435208] __lock_acquire+0xab8/0x18c0 [ 162.435982] lock_acquire+0x48/0x68 [ 162.436678] _raw_read_lock+0x3c/0x50 [ 162.449520] jbd2_trans_will_send_data_barrier+0x44/0xc8 [ 162.450681] ext4_sync_file+0x1e0/0x330 [ 162.451535] vfs_fsync_range+0x48/0xc0 [ 162.452323] dio_complete+0x1fc/0x220 [ 162.453094] dio_bio_end_aio+0xf0/0x130 [ 162.453935] bio_endio+0xe8/0xf8 [ 162.454625] blk_update_request+0x80/0x2e8 [ 162.455450] blk_mq_end_request+0x20/0x70 [ 162.456240] virtblk_request_done+0x24/0x30 [ 162.457080] __blk_mq_complete_request+0x100/0x1b0 [ 162.458047]...

...ck+0x744/0x750 [ 162.435208] __lock_acquire+0xab8/0x18c0 [ 162.435982] lock_acquire+0x48/0x68 [ 162.436678] _raw_read_lock+0x3c/0x50 [ 162.449520] jbd2_trans_will_send_data_barrier+0x44/0xc8 [ 162.450681] ext4_sync_file+0x1e0/0x330 [ 162.451535] vfs_fsync_range+0x48/0xc0 [ 162.452323] dio_complete+0x1fc/0x220 [ 162.453094] dio_bio_end_aio+0xf0/0x130 [ 162.453935] bio_endio+0xe8/0xf8 [ 162.454625] blk_update_request+0x80/0x2e8 [ 162.455450] blk_mq_end_request+0x20/0x70 [ 162.456240] virtblk_request_done+0x24/0x30 [ 162.457080] __blk_mq_complete_request+0x100/0x1b0 [ 162.458047]...

...__lock_acquire+0xab8/0x18c0 > [ 162.435982] lock_acquire+0x48/0x68 > [ 162.436678] _raw_read_lock+0x3c/0x50 > [ 162.449520] jbd2_trans_will_send_data_barrier+0x44/0xc8 > [ 162.450681] ext4_sync_file+0x1e0/0x330 > [ 162.451535] vfs_fsync_range+0x48/0xc0 > [ 162.452323] dio_complete+0x1fc/0x220 > [ 162.453094] dio_bio_end_aio+0xf0/0x130 > [ 162.453935] bio_endio+0xe8/0xf8 > [ 162.454625] blk_update_request+0x80/0x2e8 > [ 162.455450] blk_mq_end_request+0x20/0x70 > [ 162.456240] virtblk_request_done+0x24/0x30 > [ 162.457080] __blk_mq_complete_reques...

...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 at lst.de> > CC: Goldwyn Rodrigues <rgoldwyn at suse.com> > CC: stable at vger.kernel.org > Reported-by: Mark Rutland <mark.rutland at arm.com> > F...

...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 at lst.de> > CC: Goldwyn Rodrigues <rgoldwyn at suse.com> > CC: stable at vger.kernel.org > Reported-by: Mark Rutland <mark.rutland at arm.com> > F...

i_alloc_sem has always been a bit of an odd "lock". It''s the only remaining rw_semaphore that can be released by a different thread than the one that locked it, and it''s use case in the core direct I/O code is more like a counter given that the writers already have external serialization. This series removes it in favour of a simpler counter scheme, thus getting rid

...er or member 'resume' not described in 'regulator_ops' include/linux/spi/spi.h:190: warning: Function parameter or member 'driver_override' not described in 'spi_device' fs/direct-io.c:258: warning: Excess function parameter 'offset' description in 'dio_complete' fs/libfs.c:496: warning: Excess function parameter 'available' description in 'simple_write_end' fs/posix_acl.c:647: warning: Function parameter or member 'inode' not described in 'posix_acl_update_mode' fs/posix_acl.c:647: warning: Function parameter o...

This is the next version of my patch series for teaching DRM how to automatically create debugfs nodes for drivers with MST topologies. This was originally intended just for nouveau, but has since been expanded to all DRM drivers. Cc: Maarten Lankhorst <maarten.lankhorst at linux.intel.com> Cc: Daniel Stone <daniel at fooishbar.org> Lyude Paul (4): drm/debugfs: Add support for

This series cleans up duplicated code for replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. This is a sligtly updated version of a series sent on 24 Nov 2017. --- v2: - rebased on current drm-next - dropped staging/sm750fb changes - added kernel docs for DRM helpers v3: - move kerneldoc to fbdev, where functions are implemented - split kerneldoc

This series cleans up duplicated code for replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. This is a sligtly updated version of a series sent on 24 Nov 2017. --- v2: - rebased on current drm-next - dropped staging/sm750fb changes - added kernel docs for DRM helpers v3: - move kerneldoc to fbdev, where functions are implemented - split kerneldoc