- 06 Apr, 2016 40 commits
-
-
Borislav Petkov authored
BugLink: http://bugs.launchpad.net/bugs/1559914Signed-off-by:
Borislav Petkov <bp@suse.de> Cc: Arnaldo Carvalho de Melo <acme@redhat.com> Cc: Jiri Olsa <jolsa@redhat.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Stephane Eranian <eranian@google.com> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Vince Weaver <vincent.weaver@maine.edu> Link: http://lkml.kernel.org/r/1455098123-11740-3-git-send-email-bp@alien8.deSigned-off-by:
Ingo Molnar <mingo@kernel.org> (cherry picked from commit e1069839) Signed-off-by:
Tim Gardner <tim.gardner@canonical.com>
-
Borislav Petkov authored
BugLink: http://bugs.launchpad.net/bugs/1559914 Start moving the Intel bits. Signed-off-by:
-
Borislav Petkov authored
BugLink: http://bugs.launchpad.net/bugs/1559914Signed-off-by:
-
Borislav Petkov authored
BugLink: http://bugs.launchpad.net/bugs/1559914Signed-off-by:
-
Borislav Petkov authored
BugLink: http://bugs.launchpad.net/bugs/1559914Signed-off-by:
-
Borislav Petkov authored
BugLink: http://bugs.launchpad.net/bugs/1559914 We distribute those in vendor subdirs, starting with .../events/amd/. Signed-off-by:
-
Borislav Petkov authored
BugLink: http://bugs.launchpad.net/bugs/1559914 Also, keep the churn at minimum by adjusting the include "perf_event.h" when each file gets moved. Signed-off-by:
-
Mika Westerberg authored
BugLink: http://bugs.launchpad.net/bugs/1520139 I2C host controller need to be configured properly in order to meet I2C timings specified in the I2C protocol specification. Some Intel Broxton based machines do not have this information in the ACPI namespace (or the boot firmware does not support ACPI at all) so we use build-in device properties instead. Signed-off-by:
Mika Westerberg <mika.westerberg@linux.intel.com> Signed-off-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by:
Lee Jones <lee.jones@linaro.org> (cherry picked from commit 0343b2f4) Signed-off-by:
-
Tim Gardner authored
Ignore: yes Signed-off-by: -
Tim Gardner authored
Signed-off-by: -
Zhang Rui authored
BugLink: http://bugs.launchpad.net/bugs/1561676 In some cases, platform thermal driver may report invalid trip points, thermal core should not take any action for these trip points. This fixed a regression that bogus trip point starts to screw up thermal control on some Lenovo laptops, after commit bb431ba2 Author: Zhang Rui <rui.zhang@intel.com> Date: Fri Oct 30 16:31:47 2015 +0800 Thermal: initialize thermal zone device correctly After thermal zone device registered, as we have not read any temperature before, thus tz->temperature should not be 0, which actually means 0C, and thermal trend is not available. In this case, we need specially handling for the first thermal_zone_device_update(). Both thermal core framework and step_wise governor is enhanced to handle this. And since the step_wise governor is the only one that uses trends, so it's the only thermal governor that needs to be updated. Tested-by:
Manuel Krause <manuelkrause@netscape.net> Tested-by:
szegad <szegadlo@poczta.onet.pl> Tested-by:
prash <prash.n.rao@gmail.com> Tested-by:
amish <ammdispose-arch@yahoo.com> Tested-by:
Matthias <morpheusxyz123@yahoo.de> Reviewed-by:
Javi Merino <javi.merino@arm.com> Signed-off-by:
Zhang Rui <rui.zhang@intel.com> Signed-off-by:
Chen Yu <yu.c.chen@intel.com> CC: <stable@vger.kernel.org> #3.18+ Link: https://bugzilla.redhat.com/show_bug.cgi?id=1317190 Link: https://bugzilla.kernel.org/show_bug.cgi?id=114551Signed-off-by:
-
Benjamin Tissoires authored
BugLink: http://bugs.launchpad.net/bugs/1553811 Looks like the fimware 8.2 stall has the extra buttons spurious release bug. Signed-off-by:
Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by:
Joseph Salisbury <joseph.salisbury@canonical.com> Signed-off-by:
-
Tyler Hicks authored
BugLink: https://launchpad.net/bugs/1560583 Check the value of the unprivileged_userns_apparmor_policy sysctl when a namespace root process attempts to read the apparmorfs profiles file. Signed-off-by:
Tyler Hicks <tyhicks@canonical.com> Signed-off-by:
-
Tyler Hicks authored
BugLink: https://launchpad.net/bugs/1560583 Change the apparmorfs profiles file permissions check to better match the old requirements before the apparmorfs permissions were changed to allow profile loads inside of confined, first-level user namespaces. Historically, the profiles file has been readable by the root user and group. A recent change added the requirement that the process have the CAP_MAC_ADMIN capability. This is a problem for confined processes since keeping the 'capability mac_admin,' rule out of the AppArmor profile is often desired. This patch replaces the CAP_MAC_ADMIN requirement with a requirement that the process is root in its user namespace. Signed-off-by:
-
Andy Whitcroft authored
BugLink: http://bugs.launchpad.net/bugs/1561492Signed-off-by:
Andy Whitcroft <apw@canonical.com>
-
Tim Gardner authored
BugLink: http://bugs.launchpad.net/bugs/1557690Signed-off-by:
-
Andy Whitcroft authored
BugLink: http://bugs.launchpad.net/bugs/1519814Signed-off-by:
-
Dimitri John Ledkov authored
Signed-off-by:
Dimitri John Ledkov <xnox@ubuntu.com> BugLink: http://bugs.launchpad.net/bugs/1519814Signed-off-by:
-
Dimitri John Ledkov authored
BugLink: http://bugs.launchpad.net/bugs/1561483Signed-off-by:
Colin Ian King <colin.king@canonical.com>
-
Andy Whitcroft authored
BugLink: http://bugs.launchpad.net/bugs/1558871Signed-off-by:
-
Andy Whitcroft authored
BugLink: http://bugs.launchpad.net/bugs/1558871Signed-off-by:
-
Seth Forshee authored
BugLink: http://bugs.launchpad.net/bugs/1505948 The 'reqs' member of fuse_io_priv serves two purposes. First is to track the number of oustanding async requests to the server and to signal that the io request is completed. The second is to be a reference count on the structure to know when it can be freed. For sync io requests these purposes can be at odds. fuse_direct_IO() wants to block until the request is done, and since the signal is sent when 'reqs' reaches 0 it cannot keep a reference to the object. Yet it needs to use the object after the userspace server has completed processing requests. This leads to some handshaking and special casing that it needlessly complicated and responsible for at least one race condition. It's much cleaner and safer to maintain a separate reference count for the object lifecycle and to let 'reqs' just be a count of outstanding requests to the userspace server. Then we can know for sure when it is safe to free the object without any handshaking or special cases. The catch here is that most of the time these objects are stack allocated and should not be freed. Initializing these objects with a single reference that is never released prevents accidental attempts to free the objects. Fixes: 9d5722b7 ("fuse: handle synchronous iocbs internally") Cc: stable@vger.kernel.org # v4.1+ Signed-off-by:
Seth Forshee <seth.forshee@canonical.com> Signed-off-by:
Miklos Szeredi <mszeredi@redhat.com> (backported from commit 744742d6 git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git) Signed-off-by:
-
Robert Doebbelin authored
BugLink: http://bugs.launchpad.net/bugs/1505948 There's a race in fuse_direct_IO(), whereby is_sync_kiocb() is called on an iocb that could have been freed if async io has already completed. The fix in this case is simple and obvious: cache the result before starting io. It was discovered by KASan: kernel: ================================================================== kernel: BUG: KASan: use after free in fuse_direct_IO+0xb1a/0xcc0 at addr ffff88036c414390 Signed-off-by:
Robert Doebbelin <robert@quobyte.com> Signed-off-by:
-
Serge Hallyn authored
BugLink: http://bugs.launchpad.net/bugs/1560489 [ note - this is a version of the patch I just sent to lkml ported to our xenial tree. It's needed for things like docker and lxc to be certain of which cgroup tasks file is their own in certain nesting situations. We currently work around it by blindly assuming that there are no legacy container managers running on cgroup-ns-enabled kernels ] One practical problem I've found with cgroup namespaces is that there is no way to disambiguate between a cgroupfs mount which was done in a cgroup namespace, and a bind mount of a cgroupfs directory. So whether I do unshare --cgroup -- bash -c "mount -t cgroup -o freezer f /mnt; cat /proc/self/mountinfo" or whether I just mount --bind /sys/fs/cgroup/freezer/$(awk -F: '/freezer/ { print $3 }' /proc/self/cgroup) /mnt 'mount root' field (field 3) in /proc/self/mountinfo will show the same thing, the result of awk -F: '/freezer/ { print $3 }' /proc/self/cgroup. This patch adds a 'nsroot=' field to cgroup mountinfo entries, so that userspace can distinguish a mount made in a cgroup namespace from a bind mount from a cgroup subdirectory. Signed-off-by:
Serge Hallyn <serge.hallyn@ubuntu.com> Signed-off-by:
-
Tim Gardner authored
BugLink: http://bugs.launchpad.net/bugs/1560445 Remove these files on clean so they do not get included in the source package. Signed-off-by:
-
Tim Gardner authored
The reconstruct script is long enough that it overwhelms any other output from a clean operation (and is largely noise anyway). Signed-off-by: -
dann frazier authored
BugLink: http://bugs.launchpad.net/bugs/1549494 This reverts commit c1fab9a6d70a0043bbda8162e89bafab0500324c. Signed-off-by:
-
dann frazier authored
BugLink: http://bugs.launchpad.net/bugs/1549494 This reverts commit 86b9c76b0c7c5bbdb6196effb2c7ae4f08e11b80. Signed-off-by:
-
dann frazier authored
BugLink: http://bugs.launchpad.net/bugs/1549494 This reverts commit 45b5c64b98b3ab90332bf7f256a6a1bae60c1527. Signed-off-by:
-
Radha Mohan Chintakuntla authored
BugLink: http://bugs.launchpad.net/bugs/1558828 In case of ARCH_THUNDER, there is a need to allocate the GICv3 ITS table which is bigger than the allowed max order. So we are forcing it only in case of 4KB page size. Signed-off-by:
Radha Mohan Chintakuntla <rchintakuntla@cavium.com> Signed-off-by:
Robert Richter <rrichter@cavium.com> [ dannf: Depend on ARM64_4K_PAGES instead of !ARM64_64K_PAGES now that 16K pages are available ] Signed-off-by:
dann frazier <dann.frazier@canonical.com> Signed-off-by:
-
dann frazier authored
BugLink: http://bugs.launchpad.net/bugs/1558828 Needed to allocate the GICv3 ITS table on thunder platforms. Signed-off-by:
-
Ching Huang authored
BugLink: http://bugs.launchpad.net/bugs/1559609 Change driver version to v1.30.00.22-20151126 Signed-off-by:
Ching Huang <ching2048@areca.com.tw> Reviewed-by:
Tomas Henzl <thenzl@redhat.com> Signed-off-by:
Martin K. Petersen <martin.petersen@oracle.com> (cherry picked from commit 15d26397) Signed-off-by:
-
Ching Huang authored
BugLink: http://bugs.launchpad.net/bugs/1559609 Split dma resource allocation and io register assignment from get_config to a new function arcmsr_alloc_io_queue. Signed-off-by:
-
Ching Huang authored
BugLink: http://bugs.launchpad.net/bugs/1559609Signed-off-by:
-
Ching Huang authored
BugLink: http://bugs.launchpad.net/bugs/1559609 Changes driver version number. Signed-off-by:
Johannes Thumshirn <jthumshirn@suse.de> Reviewed-by:
Hannes Reinicke <hare@suse.de> Signed-off-by:
-
Ching Huang authored
BugLink: http://bugs.launchpad.net/bugs/1559609 Support Areca's new PCIe to SATA RAID adapter ARC1203. Signed-off-by:
-
Ching Huang authored
BugLink: http://bugs.launchpad.net/bugs/1559609 [mkp: Fixed checkpatch whitespace warning] Signed-off-by:
-
Ching Huang authored
BugLink: http://bugs.launchpad.net/bugs/1559609 Releasing allocated resource if get configuration data failed. Signed-off-by:
-
Ching Huang authored
BugLink: http://bugs.launchpad.net/bugs/1559609 Fixed getting wrong configuration data of adapter type B and type D. Signed-off-by:
-
Stefan Bader authored
BugLink: http://bugs.launchpad.net/bugs/1559692 There have been bugs reported already in the past (but without enough data to pinpoint the problem). This time it was found that a certain Thinkpad external keyboard would not be working from the server install image (but works from a desktop installer). The reason was a missing specific hid driver (hid-lenovo). Since we might miss more than that, I went forward and updated the whole list. I excluded a few drivers which where either force feedback drivers (.*ff.ko, I think we can live without the backlash), joystick drivers and I also not added wacom (because graphic tablets unlikely are useful to complete a server install). Signed-off-by:
Stefan Bader <stefan.bader@canonical.com> Signed-off-by:
-
