~vicamo/+git/ubuntu-kernel:bug-1939937/ath10k-dont-fail-iram/hirsute

Last commit made on 2021-09-27
Get this branch:
git clone -b bug-1939937/ath10k-dont-fail-iram/hirsute https://git.launchpad.net/~vicamo/+git/ubuntu-kernel
Only You-Sheng Yang can upload to this branch. If you are You-Sheng Yang please log in for upload directions.

Branch merges

Branch information

Name:
bug-1939937/ath10k-dont-fail-iram/hirsute
Repository:
lp:~vicamo/+git/ubuntu-kernel

Recent commits

b3ef753... by You-Sheng Yang

Bug 1939937: ath10k: don't fail if IRAM write fails

6844dfa... by Abinaya Kalaiselvan <email address hidden>

UBUNTU: SAUCE: ath10k: Fix device boot error

BugLink: https://bugs.launchpad.net/bugs/1939937

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)

Tested-on: QCA9984 X86 10.4-3.9.0.2-00139

Fixes: 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
Signed-off-by: Abinaya Kalaiselvan <email address hidden>
Signed-off-by: Jouni Malinen <email address hidden>
Reported-by: kernel test robot <email address hidden>
Patchwork-Id: 12490353
Signed-off-by: Kalle Valo <email address hidden>
(cherry picked from
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=master-pending&id=37a86881331e1451ec357b1fc6738c34fe5230c1)
Signed-off-by: You-Sheng Yang <email address hidden>

7d77830... by Stefan Bader

UBUNTU: Ubuntu-5.11.0-38.42

Signed-off-by: Stefan Bader <email address hidden>

646f930... by Stefan Bader

UBUNTU: debian/dkms-versions -- update from kernel-versions (main/2021.09.27)

BugLink: https://bugs.launchpad.net/bugs/1786013
Signed-off-by: Stefan Bader <email address hidden>

33e3a79... by Stefan Bader

UBUNTU: link-to-tracker: update tracking bug

BugLink: https://bugs.launchpad.net/bugs/1944863
Properties: no-test-build
Signed-off-by: Stefan Bader <email address hidden>

30189ec... by Kai-Heng Feng

drm/i915/dp: Use max params for panels < eDP 1.4

BugLink: https://bugs.launchpad.net/bugs/1936708

Users reported that after commit 2bbd6dba84d4 ("drm/i915: Try to use
fast+narrow link on eDP again and fall back to the old max strategy on
failure"), the screen starts to have wobbly effect.

Commit a5c936add6a2 ("drm/i915/dp: Use slow and wide link training for
everything") doesn't help either, that means the affected eDP 1.2 panels
only work with max params.

So use max params for panels < eDP 1.4 as Windows does to solve the
issue.

v3:
 - Do the eDP rev check in intel_edp_init_dpcd()

v2:
 - Check eDP 1.4 instead of DPCD 1.1 to apply max params

Cc: <email address hidden>
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/3714
Fixes: 2bbd6dba84d4 ("drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure")
Fixes: a5c936add6a2 ("drm/i915/dp: Use slow and wide link training for everything")
Suggested-by: Ville Syrjälä <email address hidden>
Signed-off-by: Kai-Heng Feng <email address hidden>
Signed-off-by: Ville Syrjälä <email address hidden>
Link: https://patchwork.freedesktop<email address hidden>
(cherry picked from commit d7f213c131adf0bec8b731553eb82990cdac265d)
Signed-off-by: Jani Nikula <email address hidden>
(cherry picked from commit c8dead5751b81dfa6b10449b740ed1062ff670c5)
Signed-off-by: Kai-Heng Feng <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Kelsey Skunberg <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

9a9def7... by Kamal Mostafa

UBUNTU: upstream stable to v5.10.62, v5.13.14

BugLink: https://bugs.launchpad.net/bugs/1944610

Ignore: yes
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

a060e3f... by Eric Biggers <email address hidden>

ubifs: report correct st_size for encrypted symlinks

BugLink: https://bugs.launchpad.net/bugs/1944610

commit 064c734986011390b4d111f1a99372b7f26c3850 upstream.

The stat() family of syscalls report the wrong size for encrypted
symlinks, which has caused breakage in several userspace programs.

Fix this by calling fscrypt_symlink_getattr() after ubifs_getattr() for
encrypted symlinks. This function computes the correct size by reading
and decrypting the symlink target (if it's not already cached).

For more details, see the commit which added fscrypt_symlink_getattr().

Fixes: ca7f85be8d6c ("ubifs: Add support for encrypted symlinks")
Cc: <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Eric Biggers <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

caf2f5d... by Eric Biggers <email address hidden>

f2fs: report correct st_size for encrypted symlinks

BugLink: https://bugs.launchpad.net/bugs/1944610

commit 461b43a8f92e68e96c4424b31e15f2b35f1bbfa9 upstream.

The stat() family of syscalls report the wrong size for encrypted
symlinks, which has caused breakage in several userspace programs.

Fix this by calling fscrypt_symlink_getattr() after f2fs_getattr() for
encrypted symlinks. This function computes the correct size by reading
and decrypting the symlink target (if it's not already cached).

For more details, see the commit which added fscrypt_symlink_getattr().

Fixes: cbaf042a3cc6 ("f2fs crypto: add symlink encryption")
Cc: <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Eric Biggers <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

13682ca... by Eric Biggers <email address hidden>

ext4: report correct st_size for encrypted symlinks

BugLink: https://bugs.launchpad.net/bugs/1944610

commit 8c4bca10ceafc43b1ca0a9fab5fa27e13cbce99e upstream.

The stat() family of syscalls report the wrong size for encrypted
symlinks, which has caused breakage in several userspace programs.

Fix this by calling fscrypt_symlink_getattr() after ext4_getattr() for
encrypted symlinks. This function computes the correct size by reading
and decrypting the symlink target (if it's not already cached).

For more details, see the commit which added fscrypt_symlink_getattr().

Fixes: f348c252320b ("ext4 crypto: add symlink encryption")
Cc: <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Eric Biggers <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>