diff options
| author | Sergey Senozhatsky <[email protected]> | 2014-04-07 22:38:19 +0000 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2014-04-07 23:36:02 +0000 |
| commit | d61f98c70e8b0d324e8e83be2ed546d6295e63f3 (patch) | |
| tree | ef4c07ad1d867c0ad97d0478decd78ba209a9387 /fs/proc/array.c | |
| parent | zram: add lz4 algorithm backend (diff) | |
| download | kernel-d61f98c70e8b0d324e8e83be2ed546d6295e63f3.tar.gz kernel-d61f98c70e8b0d324e8e83be2ed546d6295e63f3.zip | |
zram: move comp allocation out of init_lock
While fixing lockdep spew of ->init_lock reported by Sasha Levin [1],
Minchan Kim noted [2] that it's better to move compression backend
allocation (using GPF_KERNEL) out of the ->init_lock lock, same way as
with zram_meta_alloc(), in order to prevent the same lockdep spew.
[1] https://lkml.org/lkml/2014/2/27/337
[2] https://lkml.org/lkml/2014/3/3/32
Signed-off-by: Sergey Senozhatsky <[email protected]>
Reported-by: Minchan Kim <[email protected]>
Acked-by: Minchan Kim <[email protected]>
Cc: Sasha Levin <[email protected]>
Acked-by: Jerome Marchand <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'fs/proc/array.c')
0 files changed, 0 insertions, 0 deletions