~dannf/ubuntu/+source/linux/+git/xenial:lp1590168

Last commit made on 2016-06-07
Get this branch:
git clone -b lp1590168 https://git.launchpad.net/~dannf/ubuntu/+source/linux/+git/xenial
Only dann frazier can upload to this branch. If you are dann frazier please log in for upload directions.

Branch merges

Branch information

Name:
lp1590168
Repository:
lp:~dannf/ubuntu/+source/linux/+git/xenial

Recent commits

132c088... by Tirumalesh Chalamarla

iommu/arm-smmu: Workaround for ThunderX erratum #27704

BugLink: http://bugs.launchpad.net/bugs/1590168

Due to erratum #27704, the CN88xx SMMUv2 implementation supports only
shared ASID and VMID numberspaces.

This patch ensures that ASID and VMIDs are unique across all SMMU
instances on affected Cavium systems.

Signed-off-by: Tirumalesh Chalamarla <email address hidden>
Signed-off-by: Akula Geethasowjanya <email address hidden>
[will: commit message, comments and formatting]
Signed-off-by: Will Deacon <email address hidden>
(backported from commit 1bd37a6835bef0ecd2138cb42f9088fd890f9939)
Signed-off-by: dann frazier <email address hidden>
[dannf: adjusted for offset changes only]

e9c5369... by Tirumalesh Chalamarla

iommu/arm-smmu: Add support for 16 bit VMID

BugLink: http://bugs.launchpad.net/bugs/1590168

This patch adds support for 16-bit VMIDs on implementations of SMMUv2
that support it.

Signed-off-by: Tirumalesh Chalamarla <email address hidden>
[will: commit messsage and comments]
Signed-off-by: Will Deacon <email address hidden>
(cherry picked from commit 4e3e9b6997b24383264031198bf8905b3746221e)
Signed-off-by: dann frazier <email address hidden>

eaf0fb3... by Ganapat

irqchip/gicv3-its: numa: Enable workaround for Cavium thunderx erratum 23144

BugLink: http://bugs.launchpad.net/bugs/1589704

The erratum fixes the hang of ITS SYNC command by avoiding inter node
io and collections/cpu mapping on thunderx dual-socket platform.

This fix is only applicable for Cavium's ThunderX dual-socket platform.

