Skip to contentSkip to conversation

Backport dc48e56d761610da4ea1088d1bea0a030b8e3e43

DISCUSSION Jens Axboe 3 participants 3 messages May 16, 2015 – May 26, 2015 Stable branch

lore
Share & tools
lore

Jens Axboe

author
#0 lore raw

Hi,

This commit wasn't marked stable, and it should have been marked with a:

Fixes 6098b45b32 ("aio: block exit_aio() until all context requests are

completed")

Can we get dc48e56d7616 added to the stable queue for any stable kernel that backports 6098b45b32?

Thanks,

Signature · 1 line
Jens Axboe
#1 lore raw
Quoted 9 lines · Jens Axboe

Hi,

This commit wasn't marked stable, and it should have been marked with a:

Fixes 6098b45b32 ("aio: block exit_aio() until all context requests are

completed")

Can we get dc48e56d7616 added to the stable queue for any stable kernel that backports 6098b45b32?

Ok, will queue this up for the next round of patches, thanks for letting us know.

greg k-h

#2 lore raw
In reply to Jens Axboe
Quoted 9 lines · Jens Axboe

Hi,

This commit wasn't marked stable, and it should have been marked with a:

Fixes 6098b45b32 ("aio: block exit_aio() until all context requests are

completed")

Can we get dc48e56d7616 added to the stable queue for any stable kernel that backports 6098b45b32?

Hmm, not an easy one. To 3.12, I picked also:
commit 4b70ac5fd9b58bfaa5f25b4ea48f528aefbf3308

Author: Oleg Nesterov <[email protected]>
Date:   Wed Apr 30 19:02:48 2014 +0200
    aio: change exit_aio() to load mm->ioctx_table once and avoid

rcu_read_lock()

Without that, the backport was almost impossible.

thanks,

Signature · 2 lines
js
suse labs