diff options
| author | Yang Xu <xuyang2018.jy@fujitsu.com> | 2022-01-27 17:11:37 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-02-23 11:58:38 +0100 |
| commit | 04bd141c4305a8738a39571927973e26d2d1a352 (patch) | |
| tree | fe58ccaa7b317cfb964ce2b807f53b0c012037be /firmware | |
| parent | ec85569a92f17da30645e0e99f2a052196b85ca2 (diff) | |
| download | linux-stable-04bd141c4305a8738a39571927973e26d2d1a352.tar.gz linux-stable-04bd141c4305a8738a39571927973e26d2d1a352.tar.bz2 linux-stable-04bd141c4305a8738a39571927973e26d2d1a352.zip | |
selftests/zram: Adapt the situation that /dev/zram0 is being used
[ Upstream commit 01dabed20573804750af5c7bf8d1598a6bf7bf6e ]
If zram-generator package is installed and works, then we can not remove
zram module because zram swap is being used. This case needs a clean zram
environment, change this test by using hot_add/hot_remove interface. So
even zram device is being used, we still can add zram device and remove
them in cleanup.
The two interface was introduced since kernel commit 6566d1a32bf7("zram:
add dynamic device add/remove functionality") in v4.2-rc1. If kernel
supports these two interface, we use hot_add/hot_remove to slove this
problem, if not, just check whether zram is being used or built in, then
skip it on old kernel.
Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions