~vicamo/+git/ubuntu-kernel:bug-1866734/fix-selftest-retry-v2/eoan

Last commit made on 2020-03-16
Get this branch:
git clone -b bug-1866734/fix-selftest-retry-v2/eoan 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-1866734/fix-selftest-retry-v2/eoan
Repository:
lp:~vicamo/+git/ubuntu-kernel

Recent commits

5791a39... by You-Sheng Yang

Bug 1866734: Input: i8042 - fix the selftest retry logic

1e0feed... by You-Sheng Yang

Input: i8042 - fix the selftest retry logic

It returns -NODEV at the first selftest timeout, so the retry logic
doesn't work. Move the return outside of the while loop to make it real
retry 5 times before returns -ENODEV.

BTW, the origin loop will retry 6 times, also fix this.

Signed-off-by: You-Sheng Yang <email address hidden>
(backported from
https://<email address hidden>/)

65805e6... by Pavel Zakharov <email address hidden>

scsi: Revert "target/core: Inline transport_lun_remove_cmd()"

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

Commit 83f85b8ec305 postponed the percpu_ref_put(&se_cmd->se_lun->lun_ref)
call from command completion to the time when the final command reference
is dropped. That approach is not compatible with the iSCSI target driver
because the iSCSI target driver keeps the command with the highest stat_sn
after it has completed until the next command is received (see also
iscsit_ack_from_expstatsn()). Fix this regression by reverting commit
83f85b8ec305.

Fixes: 83f85b8ec305 ("scsi: target/core: Inline transport_lun_remove_cmd()")
Cc: Pavel Zakharov <email address hidden>
Cc: Mike Christie <email address hidden>
Cc: <email address hidden>
Link: https://<email address hidden>
Reported-by: Pavel Zakharov <email address hidden>
Signed-off-by: Bart Van Assche <email address hidden>
Signed-off-by: Martin K. Petersen <email address hidden>
(cherry picked from commit c14335ebb92a98646ddbf447e6cacc66de5269ad)
Acked-by: Andrea Righi <email address hidden>
Acked-by: Seth Forshee <email address hidden>
Signed-off-by: Kleber Sacilotto de Souza <email address hidden>

59ee1aa... by AceLan Kao

UBUNTU: SAUCE: platform/x86: dell-uart-backlight: add get_display_mode command

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

ODM asks us to use get_display_mode command to confirm the scalar's
behavior, and Windows use this command, too.
To align the behavior with Windows, remove get_scalar_status command and
replace it with get_display_mode.

Signed-off-by: AceLan Kao <email address hidden>
Acked-by: Kleber Sacilotto de Souza <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Signed-off-by: Kleber Sacilotto de Souza <email address hidden>

74a69c2... by Kamal Mostafa

UBUNTU: upstream stable to v4.19.103, v5.4.19

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

Ignore: yes
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>

3102e40... by Christophe Leroy <email address hidden>

powerpc/kuap: Fix set direction in allow/prevent_user_access()

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

[ Upstream commit 1d8f739b07bd538f272f60bf53f10e7e6248d295 ]

__builtin_constant_p() always return 0 for pointers, so on RADIX
we always end up opening both direction (by writing 0 in SPR29):

  0000000000000170 <._copy_to_user>:
  ...
   1b0: 4c 00 01 2c isync
   1b4: 39 20 00 00 li r9,0
   1b8: 7d 3d 03 a6 mtspr 29,r9
   1bc: 4c 00 01 2c isync
   1c0: 48 00 00 01 bl 1c0 <._copy_to_user+0x50>
     1c0: R_PPC64_REL24 .__copy_tofrom_user
  ...
  0000000000000220 <._copy_from_user>:
  ...
   2ac: 4c 00 01 2c isync
   2b0: 39 20 00 00 li r9,0
   2b4: 7d 3d 03 a6 mtspr 29,r9
   2b8: 4c 00 01 2c isync
   2bc: 7f c5 f3 78 mr r5,r30
   2c0: 7f 83 e3 78 mr r3,r28
   2c4: 48 00 00 01 bl 2c4 <._copy_from_user+0xa4>
     2c4: R_PPC64_REL24 .__copy_tofrom_user
  ...

Use an explicit parameter for direction selection, so that GCC
is able to see it is a constant:

  00000000000001b0 <._copy_to_user>:
  ...
   1f0: 4c 00 01 2c isync
   1f4: 3d 20 40 00 lis r9,16384
   1f8: 79 29 07 c6 rldicr r9,r9,32,31
   1fc: 7d 3d 03 a6 mtspr 29,r9
   200: 4c 00 01 2c isync
   204: 48 00 00 01 bl 204 <._copy_to_user+0x54>
     204: R_PPC64_REL24 .__copy_tofrom_user
  ...
  0000000000000260 <._copy_from_user>:
  ...
   2ec: 4c 00 01 2c isync
   2f0: 39 20 ff ff li r9,-1
   2f4: 79 29 00 04 rldicr r9,r9,0,0
   2f8: 7d 3d 03 a6 mtspr 29,r9
   2fc: 4c 00 01 2c isync
   300: 7f c5 f3 78 mr r5,r30
   304: 7f 83 e3 78 mr r3,r28
   308: 48 00 00 01 bl 308 <._copy_from_user+0xa8>
     308: R_PPC64_REL24 .__copy_tofrom_user
  ...

Signed-off-by: Christophe Leroy <email address hidden>
[mpe: Spell out the directions, s/KUAP_R/KUAP_READ/ etc.]
Signed-off-by: Michael Ellerman <email address hidden>
Link: https://lore.kernel.org/r/f4e88ec4941d5facb35ce75026b0112f980086c3<email address hidden>
Signed-off-by: Sasha Levin <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>

d66ffa7... by Stephen Rothwell <email address hidden>

regulator fix for "regulator: core: Add regulator_is_equal() helper"

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

[ Upstream commit 0468e667a5bead9c1b7ded92861b5a98d8d78745 ]

Signed-off-by: Stephen Rothwell <email address hidden>
Link: https://<email address hidden>
Acked-by: Marek Vasut <email address hidden>
Signed-off-by: Mark Brown <email address hidden>
Signed-off-by: Sasha Levin <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>

75fa3a3... by Paolo Bonzini <email address hidden>

KVM: x86: use CPUID to locate host page table reserved bits

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

[ Upstream commit 7adacf5eb2d2048045d9fd8fdab861fd9e7e2e96 ]

The comment in kvm_get_shadow_phys_bits refers to MKTME, but the same is actually
true of SME and SEV. Just use CPUID[0x8000_0008].EAX[7:0] unconditionally if
available, it is simplest and works even if memory is not encrypted.

Cc: <email address hidden>
Reported-by: Tom Lendacky <email address hidden>
Signed-off-by: Paolo Bonzini <email address hidden>
Signed-off-by: Sasha Levin <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>

96de6fe... by tglx

x86/timer: Don't skip PIT setup when APIC is disabled or in legacy mode

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

commit 979923871f69a4dc926658f9f9a1a4c1bde57552 upstream.

Tony reported a boot regression caused by the recent workaround for systems
which have a disabled (clock gate off) PIT.

On his machine the kernel fails to initialize the PIT because
apic_needs_pit() does not take into account whether the local APIC
interrupt delivery mode will actually allow to setup and use the local
APIC timer. This should be easy to reproduce with acpi=off on the
command line which also disables HPET.

Due to the way the PIT/HPET and APIC setup ordering works (APIC setup can
require working PIT/HPET) the information is not available at the point
where apic_needs_pit() makes this decision.

To address this, split out the interrupt mode selection from
apic_intr_mode_init(), invoke the selection before making the decision
whether PIT is required or not, and add the missing checks into
apic_needs_pit().

Fixes: c8c4076723da ("x86/timer: Skip PIT initialization on modern chipsets")
Reported-by: Anthony Buckley <email address hidden>
Tested-by: Anthony Buckley <email address hidden>
Signed-off-by: Thomas Gleixner <email address hidden>
Signed-off-by: Ingo Molnar <email address hidden>
Cc: Daniel Drake <email address hidden>
Link: https://bugzilla.kernel.org/show_bug.cgi?id=206125
Link: https://<email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>

2868b70... by Matti Vaittinen <email address hidden>

mfd: bd70528: Fix hour register mask

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

commit 6c883472e1c11cb05561b6dd0c28bb037c2bf2de upstream.

When RTC is used in 24H mode (and it is by this driver) the maximum
hour value is 24 in BCD. This occupies bits [5:0] - which means
correct mask for HOUR register is 0x3f not 0x1f. Fix the mask

Fixes: 32a4a4ebf768 ("rtc: bd70528: Initial support for ROHM bd70528 RTC")

Signed-off-by: Matti Vaittinen <email address hidden>
Acked-by: Alexandre Belloni <email address hidden>
Signed-off-by: Lee Jones <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>