On Tue, Aug 14, 2018 at 12:50:02AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:1c2f2531cf8b Add linux-next specific files for 20180809
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=16016cf840
> kernel co
This adds an x86-specific test for pinned cr4 bits. A successful test
will validate pinning and check the ROP-style call-middle-of-function
defense, if needed. For example, in the case of native_write_cr4()
looking like this:
8171bce0 :
8171bce0: 48 8b 35 79 46 f2 00mov
Hi,
On Tue, Feb 26, 2019 at 05:14:00PM +, Marc Zyngier wrote:
> On 26/02/2019 16:21, Ard Biesheuvel wrote:
> > On Mon, 25 Feb 2019 at 15:53, Marc Zyngier wrote:
> >> It outlines one thing: If you have to interpret per-device PCI
> >> properties from DT, you're in for serious trouble. I should
On Sat, Feb 23, 2019 at 2:49 AM Ioana Ciornei wrote:
>
> The first two patches enable cache stashing and configure the core cluster
> destination per software portal while the third patch is the one
> configuring the amount of stashing on a queue.
Series applied for next. Thanks.
Regards,
Leo
>
Dear Friend,
I am Mrs Alice Johnson.am sending you this brief letter to solicit your
partnership to transfer $23.5 million US Dollars.I shall send you more
information and procedures when I receive positive response from you.
please send me a message in my Email box (mrsalicejohns...@gmail.com)
as
The ASPEED AST2400, and AST2500 in some configurations include a
PCI-to-AHB MMIO bridge. This bridge allows a server to read and write
in the BMC's physical address space. This feature is especially useful
when using this bridge to send large files to the BMC.
The host may use this to send down
On Tue, Feb 26, 2019 at 3:37 PM Kees Cook wrote:
> + for (i = 0; i < 64; i++) {
> ...
> + }
> + if (i >= 256) {
> + pr_info("ok: cannot locate cr4 writing call gadget\n");
> + return;
> + }
*brown paper bag*
Argh. I changed the depth of that sea
On Wed, Feb 27, 2019 at 12:16 AM Ulf Hansson wrote:
>
> On Tue, 26 Feb 2019 at 23:08, Rafael J. Wysocki wrote:
> >
> > On Tue, Feb 26, 2019 at 3:54 PM Ulf Hansson wrote:
> > >
> > > A common piece of data used by cpuidle governors, is the information about
> > > when the next timer/tick is going
This adds CR0 pinning (for WP), and cleans up the CR4 pin to avoid
taking an exception from WARN before fixing up the desired pin.
Additionally adds lkdtm test (which depends on the CR4 patch, otherwise
I'd send it via Greg's tree).
Thanks!
-Kees
Kees Cook (3):
x86/asm: Pin sensitive CR0 bits
With sensitive CR4 bits pinned now, it's possible that the WP bit for CR0
might become a target as well. Following the same reasoning for the CR4
pinning, this pins CR0's WP bit (but this can be done with a static value).
As before, to convince the compiler to not optimize away the check for the
W
This adds an x86-specific test for pinned cr4 bits. A successful test
will validate pinning and check the ROP-style call-middle-of-function
defense, if needed. For example, in the case of native_write_cr4()
looking like this:
8171bce0 :
8171bce0: 48 8b 35 79 46 f2 00mov
On Tue, Feb 26, 2019 at 3:36 PM Patrick Venture wrote:
>
> The ASPEED AST2400, and AST2500 in some configurations include a
> PCI-to-AHB MMIO bridge. This bridge allows a server to read and write
> in the BMC's physical address space. This feature is especially useful
> when using this bridge to
Instead of taking a full WARN() exception before restoring a potentially
missed CR4 bit, this retains the missing bit for later reporting. This
matches the logic done for the CR0 pinning.
Signed-off-by: Kees Cook
---
arch/x86/include/asm/special_insns.h | 10 +++---
1 file changed, 7 inserti
The ASPEED AST2400, and AST2500 in some configurations include a
PCI-to-AHB MMIO bridge. This bridge allows a server to read and write
in the BMC's physical address space. This feature is especially useful
when using this bridge to send large files to the BMC.
The host may use this to send down
On 2019-02-26 8:23 pm, Nicolin Chen wrote:
This reverts commit d222e42e88168fd67e6d131984b86477af1fc256.
The original change breaks omap dss:
omapdss_dispc 58001000.dispc:
dispc_errata_i734_wa_init: dma_alloc_writecombine failed
Let's revert it first and then find a safer solution
Document the ast2400, ast2500 PCI-to-AHB bridge control driver bindings.
Signed-off-by: Patrick Venture
Change-Id: Ic89a2df0f555dee10598f87537ee004e82d13acd
---
Changes for v2:
- Added comment about syscon required parameter.
---
.../bindings/misc/aspeed-p2a-ctrl.txt | 32 +++
On 2/26/2019 12:49 PM, Denis Efremov wrote:
Recent "New LSM Hooks" discussion has led me to the
thought that it might be a good idea to slightly
update the current documentation. The patchset adds
nothing new to the documentation, only fixes the old
description of hooks to reflect their current s
On Tue, Feb 26, 2019 at 03:31:31PM -0800, Brian Norris wrote:
> Hi Marc,
>
> On Sun, Feb 24, 2019 at 02:04:25PM +, Marc Zyngier wrote:
> > The mwifiex driver makes unsafe assumptions about the state of the
> > wake-up interrupt. It requests it and only then disable it. Of
> > course, the inter
Hi Marc,
On Sun, Feb 24, 2019 at 02:04:25PM +, Marc Zyngier wrote:
> The mwifiex driver makes unsafe assumptions about the state of the
> wake-up interrupt. It requests it and only then disable it. Of
> course, the interrupt may be screaming for whatever reason at that
> time, and the handler
On Fri, 1 Feb 2019 08:48:09 +0100 Michal Hocko wrote:
> On Fri 01-02-19 08:12:03, Michal Hocko wrote:
> > On Thu 31-01-19 23:57:11, Chris Down wrote:
> > > memcg is NULL if we have CONFIG_MEMCG set, but cgroup_disable=memory on
> > > the kernel command line.
> > >
> > > Fixes: 8a907cdf0177ab40 (
+ others
Hi Marc,
Thanks for the series. I have a few bits of history to add to this, and
some comments.
On Sun, Feb 24, 2019 at 02:04:22PM +, Marc Zyngier wrote:
> For quite some time, I wondered why the PCI mwifiex device built in my
> Chromebook was unable to use the good old legacy inter
While the appended kernel module signature can be verified, when loading
a kernel module via either the init_module or the finit_module syscall,
verifying the IMA signature requires access to the file descriptor,
which is only available via the finit_module syscall. As "modprobe"
does not provide
Remove the few bashisms and use the complete option name for clarity.
Signed-off-by: Mimi Zohar
Reviewed-by: Petr Vorel
---
tools/testing/selftests/ima/test_kexec_load.sh | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/tools/testing/selftests/ima/test_kexe
Define, update and move get_secureboot_mode() to a common file for use
by other tests.
Signed-off-by: Mimi Zohar
Reviewed-by: Petr Vorel
---
tools/testing/selftests/ima/Makefile | 1 +
tools/testing/selftests/ima/common_lib.sh | 24
tools/testing/selftes
The kernel can be configured to require kexec kernel images and kernel
modules are signed. An IMA policy can be specified on the boot command
line or a custom IMA policy loaded requiring the kexec kernel image and
kernel modules be signed. In addition, systems booted in secure boot
mode with the
Define log_info, log_pass, log_fail, and log_skip functions.
Suggested-by: Petr Vorel
Signed-off-by: Mimi Zohar
---
tools/testing/selftests/ima/common_lib.sh | 43 +++---
tools/testing/selftests/ima/test_kexec_load.sh | 19 +++-
2 files changed, 43 insertions(+)
The kernel can be configured to verify PE signed kernel images, IMA
kernel image signatures, both types of signatures, or none. This test
verifies only properly signed kernel images are loaded into memory,
based on the kernel configuration and runtime policies.
Signed-off-by: Mimi Zohar
---
too
On Tue, Feb 26, 2019 at 06:18:25PM +0100, Andrey Konovalov wrote:
> On Fri, Feb 22, 2019 at 11:55 PM Dave Hansen wrote:
> >
> > On 2/22/19 4:53 AM, Andrey Konovalov wrote:
> > > The following testing approaches has been taken to find potential issues
> > > with user pointer untagging:
> > >
> > >
On Tue, 26 Feb 2019 at 23:08, Rafael J. Wysocki wrote:
>
> On Tue, Feb 26, 2019 at 3:54 PM Ulf Hansson wrote:
> >
> > A common piece of data used by cpuidle governors, is the information about
> > when the next timer/tick is going to fire. Rather than having each governor
> > calling tick_nohz_ge
On Tue, Feb 26, 2019 at 02:49:05PM +0800, Huang, Ying wrote:
> Do you have time to take a look at this patch?
Hi Ying, is this handling all places where swapoff might cause a task to read
invalid data? For example, why don't other reads of swap_map (for example
swp_swapcount, page_swapcount, swap
This patch tries to enable PMU sharing. To make perf event scheduling
fast, we use special data structures.
An array of "struct perf_event_dup" is added to the perf_event_context,
to remember all the duplicated events under this ctx. All the events
under this ctx has a "dup_id" pointing to its per
Changes v4 -> v5:
1. Rebase upon latest tip/perf/core.
2. Remove prototype from v4 (2/2).
Changes v3 -> v4:
1. In __perf_install_in_context() always reprogram ctx for cpu and cgroup
events to make sure event duplications set up properly.
2. Add a prototype (2/2) to show potential solu
Jiri Olsa writes:
>
> im still getting compile error the new branch:
>
> CC ui/browsers/hists.o
> ui/browsers/hists.c: In function ‘perf_evsel__hists_browse’:
> ui/browsers/hists.c:2567:8: error: ‘%s’ directive output may be truncated
> writing up to 63 bytes into a region of size between
From: Haiyang Zhang
Date: Fri, 22 Feb 2019 18:25:03 +
> From: Haiyang Zhang
>
> Incoming packets may have IP header checksum verified by the host.
> They may not have IP header checksum computed after coalescing.
> This patch re-compute the checksum when necessary, otherwise the
> packets m
On Sun, 24 Feb 2019 12:33:51 -0800, Robert Eshleman wrote:
> Adds device tree bindings for the ap3216c ambient light and proximity
> sensor.
>
> Signed-off-by: Robert Eshleman
> ---
> .../devicetree/bindings/iio/light/ap3216c.txt | 22 +++
> 1 file changed, 22 insertions(+)
> cr
On Sun, 24 Feb 2019 12:33:29 -0800, Robert Eshleman wrote:
> This patch adds a vendor-prefix for the Lite-On Semiconductor
> Corporation.
>
> Signed-off-by: Robert Eshleman
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob
On Mon, Feb 25, 2019 at 02:19:10AM +, Anson Huang wrote:
> i.MX8QXP is an ARMv8 SoC which has a Cortex-M4 system controller
> inside, the system controller is in charge of controlling power,
> clock and watchdog etc..
>
> This patch adds i.MX system controller watchdog driver support,
> watchd
On 2/25/19 9:55 AM, Keith Busch wrote:
> On Sun, Feb 24, 2019 at 03:27:09PM -0800, alex_gagn...@dellteam.com wrote:
>> [ 57.680494] {1}[Hardware Error]: Hardware error from APEI Generic
>> Hardware Error Source: 1
>> [ 57.680495] {1}[Hardware Error]: event severity: fatal
>> [ 57.680496] {1
>
> The number of node specific huge pages can be set via a file such as:
> /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages
> When a node specific value is specified, the global number of huge
> pages must also be adjusted. This adjustment is calculated as the
> specified n
We'd like to have a pointer to the device that's consuming a particular
clk in the clk framework so we can link the consumer to the clk provider
with a PM device link. Add a device argument to clk_hw_create_clk() for
this so it can be used in subsequent patches to add and remove the link.
Cc: Miqu
There are a couple warts with clk parent handling in the common clk
framework. This patch series addresses one of those warts, parent-child
linkages. We use strings for all parent-child linkages, and this leads
to poorly written code that extracts clk names from struct clk pointers
and makes clk pr
This is an example patch to show how DT nodes are updated to specify the
clocks which are external to the clock controller can be specified in DT
and then found by the clk core to do parent-child linkage.
Cc: Miquel Raynal
Cc: Jerome Brunet
Cc: Russell King
Cc: Michael Turquette
Cc: Jeffrey Hu
The __clk_get() function is practically a private clk implementation
detail now. No architecture defines it, and given that new code should
be using the common clk framework there isn't a need for it to keep
existing just to serve clkdev purposes. Let's fold it into the
__clk_create_clk() function
The API between clk.c and clkdev.c is purely getting the clk_hw
structure (or the struct clk if it's not CCF) and then turning that
struct clk_hw pointer into a struct clk pointer via clk_hw_create_clk().
There's no need to complicate clkdev.c with these DT parsing details
that are only relevant to
The common clk framework is lacking in ability to describe the clk
topology without specifying strings for every possible parent-child
link. There are a few drawbacks to the current approach:
1) String comparisons are used for everything, including describing
topologies that are 'local' to a sin
TODO: Fully convert driver
Cc: Miquel Raynal
Cc: Jerome Brunet
Cc: Russell King
Cc: Michael Turquette
Cc: Jeffrey Hugo
Cc: Chen-Yu Tsai
Signed-off-by: Stephen Boyd
---
drivers/clk/qcom/gcc-sdm845.c | 180 +-
1 file changed, 90 insertions(+), 90 deletions(-)
From: Miquel Raynal
Currently, the core->dev entry is populated only if runtime PM is
enabled. Doing so prevents accessing the device structure in any
case.
Keep the same logic but instead of using the presence of core->dev as
the only condition, also check the status of
pm_runtime_enabled(). Th
We want to get struct clk_hw pointers from a DT clk specifier (i.e. a
clocks property) so that we can find parent clks without searching for
globally unique clk names. This should save time by avoiding the global
string search for clks that are external to the clock controller
providing the clk and
On Mon, Feb 25, 2019 at 07:04:01PM -0800, Andi Kleen wrote:
> [Changes:
> Removed already merged patches.
> Address review feedback, see individual patches.
> Now compiles with gcc 8.
> Some minor bug fixes and improvements.]
>
> We currently have two ways to look at sample data in perf:
> either
On Fri, 22 Feb 2019 14:53:44 -0800, Brian Norris wrote:
> There are two USB PID/VID variations I've seen for this chip, and I want
> to utilize the 'interrupts' property defined here already.
>
> Signed-off-by: Brian Norris
> Reviewed-by: Matthias Kaehlcke
> ---
> v2:
> * drop leading zeroes fr
On Tue, Feb 26, 2019 at 2:20 PM Andrew Jeffery wrote:
>
>
>
> On Wed, 27 Feb 2019, at 08:26, Patrick Venture wrote:
> > On Tue, Feb 26, 2019 at 1:42 PM Patrick Venture wrote:
> > >
> > > On Sun, Feb 24, 2019 at 5:26 PM Andrew Jeffery wrote:
> > > >
> > >
> > > >
> > > > > +
> > > > > + /* Ac
On Fri, Feb 22, 2019 at 06:24:40PM -0800, Brian Norris wrote:
> Documentation/devicetree/bindings/usb/usb-device.txt describes the
> 'usbVID,...' compatible format, where VID is lower-case hexadecimal,
> with leading zeroes suppressed. Allow it here without complaining about
> lack of documentation
On Tue, Feb 26, 2019 at 03:34:12PM -0600, Rob Herring wrote:
> > >
> > > I think Rob suggested that the SCU parent driver should instantiate the
> > > watchdog without explicit watchdog node. That would be possible, but it
> > > currently uses
> > > devm_of_platform_populate() to do the instantiati
Hi Daniel,
Thanks for the comment.
On Tue, 2019-02-26 at 04:06:13 -0800, Daniel Vetter wrote:
> On Tue, Feb 26, 2019 at 12:53 PM Greg Kroah-Hartman
> wrote:
> >
> > On Sat, Feb 23, 2019 at 12:28:17PM -0800, Hyun Kwon wrote:
> > > Add the dmabuf map / unmap interfaces. This allows the user driver
On Wed, 27 Feb 2019, at 08:26, Patrick Venture wrote:
> On Tue, Feb 26, 2019 at 1:42 PM Patrick Venture wrote:
> >
> > On Sun, Feb 24, 2019 at 5:26 PM Andrew Jeffery wrote:
> > >
> >
> > >
> > > > +
> > > > + /* Access to these needs to be locked, held via probe, mapping
> > > > ioctl,
>
This patch increase the size field in the uapi structure of the Memory
IOCTL from 32-bit to 64-bit. This is to allow the user to allocate and/or
map memory in chunks that are larger then 4GB.
Goya's device memory (DRAM) can be up to 16GB, and for certain
topologies, the user may want an allocation
Hi Greg,
Thanks for the comments.
On Tue, 2019-02-26 at 03:53:11 -0800, Greg Kroah-Hartman wrote:
> On Sat, Feb 23, 2019 at 12:28:17PM -0800, Hyun Kwon wrote:
> > Add the dmabuf map / unmap interfaces. This allows the user driver
> > to be able to import the external dmabuf and use it from user s
On Tue, Feb 26, 2019 at 11:08 PM Rafael J. Wysocki wrote:
>
> On Tue, Feb 26, 2019 at 3:54 PM Ulf Hansson wrote:
> >
> > A common piece of data used by cpuidle governors, is the information about
> > when the next timer/tick is going to fire. Rather than having each governor
> > calling tick_nohz
Quoting Eric Biggers (2019-02-26 22:08:58)
> From: Eric Biggers
>
> If drm_gem_handle_create() fails in vkms_gem_create(), then the
> vkms_gem_object is freed twice: once when the reference is dropped by
> drm_gem_object_put_unlocked(), and again by the extra calls to
> drm_gem_object_release() a
On Tue, Feb 26, 2019 at 11:06 PM Ulf Hansson wrote:
>
> On Tue, 26 Feb 2019 at 22:52, Rafael J. Wysocki wrote:
> >
> > On Tue, Feb 26, 2019 at 10:31 PM Ulf Hansson wrote:
> > >
> > > On Tue, 26 Feb 2019 at 18:50, Rafael J. Wysocki wrote:
> > > >
> > > > On Tue, Feb 26, 2019 at 3:55 PM Ulf Hanss
From: Eric Biggers
If drm_gem_handle_create() fails in vkms_gem_create(), then the
vkms_gem_object is freed twice: once when the reference is dropped by
drm_gem_object_put_unlocked(), and again by the extra calls to
drm_gem_object_release() and kfree().
Fix it by skipping the second release and
On Tue, Feb 26, 2019 at 3:54 PM Ulf Hansson wrote:
>
> A common piece of data used by cpuidle governors, is the information about
> when the next timer/tick is going to fire. Rather than having each governor
> calling tick_nohz_get_next_timer|hrtimer() separately, let's consolidate
> the code by c
On Tue, Feb 26, 2019 at 06:36:38PM +0300, Andrey Ryabinin wrote:
>
>
> On 2/25/19 7:03 AM, Roman Gushchin wrote:
> > On Fri, Feb 22, 2019 at 08:58:25PM +0300, Andrey Ryabinin wrote:
> >> In a presence of more than 1 memory cgroup in the system our reclaim
> >> logic is just suck. When we hit memo
On Tue, 26 Feb 2019 at 22:52, Rafael J. Wysocki wrote:
>
> On Tue, Feb 26, 2019 at 10:31 PM Ulf Hansson wrote:
> >
> > On Tue, 26 Feb 2019 at 18:50, Rafael J. Wysocki wrote:
> > >
> > > On Tue, Feb 26, 2019 at 3:55 PM Ulf Hansson
> > > wrote:
> > > >
> > > > Changes in v11:
> > > > - This ver
On Tue, 26 Feb 2019 10:13:14 +0100 Oscar Salvador wrote:
> When using mremap() syscall in addition to MREMAP_FIXED flag,
> mremap() calls mremap_to() which does the following:
>
> 1) unmaps the destination region where we are going to move the map
> 2) If the new region is going to be smaller, w
On Tue, Feb 26, 2019 at 1:42 PM Patrick Venture wrote:
>
> On Sun, Feb 24, 2019 at 5:26 PM Andrew Jeffery wrote:
> >
> > On Fri, 22 Feb 2019, at 08:55, Patrick Venture wrote:
> > > The ASPEED AST2400, and AST2500 in some configurations include a
> > > PCI-to-AHB MMIO bridge. This bridge allows a
On Tue, Feb 26, 2019 at 05:25:46PM +, Ghannam, Yazen wrote:
> From: Yazen Ghannam
>
> Define and use a macro for looping over the number of Unified Memory
> Controllers.
>
> No functional change.
>
> Signed-off-by: Yazen Ghannam
> ---
> Link:
> https://lkml.kernel.org/r/20190219202536.1546
On Tue, Feb 26, 2019 at 10:31 PM Ulf Hansson wrote:
>
> On Tue, 26 Feb 2019 at 18:50, Rafael J. Wysocki wrote:
> >
> > On Tue, Feb 26, 2019 at 3:55 PM Ulf Hansson wrote:
> > >
> > > Changes in v11:
> > > - This version contains only the infrastructure changes that is needed
> > > for
> > > dep
On Tue, 26 Feb 2019 18:58:03 +0900 Tetsuo Handa
wrote:
> Since commit a2e514453861dd39 ("kernel/hung_task.c: allow to set checking
> interval separately from timeout") added hung_task_check_interval_secs,
> setting a value different from hung_task_timeout_secs
>
> echo 0 > /proc/sys/kernel/hu
From: Eric Biggers
If drm_gem_handle_create() fails in vgem_gem_create(), then the
drm_vgem_gem_object is freed twice: once when the reference is dropped
by drm_gem_object_put_unlocked(), and again by __vgem_gem_destroy().
This was hit by syzkaller using fault injection.
Fix it by skipping the
On Sun, Feb 24, 2019 at 5:26 PM Andrew Jeffery wrote:
>
> On Fri, 22 Feb 2019, at 08:55, Patrick Venture wrote:
> > The ASPEED AST2400, and AST2500 in some configurations include a
> > PCI-to-AHB MMIO bridge. This bridge allows a server to read and write
> > in the BMC's memory space.
>
> Bit of
On Tue, 2017-09-05 at 14:12 +0900, Jiada Wang wrote:
> Previously i.MX SPI controller only works in Master mode.
> This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI
> controller to work also in Slave mode.
Recently DMA has been enabled for imx6/7 with SPI. This results in
memory corruptio
On Mon, Feb 25, 2019 at 11:04:42PM +0900, Masami Hiramatsu wrote:
> Hi,
>
> Here is an RFC series of probe-event to support user-space access
> methods, which we discussed in previous thread.
>
> https://lkml.kernel.org/r/20190220171019.5e81a4946b56982f324f7...@kernel.org
>
> So in this thread,
On Sun, Feb 24, 2019 at 8:26 PM Anson Huang wrote:
>
> Hi, Guenter
>
> Best Regards!
> Anson Huang
>
> > -Original Message-
> > From: Guenter Roeck [mailto:groe...@gmail.com] On Behalf Of Guenter
> > Roeck
> > Sent: 2019年2月24日 11:20
> > To: Anson Huang ; Rob Herring
> > Cc: mark.rutl...@a
On Tue, 2019-02-26 at 10:11 +, Vabhav Sharma wrote:
> From: Yogesh Gaur
>
> Increase size of cmux_to_group array, to accomdate entry of
> -1 termination.
>
> Added -1, terminated, entry for 4080_cmux_grpX.
>
> Signed-off-by: Yogesh Gaur
> Signed-off-by: Vabhav Sharma
> Acked-by: Stephen B
On Tue, 2019-02-26 at 10:11 +, Vabhav Sharma wrote:
> From: Yogesh Gaur
>
> Add clockgen support for lx2160a.
> Added entry for compat 'fsl,lx2160a-clockgen'.
>
> Signed-off-by: Tang Yuantian
> Signed-off-by: Yogesh Gaur
> Signed-off-by: Vabhav Sharma
> Acked-by: Stephen Boyd
> Acked-by:
On Tue, 26 Feb 2019 at 18:50, Rafael J. Wysocki wrote:
>
> On Tue, Feb 26, 2019 at 3:55 PM Ulf Hansson wrote:
> >
> > Changes in v11:
> > - This version contains only the infrastructure changes that is needed for
> > deployment. The PSCI/ARM changes have also been updated and tested, but I
> >
On Tue, Feb 26, 2019 at 09:01:29PM +, Chris Wilson wrote:
> Quoting Eric Biggers (2019-02-26 20:47:26)
> > From: Eric Biggers
> >
> > If drm_gem_handle_create() fails in vgem_gem_create(), then the
> > drm_vgem_gem_object is freed twice: once when the reference is dropped
> > by drm_gem_objec
On 2/26/19 2:47 PM, Jason Wessel wrote:
> We'll have to fix them at some point.
>
Yep. And we're about to fix them all.
> Acked-by: Jason Wessel
>
Thanks, Jason.
--
Gustavo
>
> Cheers,
> Jason.
>
> On 2/26/19 1:16 PM, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit-
On Tue, Feb 26, 2019 at 5:55 AM Jisheng Zhang
wrote:
>
> Currently, the PCI dwc host users don't support the remove, but nothing
> prevent us from supporting it. To achieve this goal, we need to ensure
> we can do necessary clean up work.
>
> Jisheng Zhang (5):
> PCI: dwc: fix dw_pcie_free_msi()
Hi,
On 26-02-19 20:23, Gustavo A. R. Silva wrote:
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/virt/vboxguest/vboxguest_core.c: In function ‘vbg_core_ioctl’:
drivers/virt/vboxguest/v
Quoting Eric Biggers (2019-02-26 20:47:26)
> From: Eric Biggers
>
> If drm_gem_handle_create() fails in vgem_gem_create(), then the
> drm_vgem_gem_object is freed twice: once when the reference is dropped
> by drm_gem_object_put_unlocked(), and again by __vgem_gem_destroy().
>
> This was hit by
On Tue, Feb 26, 2019 at 01:07:43PM -0600, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warning:
>
> drivers/watchdog/w83877f_wdt.c: In function ‘fop_ioctl’:
> drivers/
On Tue, Feb 26, 2019 at 12:01:14PM -0600, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warning:
>
> drivers/watchdog/sc520_wdt.c: In function ‘fop_ioctl’:
> drivers/wa
On Tue, Feb 26, 2019 at 11:58:35AM -0600, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warning:
>
> drivers/watchdog/sbc60xxwdt.c: In function ‘fop_ioctl’:
> drivers/w
/habanalabs/habanalabs.ko] undefined!
> ERROR: "gen_pool_free" [drivers/misc/habanalabs/habanalabs.ko] undefined!
>
> Signed-off-by: Randy Dunlap
> Cc: Oded Gabbay
> ---
> drivers/misc/habanalabs/Kconfig |1 +
> 1 file changed, 1 insertion(+)
>
> --- l
On Tue, 26 Feb 2019 at 21:44, Nick Desaulniers wrote:
>
> On Mon, Feb 25, 2019 at 11:19 PM Ard Biesheuvel
> wrote:
> >
> > On Tue, 26 Feb 2019 at 05:03, wrote:
> > >
> > > Clang warns: vector initializers are not compatible with NEON intrinsics
> > > in big endian mode [-Wnonportable-vector-init
The shm_* hooks were changed in the commit
"shm/security: Pass kern_ipc_perm not shmid_kernel into the
shm security hooks" (7191adff2a55). The type of the argument
shp was changed from shmid_kernel to kern_ipc_perm. This patch
updates the documentation for the hooks accordingly.
Signed-off-by: Den
The sem_* hooks were changed in the commit
"sem/security: Pass kern_ipc_perm not sem_array into the
sem security hooks" (aefad9593ec5). The type of the argument
sma was changed from sem_array to kern_ipc_perm. This patch
updates the documentation for the hooks accordingly.
Signed-off-by: Denis Efr
This patch updates the documentation for the audit_* hooks
to use the same arguments names as in the hook's declarations.
Signed-off-by: Denis Efremov
---
include/linux/lsm_hooks.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/linux/lsm_hooks.h b/include/lin
The msg_queue_* hooks were changed in the commit
"msg/security: Pass kern_ipc_perm not msg_queue into the msg_queue
security hooks" (d8c6e8543294). The type of the argument msq was changed
from msq_queue to kern_ipc_perm. This patch updates the documentation
for the hooks accordingly.
Signed-off-b
Fix for name mismatch and omitted colons in the
security_list_options documentation.
Signed-off-by: Denis Efremov
---
include/linux/lsm_hooks.h | 23 +--
1 file changed, 9 insertions(+), 14 deletions(-)
diff --git a/include/linux/lsm_hooks.h b/include/linux/lsm_hooks.h
index
This patch slightly fixes the documentation for the
socket_post_create hook. The documentation states that
i_security field is accessible through inode field of socket
structure (i.e., 'sock->inode->i_security'). There is no inode
field in the socket structure. The i_security field is accessible
th
The path_chmod hook was changed in the commit
"switch security_path_chmod() to struct path *" (cdcf116d44e7).
The argument @mnt was removed from the hook, @dentry was changed
to @path. This patch updates the documentation accordingly.
Signed-off-by: Denis Efremov
---
include/linux/lsm_hooks.h |
The socket_getpeersec_dgram hook was changed in the commit
"[AF_UNIX]: Kernel memory leak fix for af_unix datagram
getpeersec patch" (dc49c1f94e34). The arguments @secdata
and @seclen were changed to @sock and @secid. This patch
updates the documentation accordingly.
Signed-off-by: Denis Efremov
The syslog hook was changed in the commit
"capabilities/syslog: open code cap_syslog logic to
fix build failure" (12b3052c3ee8). The argument @from_file
was removed from the hook. This patch updates the
documentation for the syslog hook accordingly.
Signed-off-by: Denis Efremov
---
include/linux
The task_setscheduler hook was changed in the commit
"security: remove unused parameter from security_task_setscheduler()"
(b0ae19811375). The arguments @policy, @lp were removed from the hook.
This patch updates the documentation accordingly.
Signed-off-by: Denis Efremov
---
include/linux/lsm_h
The @type argument of the sb_copy_data hook was removed
in the commit "LSM/SELinux: Interfaces to allow FS to control
mount options" (e0007529893c). This commit removes the description
of the @type argument from the LSM documentation.
Signed-off-by: Denis Efremov
---
include/linux/lsm_hooks.h |
From: Eric Biggers
If drm_gem_handle_create() fails in vgem_gem_create(), then the
drm_vgem_gem_object is freed twice: once when the reference is dropped
by drm_gem_object_put_unlocked(), and again by __vgem_gem_destroy().
This was hit by syzkaller using fault injection.
Fix it by skipping the
Recent "New LSM Hooks" discussion has led me to the
thought that it might be a good idea to slightly
update the current documentation. The patchset adds
nothing new to the documentation, only fixes the old
description of hooks to reflect their current state.
V2 adds the clarification on arguments
201 - 300 of 929 matches
Mail list logo
