mask value ATH10K_FW_CRASH_DUMP_RAM_DATA is not mandatory to get iram
mem layout. So introduced ath10k_coredump_get_hw_mem_layout to copy
hardware memory layout.
This fixes the below boot error:
[ 17.468882] ath10k_pci 0000:06:00.0: failed to copy target iram contents: -12
[ 17.513925] ath10k_pci 0000:06:00.0: could not init core (-12)
[ 17.517635] ath10k_pci 0000:06:00.0: could not probe fw (-12)
Ignore: yes
Signed-off-by: Andrea Righi <email address hidden>
271cde0...
by
Stephen Brennan <email address hidden>
ext4: use ext4_grp_locked_error in mb_find_extent
Commit 5d1b1b3f492f ("ext4: fix BUG when calling ext4_error with locked
block group") introduces ext4_grp_locked_error to handle unlocking a
group in error cases. Otherwise, there is a possibility of a sleep while
atomic. However, since 43c73221b3b1 ("ext4: replace BUG_ON with WARN_ON
in mb_find_extent()"), mb_find_extent() has contained a ext4_error()
call while a group spinlock is held. Replace this with
ext4_grp_locked_error.
Fixes: 43c73221b3b1 ("ext4: replace BUG_ON with WARN_ON in mb_find_extent()")
Cc: <email address hidden> # 4.14+
Signed-off-by: Stephen Brennan <email address hidden>
Reviewed-by: Lukas Czerner <email address hidden>
Reviewed-by: Junxiao Bi <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Theodore Ts'o <email address hidden>
(cherry picked from commit cd84bbbac12a173a381a64c6ec8b76a5277b87b5)
Signed-off-by: Andrea Righi <email address hidden>
ext4: remove check for zero nr_to_scan in ext4_es_scan()
After converting fs shrinkers to new scan/count API, we are no longer
pass zero nr_to_scan parameter to detect the number of objects to free,
just remove this check.
Fixes: 1ab6c4997e04 ("fs: convert fs shrinkers to new scan/count API")
Cc: <email address hidden> # 3.12+
Signed-off-by: Zhang Yi <email address hidden>
Reviewed-by: Jan Kara <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Theodore Ts'o <email address hidden>
(cherry picked from commit e5e7010e5444d923e4091cafff61d05f2d19cada)
Signed-off-by: Andrea Righi <email address hidden>
ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
The cache_cnt parameter of tracepoint ext4_es_shrink_exit means the
remaining cache count after shrink, but now it is the cache count before
shrink, fix it by read sbi->s_extent_cache_cnt again.
Fixes: 1ab6c4997e04 ("fs: convert fs shrinkers to new scan/count API")
Cc: <email address hidden> # 3.12+
Signed-off-by: Zhang Yi <email address hidden>
Reviewed-by: Jan Kara <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Theodore Ts'o <email address hidden>
(cherry picked from commit 4fb7c70a889ead2e91e184895ac6e5354b759135)
Signed-off-by: Andrea Righi <email address hidden>
c6a8313...
by
Yang Yingliang <email address hidden>
ext4: return error code when ext4_fill_flex_info() fails
After commit c89128a00838 ("ext4: handle errors on
ext4_commit_super"), 'ret' may be set to 0 before calling
ext4_fill_flex_info(), if ext4_fill_flex_info() fails ext4_mount()
doesn't return error code, it makes 'root' is null which causes crash
in legacy_get_tree().
Fixes: c89128a00838 ("ext4: handle errors on ext4_commit_super")
Reported-by: Hulk Robot <email address hidden>
Cc: <email address hidden> # v4.18+
Signed-off-by: Yang Yingliang <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Theodore Ts'o <email address hidden>
(cherry picked from commit 8f6840c4fd1e7bd715e403074fb161c1a04cda73)
Signed-off-by: Andrea Righi <email address hidden>