Reviewed-by: Robert Richter <email address hidden>
Signed-off-by: Ganapatrao Kulkarni <email address hidden>
Signed-off-by: Robert Richter <email address hidden>
Signed-off-by: Marc Zyngier <email address hidden>
(back-ported from commit fbf8f40e1658cb2f17452dbd3c708e329c5d27e0)
Signed-off-by: dann frazier <email address hidden>
[ dannf: Adjusted for offset changes; dropped Documentation/ updates for
  file that didn't exist in v4.4 ]
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>

0a5b716... by dann frazier

UBUNTU: [Config] CONFIG_CAVIUM_ERRATUM_23144=y

Signed-off-by: dann frazier <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>

0b962a9... by Greg Kroah-Hartman <email address hidden>

Linux 4.4.12

BugLink: http://bugs.launchpad.net/bugs/1588945

Signed-off-by: Tim Gardner <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>

884a8e6... by Arnd Bergmann

kbuild: move -Wunused-const-variable to W=1 warning level

BugLink: http://bugs.launchpad.net/bugs/1588945

commit c9c6837d39311b0cc14cdbe7c18e815ab44aefb1 upstream.

gcc-6 started warning by default about variables that are not
used anywhere and that are marked 'const', generating many
false positives in an allmodconfig build, e.g.:

arch/arm/mach-davinci/board-da830-evm.c:282:20: warning: 'da830_evm_emif25_pins' defined but not used [-Wunused-const-variable=]
arch/arm/plat-omap/dmtimer.c:958:34: warning: 'omap_timer_match' defined but not used [-Wunused-const-variable=]
drivers/bluetooth/hci_bcm.c:625:39: warning: 'acpi_bcm_default_gpios' defined but not used [-Wunused-const-variable=]
drivers/char/hw_random/omap-rng.c:92:18: warning: 'reg_map_omap4' defined but not used [-Wunused-const-variable=]
drivers/devfreq/exynos/exynos5_bus.c:381:32: warning: 'exynos5_busfreq_int_pm' defined but not used [-Wunused-const-variable=]
drivers/dma/mv_xor.c:1139:34: warning: 'mv_xor_dt_ids' defined but not used [-Wunused-const-variable=]

This is similar to the existing -Wunused-but-set-variable warning
that was added in an earlier release and that we disable by default
now and only enable when W=1 is set, so it makes sense to do
the same here. Once we have eliminated the majority of the
warnings for both, we can put them back into the default list.

We probably want this in backport kernels as well, to allow building
them with gcc-6 without introducing extra warnings.

Signed-off-by: Arnd Bergmann <email address hidden>
Acked-by: Olof Johansson <email address hidden>
Acked-by: Lee Jones <email address hidden>
Signed-off-by: Michal Marek <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

Signed-off-by: Tim Gardner <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>

32583a3... by Johannes Thumshirn <email address hidden>

Revert "scsi: fix soft lockup in scsi_remove_target() on module removal"

BugLink: http://bugs.launchpad.net/bugs/1588945

commit 305c2e71b3d733ec065cb716c76af7d554bd5571 upstream.

Now that we've done a more comprehensive fix with the intermediate
target state we can remove the previous hack introduced with commit
90a88d6ef88e ("scsi: fix soft lockup in scsi_remove_target() on module
removal").

Signed-off-by: Johannes Thumshirn <email address hidden>
Reviewed-by: Ewan D. Milne <email address hidden>
Reviewed-by: Hannes Reinecke <email address hidden>
Signed-off-by: Martin K. Petersen <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

Signed-off-by: Tim Gardner <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>

ac51e8c... by Johannes Thumshirn <email address hidden>

scsi: Add intermediate STARGET_REMOVE state to scsi_target_state

BugLink: http://bugs.launchpad.net/bugs/1588945

commit f05795d3d771f30a7bdc3a138bf714b06d42aa95 upstream.

Add intermediate STARGET_REMOVE state to scsi_target_state to avoid
running into the BUG_ON() in scsi_target_reap(). The STARGET_REMOVE
state is only valid in the path from scsi_remove_target() to
scsi_target_destroy() indicating this target is going to be removed.

This re-fixes the problem introduced in commits bc3f02a795d3 ("[SCSI]
scsi_remove_target: fix softlockup regression on hot remove") and
40998193560d ("scsi: restart list search after unlock in
scsi_remove_target") in a more comprehensive way.

[mkp: Included James' fix for scsi_target_destroy()]

Signed-off-by: Johannes Thumshirn <email address hidden>
Fixes: 40998193560dab6c3ce8d25f4fa58a23e252ef38
Reported-by: Sergey Senozhatsky <email address hidden>
Tested-by: Sergey Senozhatsky <email address hidden>
Reviewed-by: Ewan D. Milne <email address hidden>
Reviewed-by: Hannes Reinecke <email address hidden>
Reviewed-by: James Bottomley <email address hidden>
Signed-off-by: Martin K. Petersen <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

Signed-off-by: Tim Gardner <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>

c207d12... by Mikulas Patocka <email address hidden>

hpfs: implement the show_options method

BugLink: http://bugs.launchpad.net/bugs/1588945

commit 037369b872940cd923835a0a589763180c4a36bc upstream.

The HPFS filesystem used generic_show_options to produce string that is
displayed in /proc/mounts. However, there is a problem that the options
may disappear after remount. If we mount the filesystem with option1
and then remount it with option2, /proc/mounts should show both option1
and option2, however it only shows option2 because the whole option
string is replaced with replace_mount_options in hpfs_remount_fs.

To fix this bug, implement the hpfs_show_options function that prints
options that are currently selected.

Signed-off-by: Mikulas Patocka <email address hidden>
Signed-off-by: Linus Torvalds <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

Signed-off-by: Tim Gardner <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>

4ec6356... by Mikulas Patocka <email address hidden>

hpfs: fix remount failure when there are no options changed

BugLink: http://bugs.launchpad.net/bugs/1588945

commit 44d51706b4685f965cd32acde3fe0fcc1e6198e8 upstream.

Commit ce657611baf9 ("hpfs: kstrdup() out of memory handling") checks if
the kstrdup function returns NULL due to out-of-memory condition.

However, if we are remounting a filesystem with no change to
filesystem-specific options, the parameter data is NULL. In this case,
kstrdup returns NULL (because it was passed NULL parameter), although no
out of memory condition exists. The mount syscall then fails with
ENOMEM.

This patch fixes the bug. We fail with ENOMEM only if data is non-NULL.

The patch also changes the call to replace_mount_options - if we didn't
pass any filesystem-specific options, we don't call
replace_mount_options (thus we don't erase existing reported options).

Fixes: ce657611baf9 ("hpfs: kstrdup() out of memory handling")
Signed-off-by: Mikulas Patocka <email address hidden>
Signed-off-by: Linus Torvalds <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

Signed-off-by: Tim Gardner <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>