[PATCH 12/27] x86: Lock down IO port access when the kernel is locked down

From: Matthew Garrett IO port access would permit users to gain access to PCI configuration registers, which in turn (on a lot of hardware) give access to MMIO register space. This would potentially permit root to trigger arbitrary DMA, so lock it down by default. This also implicitly locks

[PATCH 27/27] lockdown: Print current->comm in restriction messages

From: David Howells Print the content of current->comm in messages generated by lockdown to indicate a restriction that was hit. This makes it a bit easier to find out what caused the message. The message now patterned something like: Lockdown: : is restricted; see man

[PATCH 19/27] Lock down TIOCSSERIAL

From: David Howells Lock down TIOCSSERIAL as that can be used to change the ioport and irq settings on a serial port. This only appears to be an issue for the serial drivers that use the core serial code. All other drivers seem to either ignore attempts to change port/irq or give an error.

[PATCH 15/27] acpi: Ignore acpi_rsdp kernel param when the kernel has been locked down

From: Josh Boyer This option allows userspace to pass the RSDP address to the kernel, which makes it possible for a user to modify the workings of hardware . Reject the option when the kernel is locked down. Signed-off-by: Josh Boyer Signed-off-by: David Howells Reviewed-by: "Lee, Chun-Yi"

Re: [PATCH 1/3] mm/mincore: make mincore() more conservative

On Wed, 6 Mar 2019, Andrew Morton wrote: > > The semantics of what mincore() considers to be resident is not completely > > clear, but Linux has always (since 2.3.52, which is when mincore() was > > initially done) treated it as "page is available in page cache". > > > > That's potentially a

[PATCH 26/27] debugfs: Restrict debugfs when the kernel is locked down

From: David Howells Disallow opening of debugfs files that might be used to muck around when the kernel is locked down as various drivers give raw access to hardware through debugfs. Given the effort of auditing all 2000 or so files and manually fixing each one as necessary, I've chosen to

[PATCH 25/27] Lock down perf

From: David Howells Disallow the use of certain perf facilities that might allow userspace to access kernel data. Signed-off-by: David Howells Signed-off-by: Matthew Garrett --- kernel/events/core.c | 5 + 1 file changed, 5 insertions(+) diff --git a/kernel/events/core.c

[PATCH 23/27] Lock down kprobes

From: David Howells Disallow the creation of kprobes when the kernel is locked down by preventing their registration. This prevents kprobes from being used to access kernel memory, either to make modifications or to steal crypto data. Reported-by: Alexei Starovoitov Signed-off-by: David

[PATCH 18/27] Prohibit PCMCIA CIS storage when the kernel is locked down

From: David Howells Prohibit replacement of the PCMCIA Card Information Structure when the kernel is locked down. Suggested-by: Dominik Brodowski Signed-off-by: David Howells cc: linux-pcm...@lists.infradead.org Signed-off-by: Matthew Garrett --- drivers/pcmcia/cistpl.c | 3 +++ 1 file

[PATCH 24/27] bpf: Restrict kernel image access functions when the kernel is locked down

From: David Howells There are some bpf functions can be used to read kernel memory: bpf_probe_read, bpf_probe_write_user and bpf_trace_printk. These allow private keys in kernel memory (e.g. the hibernation image signing key) to be read by an eBPF program and kernel memory to be altered without

[PATCH 21/27] x86/mmiotrace: Lock down the testmmiotrace module

From: David Howells The testmmiotrace module shouldn't be permitted when the kernel is locked down as it can be used to arbitrarily read and write MMIO space. Suggested-by: Thomas Gleixner Signed-off-by: David Howells cc: Steven Rostedt cc: Ingo Molnar cc: "H. Peter Anvin" cc:

[PATCH 11/27] PCI: Lock down BAR access when the kernel is locked down

From: Matthew Garrett Any hardware that can potentially generate DMA has to be locked down in order to avoid it being possible for an attacker to modify kernel code, allowing them to circumvent disabled module loading or module signing. Default to paranoid - in future we can potentially relax

[PATCH 20/27] Lock down module params that specify hardware parameters (eg. ioport)

From: David Howells Provided an annotation for module parameters that specify hardware parameters (such as io ports, iomem addresses, irqs, dma channels, fixed dma buffers and other types). Suggested-by: Alan Cox Signed-off-by: David Howells Signed-off-by: Matthew Garrett ---

[PATCH 22/27] Lock down /proc/kcore

From: David Howells Disallow access to /proc/kcore when the kernel is locked down to prevent access to cryptographic data. Signed-off-by: David Howells Reviewed-by: James Morris Signed-off-by: Matthew Garrett --- fs/proc/kcore.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 14/27] ACPI: Limit access to custom_method when the kernel is locked down

From: Matthew Garrett custom_method effectively allows arbitrary access to system memory, making it possible for an attacker to circumvent restrictions on module loading. Disable it if the kernel is locked down. Signed-off-by: Matthew Garrett Signed-off-by: David Howells Reviewed-by: "Lee,

[PATCH 16/27] acpi: Disable ACPI table override if the kernel is locked down

From: Linn Crosetto >From the kernel documentation (initrd_table_override.txt): If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible to override nearly any ACPI table provided by the BIOS with an instrumented, modified one. When securelevel is set, the kernel should

[PATCH 10/27] uswsusp: Disable when the kernel is locked down

From: Matthew Garrett uswsusp allows a user process to dump and then restore kernel state, which makes it possible to modify the running kernel. Disable this if the kernel is locked down. Signed-off-by: Matthew Garrett Signed-off-by: David Howells Reviewed-by: "Lee, Chun-Yi" Reviewed-by:

[PATCH 08/27] kexec_file: Restrict at runtime if the kernel is locked down

From: Jiri Bohac When KEXEC_SIG is not enabled, kernel should not load images through kexec_file systemcall if the kernel is locked down. [Modified by David Howells to fit with modifications to the previous patch and to return -EPERM if the kernel is locked down for consistency with other

[PATCH 13/27] x86/msr: Restrict MSR access when the kernel is locked down

From: Matthew Garrett Writing to MSRs should not be allowed if the kernel is locked down, since it could lead to execution of arbitrary code in kernel mode. Based on a patch by Kees Cook. MSR accesses are logged for the purposes of building up a whitelist as per Alan Cox's suggestion.

[PATCH 06/27] Copy secure_boot flag in boot params across kexec reboot

From: Dave Young Kexec reboot in case secure boot being enabled does not keep the secure boot mode in new kernel, so later one can load unsigned kernel via legacy kexec_load. In this state, the system is missing the protections provided by secure boot. Adding a patch to fix this by retain the

[PATCH 07/27] kexec_file: split KEXEC_VERIFY_SIG into KEXEC_SIG and KEXEC_SIG_FORCE

From: Jiri Bohac This is a preparatory patch for kexec_file_load() lockdown. A locked down kernel needs to prevent unsigned kernel images from being loaded with kexec_file_load(). Currently, the only way to force the signature verification is compiling with KEXEC_VERIFY_SIG. This prevents

[PATCH 05/27] kexec_load: Disable at runtime if the kernel is locked down

From: Matthew Garrett The kexec_load() syscall permits the loading and execution of arbitrary code in ring 0, which is something that lock-down is meant to prevent. It makes sense to disable kexec_load() in this situation. This does not affect kexec_file_load() syscall which can check for a

[PATCH 04/27] Restrict /dev/{mem,kmem,port} when the kernel is locked down

From: Matthew Garrett Allowing users to read and write to core kernel memory makes it possible for the kernel to be subverted, avoiding module loading restrictions, and also to steal cryptographic information. Disallow /dev/mem and /dev/kmem from being opened this when the kernel has been

[PULL REQUEST] Kernel lockdown patches for 5.2

Hi James, This patchset introduces an optional kernel lockdown feature, intended to strengthen the boundary between UID 0 and the kernel. When enabled and active (by enabling the config option and passing the "lockdown" option on the kernel command line), various pieces of kernel functionality

[PATCH 03/27] Enforce module signatures if the kernel is locked down

From: David Howells If the kernel is locked down, require that all modules have valid signatures that we can verify. I have adjusted the errors generated: (1) If there's no signature (ENODATA) or we can't check it (ENOPKG, ENOKEY), then: (a) If signatures are enforced then

[PATCH 02/27] Add a SysRq option to lift kernel lockdown

From: Kyle McMartin Make an option to provide a sysrq key that will lift the kernel lockdown, thereby allowing the running kernel image to be accessed and modified. On x86 this is triggered with SysRq+x, but this key may not be available on all arches, so it is set by setting LOCKDOWN_LIFT_KEY

[PATCH v3 1/1] mm: introduce put_user_page*(), placeholder versions

From: John Hubbard Introduces put_user_page(), which simply calls put_page(). This provides a way to update all get_user_pages*() callers, so that they call put_user_page(), instead of put_page(). Also introduces put_user_pages(), and a few dirty/locked variations, as a replacement for

[PATCH v3 0/1] mm: introduce put_user_page*(), placeholder versions

From: John Hubbard Hi Andrew and all, Can we please apply this (destined for 5.2) once the time is right? (I see that -mm just got merged into the main tree today.) We seem to have pretty solid consensus on the concept and details of the put_user_pages() approach. Or at least, if we don't,

Re: [RFC][QEMU Patch] KVM: Enable QEMU to free the pages hinted by the guest

On Wed, Mar 6, 2019 at 7:52 AM Nitesh Narayan Lal wrote: > > This patch enables QEMU to perform MADVISE_DONTNEED on the pages > reported by the guest. > > Signed-off-by: Nitesh Narayan Lal > --- > hw/virtio/trace-events| 1 + > hw/virtio/virtio-balloon.c

Re: [GIT PULL] Driver core patches for 5.1-rc1

On Wed, Mar 6, 2019 at 2:33 AM Greg KH wrote: > > Joe Perches (1): > device.h: Add __cold to dev_ logging functions This is very funky, but that commit generates a new warning in a totally unrelated area: drivers/iio/adc/qcom-pm8xxx-xoadc.c: In function ‘pm8xxx_xoadc_probe’:

Re: [PATCH v4 03/22] iommu: introduce device fault report API

On Tue, 5 Mar 2019 15:03:41 + Jean-Philippe Brucker wrote: > On 18/02/2019 13:54, Eric Auger wrote: > [...]> +/** > > + * iommu_register_device_fault_handler() - Register a device fault > > handler > > + * @dev: the device > > + * @handler: the fault handler > > + * @data: private data

Re: [RFC][Patch v9 1/6] KVM: Guest free page hinting support

On Wed, Mar 6, 2019 at 7:51 AM Nitesh Narayan Lal wrote: > > This patch adds the following: > 1. Functional skeleton for the guest implementation. It enables the > guest to maintain the PFN of head buddy free pages of order > FREE_PAGE_HINTING_MIN_ORDER (currently defined as MAX_ORDER - 1) > in a

Re: [PATCH 0/3] mincore() and IOCB_NOWAIT adjustments

On Thu, 7 Mar 2019 00:32:09 +0100 Dominique Martinet wrote: > Andrew Morton wrote on Wed, Mar 06, 2019: > > On Wed, 6 Mar 2019 23:48:03 +0100 (CET) Jiri Kosina > > wrote: > > > > > 3/3 is actually waiting for your decision, see > > > > > >

Re: [RFC] Provide in-kernel headers for making it easy to extend the kernel

On Wed, Mar 6, 2019 at 3:09 PM Pavel Machek wrote: > > > > > >Ok, I'll look into LZMA. Thanks for checking the compression sizes. > > > > > > > >- Joel > > > > > > Don't use lzma, use xz if you are going to do something. > > > > Ok, sounds good. XZ is a file format for LZMA2. Everyone's right.

Re: [RFC] Provide in-kernel headers for making it easy to extend the kernel

On 3/6/19 3:09 PM, Pavel Machek wrote: > On Fri 2019-01-18 17:55:43, Joel Fernandes wrote: >> From: "Joel Fernandes (Google)" >> >> Introduce in-kernel headers and other artifacts which are made available >> as an archive through proc (/proc/kheaders.tgz file). This archive makes >> it possible

Re: [PATCH 0/3] mincore() and IOCB_NOWAIT adjustments

Andrew Morton wrote on Wed, Mar 06, 2019: > On Wed, 6 Mar 2019 23:48:03 +0100 (CET) Jiri Kosina wrote: > > > 3/3 is actually waiting for your decision, see > > > > https://lore.kernel.org/lkml/20190212063643.gl15...@dhcp22.suse.cz/ > > I pity anyone who tried to understand this code by

Re: [PATCH] fs: 9p: Kconfig: pedantic cleanups

Enrico Weigelt, metux IT consult wrote on Wed, Mar 06, 2019: > Signed-off-by: Enrico Weigelt, metux IT consult I don't mind trivial patches but please resend with a description of what is done (change spaces to tabs) in the commit message. That aside I gues there's no harm in it, thanks for the

Re: [PATCH 0/3] mincore() and IOCB_NOWAIT adjustments

On Wed, 6 Mar 2019 23:48:03 +0100 (CET) Jiri Kosina wrote: > 3/3 is actually waiting for your decision, see > > https://lore.kernel.org/lkml/20190212063643.gl15...@dhcp22.suse.cz/ I pity anyone who tried to understand this code by reading this code. Can we please get some careful

Re: [PATCH v2 07/12] NTB: Introduce functions to calculate multi-port resource index

On 2019-03-06 3:45 p.m., Serge Semin wrote: [Snip] Pretty sure everything above is just agreement... > So your current approach is inbound MW-centralized, while mine is developed > around the outbound MWs. I don't think this has anything to do with inbound vs outbound. The problem is the

[PATCH] dt-bindings: remoteproc: Rename qcom,adsp binding document

The qcom,adsp binding document has evolved to cover the mechanism to load and boot firmware on a range of different Hexagon based remote subsystems. Rename the binding and update the description to better capture this. Signed-off-by: Bjorn Andersson --- .../{qcom,adsp.txt => qcom,q6v5-pas.txt}

Re: [PATCH v1] clk: Probe defer clk_get() on orphans

Quoting Jeffrey Hugo (2019-03-06 13:48:13) > Ping? > > Stephen, I know as this depends on your clock parent handling series > (happens to apply just fine to v2), its not going to be accepted until > that gets sorted out, but do you have any thoughts on if this seems like > an appropriate thing

[PATCH v2 1/5] i2c: mux: pca9541: use the BIT macro

Because it looks nice! Reviewed-by: Guenter Roeck Reviewed-by: Vladimir Zapolskiy Signed-off-by: Peter Rosin --- drivers/i2c/muxes/i2c-mux-pca9541.c | 29 +++-- 1 file changed, 15 insertions(+), 14 deletions(-) diff --git a/drivers/i2c/muxes/i2c-mux-pca9541.c

[PATCH v2 5/5] i2c: mux: pca9541: add support for PCA9641

Heavily based on code from Ken Chen . Signed-off-by: Peter Rosin --- drivers/i2c/muxes/Kconfig | 6 +- drivers/i2c/muxes/i2c-mux-pca9541.c | 137 ++-- 2 files changed, 136 insertions(+), 7 deletions(-) diff --git a/drivers/i2c/muxes/Kconfig

[PATCH v2 2/5] i2c: mux: pca9541: namespace cleanup

In preparation for PCA9641 support, convert the mybus and busoff macros to functions, and in the process prefix them with pca9541_. Also prefix remaining chip specific macros with PCA9541_. Reviewed-by: Vladimir Zapolskiy Reviewed-by: Guenter Roeck Signed-off-by: Peter Rosin ---

[PATCH v2 3/5] i2c: mux: pca9541: prepare for PCA9641 support

Make the arbitrate and release_bus implementation chip specific. Reviewed-by: Guenter Roeck Reviewed-by: Vladimir Zapolskiy Signed-off-by: Peter Rosin --- drivers/i2c/muxes/i2c-mux-pca9541.c | 62 +++-- 1 file changed, 45 insertions(+), 17 deletions(-) diff

[PATCH v2 4/5] dt-bindings: i2c: pca9541: extend with compatible for PCA9641

The binding is equivalent apart from the compatible. Signed-off-by: Peter Rosin --- Documentation/devicetree/bindings/i2c/nxp,pca9541.txt | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/i2c/nxp,pca9541.txt

[PATCH v2 0/5] i2c: mux: pca9541: extend with support for pca9641

Hi! So, it's been a year or so since this was last visited. Time flies. At that time, Ken Chen gave up and I didn't want to add untested code. However, Pradeep Srinivasan asked about PCA9641 and so I have now rebased the preparatory patches to v5.0 and added the bits Ken wrote on top of the

Re: [PATCH 1/3] mm/mincore: make mincore() more conservative

On Wed, 30 Jan 2019 13:44:18 +0100 Vlastimil Babka wrote: > From: Jiri Kosina > > The semantics of what mincore() considers to be resident is not completely > clear, but Linux has always (since 2.3.52, which is when mincore() was > initially done) treated it as "page is available in page

Re: [PATCH v2 09/12] NTB: Introduce MSI library

On Wed, Mar 06, 2019 at 02:35:53PM -0700, Logan Gunthorpe wrote: > > > On 2019-03-06 1:26 p.m., Serge Semin wrote: > > First of all, It might be unsafe to have some resources consumed by NTB > > MSI or some other library without a simple way to warn NTB client drivers > > about their attempts to

Re: [RFC][Patch v9 0/6] KVM: Guest Free Page Hinting

On Wed, Mar 6, 2019 at 2:18 PM Michael S. Tsirkin wrote: > > On Wed, Mar 06, 2019 at 10:40:57PM +0100, David Hildenbrand wrote: > > On 06.03.19 21:32, Michael S. Tsirkin wrote: > > > On Wed, Mar 06, 2019 at 07:59:57PM +0100, David Hildenbrand wrote: > > >> On 06.03.19 19:43, Michael S. Tsirkin

Re: 4.20.1: BUG: unable to handle kernel paging request at 0000100000000008

On Tue 2019-01-22 11:15:39, Harald Dunkel wrote: > Is this the wrong list to report this problem? I haven't found a > "mem" mailing list on vger. Right list, ugly looking problem. How reproducible is it? You may want to look at MAINTAINERS file, cc x86 and memory management people...?

Re: [PATCH] devfreq: Suspend all devices on system shutdown

On Fri 2019-01-25 14:54:03, Marek Szyprowski wrote: > This way devfreq core ensures that all its devices will be set to safe > operation points before reboot operation. There are board on which some > aggressive power saving operation points are behind the capabilities of > the bootloader to

Re: [PATCH v5 00/18] mfd: demodularization of non-modular drivers

On Wed 2019-01-16 13:24:31, Lee Jones wrote: > [...] > > > Paul Gortmaker (18): > > mfd: aat2870-core: Make it explicitly non-modular > > mfd: adp5520: Make it explicitly non-modular > > mfd: as3711: Make it explicitly non-modular > > mfd: db8500-prcmu: drop unused MODULE_ tags from

Re: System crash with perf_fuzzer (kernel: 5.0.0-rc3)

On Fri 2019-01-25 08:00:56, Andi Kleen wrote: > > [Fri Jan 25 10:28:53 2019] perf: interrupt took too long (2501 > 2500), > > lowering kernel.perf_event_max_sample_rate to 79750 > > [Fri Jan 25 10:29:08 2019] perf: interrupt took too long (3136 > 3126), > > lowering

Re: [RFC] Provide in-kernel headers for making it easy to extend the kernel

On Fri 2019-01-18 17:55:43, Joel Fernandes wrote: > From: "Joel Fernandes (Google)" > > Introduce in-kernel headers and other artifacts which are made available > as an archive through proc (/proc/kheaders.tgz file). This archive makes > it possible to build kernel modules, run eBPF programs,

Re: [RFC] Provide in-kernel headers for making it easy to extend the kernel

> > >Ok, I'll look into LZMA. Thanks for checking the compression sizes. > > > > > >- Joel > > > > Don't use lzma, use xz if you are going to do something. > > Ok, sounds good. > > > However, it seems unlikely to me that someone not willing to spend the > > space in the filesystem will spend

[PATCH 3/7] i3c: master: dw: remove dead code from dw_i3c_master_*_xfers()

Detected by CoverityScan (Event result_independent_of_operands): "(i3c_xfers + i).len > 65536" is always false regardless of the values of its operands. This occurs as the logical operand of "if" "(i2c_xfers + i).len > 65536" is always false regardless of the values of its operands. This occurs

[PATCH v1] drm/tegra: gem: Fix CPU-cache maintenance for BO's allocated using get_pages()

The allocated pages need to be invalidated in CPU caches. On ARM32 the DMA_BIDIRECTIONAL flag only ensures that data is written-back to DRAM and the data stays in CPU cache lines. While the DMA_FROM_DEVICE flag ensures that the corresponding CPU cache lines are getting invalidated and nothing

[GIT PULL] RTC for 5.1

Hello Linus, Here is the pull-request for the RTC subsystem for 5.1. There is an unusual amount of new drivers this cycle, and this explains the number of insertions. Other than that, the changes are the usual fixes and feature addition. The following changes since commit

[PATCH v1 2/3] iommu/tegra-smmu: Properly release domain resources

Release all memory allocations associated with a released domain and emit warning if domain is in-use at the time of destruction. Signed-off-by: Dmitry Osipenko --- drivers/iommu/tegra-smmu.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/iommu/tegra-smmu.c

[PATCH v1 3/3] iommu/tegra-smmu: Respect IOMMU API read-write protections

Set PTE read/write attributes accordingly to the the protections requested by IOMMU API. Signed-off-by: Dmitry Osipenko --- drivers/iommu/tegra-smmu.c | 13 ++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/drivers/iommu/tegra-smmu.c b/drivers/iommu/tegra-smmu.c index

[PATCH v1 1/3] iommu/tegra-smmu: Fix invalid ASID bits on Tegra30/114

Both Tegra30 and Tegra114 have 4 ASID's and the corresponding bitfield of the TLB_FLUSH register differs from later Tegra generations that have 128 ASID's. In a result the PTE's are now flushed correctly from TLB and this fixes problems with graphics (randomly failing tests) on Tegra30. Cc:

[PATCH v1 0/3] IOMMU: Tegra SMMU fixes

Hello, This small series primarily fixes a bug that affects Terga30 and Terga114 platforms, it also carries two patches that improve SMMU functionality and clean up code a tad. Dmitry Osipenko (3): iommu/tegra-smmu: Fix invalid ASID bits on Tegra30/114 iommu/tegra-smmu: Properly release

[PATCH] nfsd: allow nfsv3 readdir request to be larger.

nfsd currently reports the NFSv4 dtpref FSINFO parameter to be PAGE_SIZE, so NFS clients will typically ask for one page of directory entries at a time. This is needlessly restrictive as nfsd can handle larger replies easily. Also, a READDIR request (but not a READDIRPLUS request) has the count

Re: [PATCH 0/3] mincore() and IOCB_NOWAIT adjustments

On Wed, 6 Mar 2019, Andrew Morton wrote: > > could you please take at least the correct and straightforward fix for > > mincore() before we figure out how to deal with the slightly less > > practical RWF_NOWAIT? Thanks. > > I assume we're talking about [1/3] and [2/3] from this thread? > >

Re: [PATCH v2 07/12] NTB: Introduce functions to calculate multi-port resource index

On Wed, Mar 06, 2019 at 12:11:11PM -0700, Logan Gunthorpe wrote: > > > On 2019-03-05 6:24 p.m., Serge Semin wrote: > >> + * In a 5 peer system, this function will return the following matrix > >> + * > >> + * pidx \ port01234 > >> + * 0 00123 > >>

[PATCH 8/8] media: vimc: propagate pixel format in the stream

Media bus codes were being mapped to pixelformats, which causes a limitation on vimc because not all pixelformats can be mapped to media bus codes. Also, media bus codes are an internal configuration from the device. Userspace only assures media bus codes matches between pads and expects the image

[PATCH 7/8] media: vimc: stream: init/terminate the first entity

The s_stream callback was not being called for the first entity in the stream pipeline array. Instead of verifying the type of the node (video or subdevice) and calling s_stream from the second entity in the pipeline, do this process for all the entities in the pipeline for consistency. The

[PATCH 4/8] media: v4l2-common: add bayer formats in v4l2_format_info

Add bayer format information in struct v4l2_format_info table. Signed-off-by: Helen Koike --- drivers/media/v4l2-core/v4l2-common.c | 22 ++ 1 file changed, 22 insertions(+) diff --git a/drivers/media/v4l2-core/v4l2-common.c b/drivers/media/v4l2-core/v4l2-common.c index

[PATCH 5/8] media: vimc: stream: cleanup frame field from struct vimc_stream

There is no need to have the frame field in the vimc_stream struct. Signed-off-by: Helen Koike --- drivers/media/platform/vimc/vimc-streamer.c | 10 -- drivers/media/platform/vimc/vimc-streamer.h | 1 - 2 files changed, 4 insertions(+), 7 deletions(-) diff --git

[PATCH 6/8] media: vimc: stream: add docs to struct vimc_stream

Add missing documentation for struct vimc_stream Signed-off-by: Helen Koike --- drivers/media/platform/vimc/vimc-streamer.h | 15 +++ 1 file changed, 15 insertions(+) diff --git a/drivers/media/platform/vimc/vimc-streamer.h b/drivers/media/platform/vimc/vimc-streamer.h index

[PATCH 1/8] media: vimc: deb: fix default sink bayer format

The format of the sink pad should be a bayer mbus format. This fixes a kernel NULL pointer dereference error that was caused when the stream starts because the configured format was not found in the pixelmap table. Reported-by: Hans Verkuil Signed-off-by: Helen Koike ---

[PATCH 0/8] media: vimc: remove media bus code limitation

Hello, This patch series has several vimc fixes (that I am sending in the same series only for convenience, let me know if you prefer them to be sent separately from the series). The last commit removes the vimc_pix_map_list[] that was mapping pixelformats with media bus formats, but it turns

[PATCH 3/8] media: vimc: cap: fix step width/height in enum framesize

The type V4L2_FRMSIZE_TYPE_CONTINUOUS expects a step of 1. This fixes v4l2-compliance test error: fail: v4l2-test-formats.cpp(184): invalid step_width/height for continuous framesize test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: FAIL Signed-off-by: Helen Koike ---

[PATCH 2/8] media: vimc: stream: fix thread state before sleep

The state TASK_UNINTERRUPTIBLE should be set just before schedule_timeout() call, so it knows the sleep mode it should enter. There is no point in setting TASK_UNINTERRUPTIBLE at the initialization of the thread as schedule_timeout() will set the state back to TASK_RUNNING. This fixes a warning

[PATCH v4 3/4] ARM: dts: rockchip: rk3066a-mk808: enable vop0 and hdmi nodes

This patch enables the vop0 and hdmi nodes for a MK808 with rk3066 processor. Signed-off-by: Johan Jonker --- arch/arm/boot/dts/rk3066a-mk808.dts | 29 + 1 file changed, 29 insertions(+) diff --git a/arch/arm/boot/dts/rk3066a-mk808.dts

[PATCH v4 4/4] dt-bindings: display: rockchip: add document for rk3066 hdmi

This patch adds a binding that describes the HDMI controller for rk3066. Signed-off-by: Johan Jonker --- .../display/rockchip/rockchip,rk3066-hdmi.txt | 72 ++ 1 file changed, 72 insertions(+) create mode 100644

[PATCH v4 2/4] ARM: dts: rockchip: add rk3066 hdmi nodes

From: Zheng Yang This patch adds the hdmi nodes to rk3066. Signed-off-by: Zheng Yang Signed-off-by: Johan Jonker --- arch/arm/boot/dts/rk3066a.dtsi | 52 ++ 1 file changed, 52 insertions(+) diff --git a/arch/arm/boot/dts/rk3066a.dtsi

[PATCH v4 1/4] drm: rockchip: introduce rk3066 hdmi

From: Zheng Yang The RK3066 HDMI TX serves as interface between a LCD Controller and a HDMI bus. A HDMI TX consists of one HDMI transmitter controller and one HDMI transmitter PHY. The interface has three (3) 8-bit data channels which can be configured for a number of bus widths

[PATCH v4 0/4] Enable rk3066 VOP and HDMI for MK808

For testing only. Version: V4 Title: Enable rk3066 VOP and HDMI for MK808. This patch serie only works in combination with a MK808 TV stick and a rk3066 processor. Other boxes and tablets with a rk3066 need extra software for power management and lcd's. What does it do: With these kernel

Re: [PATCH 0/3] mincore() and IOCB_NOWAIT adjustments

On Wed, 6 Mar 2019 13:11:39 +0100 (CET) Jiri Kosina wrote: > On Wed, 30 Jan 2019, Vlastimil Babka wrote: > > > I've collected the patches from the discussion for formal posting. The first > > two should be settled already, third one is the possible improvement I've > > mentioned earlier, where

[tip:x86/urgent] x86/hyperv: Fix kernel panic when kexec on HyperV

Commit-ID: 179fb36abb097976997f50733d5b122a29158cba Gitweb: https://git.kernel.org/tip/179fb36abb097976997f50733d5b122a29158cba Author: Kairui Song AuthorDate: Wed, 6 Mar 2019 19:18:27 +0800 Committer: Thomas Gleixner CommitDate: Wed, 6 Mar 2019 23:27:44 +0100 x86/hyperv: Fix kernel

[tip:x86/urgent] x86/mm: Remove unused variable 'old_pte'

Commit-ID: 24c41220659ecc5576c34c6f23537f8d3949fb05 Gitweb: https://git.kernel.org/tip/24c41220659ecc5576c34c6f23537f8d3949fb05 Author: Qian Cai AuthorDate: Fri, 1 Mar 2019 10:29:24 -0500 Committer: Thomas Gleixner CommitDate: Wed, 6 Mar 2019 23:24:53 +0100 x86/mm: Remove unused

Re: [PATCH v1] Bluetooth: hci_qca: Give enough time to ROME controller to bootup.

Quoting Balakrishna Godavarthi (2019-03-06 08:21:13) > This patch enables enough time to ROME controller to bootup > after we bring the enable ping out of reset. > > Signed-off-by: Balakrishna Godavarthi > --- Any Fixes tag? And maybe some more explanation or background on where 150 ms sleep

[tip:x86/urgent] x86/mm: Remove unused variable 'cpu'

Commit-ID: 3609e31bc8dc03b701390f79c74fc7fe92b95039 Gitweb: https://git.kernel.org/tip/3609e31bc8dc03b701390f79c74fc7fe92b95039 Author: Qian Cai AuthorDate: Thu, 28 Feb 2019 17:01:55 -0500 Committer: Thomas Gleixner CommitDate: Wed, 6 Mar 2019 23:24:52 +0100 x86/mm: Remove unused

[tip:x86/urgent] x86/unwind: Add hardcoded ORC entry for NULL

Commit-ID: ac5ceccce5501e43d217c596e4ee859f2a3fef79 Gitweb: https://git.kernel.org/tip/ac5ceccce5501e43d217c596e4ee859f2a3fef79 Author: Jann Horn AuthorDate: Fri, 1 Mar 2019 04:12:01 +0100 Committer: Thomas Gleixner CommitDate: Wed, 6 Mar 2019 23:03:26 +0100 x86/unwind: Add hardcoded

[tip:x86/urgent] Revert "x86_64: Increase stack size for KASAN_EXTRA"

Commit-ID: a2863b53418d7d8f6332adf0cfb32611def0c4b9 Gitweb: https://git.kernel.org/tip/a2863b53418d7d8f6332adf0cfb32611def0c4b9 Author: Qian Cai AuthorDate: Wed, 6 Mar 2019 16:38:06 -0500 Committer: Thomas Gleixner CommitDate: Wed, 6 Mar 2019 23:03:27 +0100 Revert "x86_64: Increase

Actualiza tu cuenta

Web de correo electrónico de administración de notificaciones Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a todos nuestros clientes de correo web. Su cuenta de correo electrónico se

Re: [PATCH v2] xfrm: Reset secpath in xfrm failure

On 03/06/2019 01:55 PM, Myungho Jung wrote: > In esp4_gro_receive() and esp6_gro_receive(), secpath can be allocated > without adding xfrm state to xvec. Then, sp->xvec[sp->len - 1] would > fail and result in dereferencing invalid pointer in esp4_gso_segment() > and esp6_gso_segment(). Reset

[tip:x86/urgent] x86/unwind: Handle NULL pointer calls better in frame unwinder

Commit-ID: f4f34e1b82eb4219d8eaa1c7e2e17ca219a6a2b5 Gitweb: https://git.kernel.org/tip/f4f34e1b82eb4219d8eaa1c7e2e17ca219a6a2b5 Author: Jann Horn AuthorDate: Fri, 1 Mar 2019 04:12:00 +0100 Committer: Thomas Gleixner CommitDate: Wed, 6 Mar 2019 23:03:26 +0100 x86/unwind: Handle NULL

Re: [GIT PULL] sound updates for 5.1

The pull request you sent on Sat, 02 Mar 2019 09:58:59 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git > tags/sound-5.1-rc1 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/da2577fe63f865cd9dc785a42c29c0071f567a35 Thank you! -- Deet-doot-dot,

Re: [RFC PATCH v1 08/25] printk: add ring buffer and kthread

On 2019-03-06, Petr Mladek wrote: >> _Both_ categories are important for the user, but their requirements >> are different: >> >>informational: non-disturbing >>emergency: reliable > > Isn't this already handled by the console_level? > > The informational messages can be reliably

[PATCH v2] fs: cifs: Kconfig: pedantic formatting

Formatting of Kconfig files doesn't look so pretty, so just take damp cloth and clean it up. Signed-off-by: Enrico Weigelt, metux IT consult --- fs/cifs/Kconfig | 120 1 file changed, 60 insertions(+), 60 deletions(-) diff --git

The NSA Makes Ghidra, a Powerful Cybersecurity Tool, Open Source | WIRED

Good morning from Singapore, I am sharing some information technology news on open source cybersecurity tools developed by the NSA. Article: The NSA Makes Ghidra, a Powerful Cybersecurity Tool, Open Source Author: Lily Hay Newman News Media: WIRED.com Date Published: 5 Mar 2019 Time Published:

Re: [PATCH RESEND v3 2/3] drivers: qcom: rpmh-rsc: return if the controller is idle

On Wed, Mar 06 2019 at 15:12 -0700, Stephen Boyd wrote: Quoting Lina Iyer (2019-03-04 09:14:50) On Fri, Mar 01 2019 at 10:58 -0700, Stephen Boyd wrote: >Quoting Lina Iyer (2019-02-27 14:29:13) >> Hi Stephen, >> >> On Tue, Feb 26 2019 at 17:49 -0700, Stephen Boyd wrote: > >Ok, can you explain

Re: [PATCH 09/10] mm/hmm: allow to mirror vma of a file on a DAX backed filesystem

On Wed, 6 Mar 2019 10:49:04 -0500 Jerome Glisse wrote: > On Tue, Mar 05, 2019 at 02:16:35PM -0800, Andrew Morton wrote: > > On Wed, 30 Jan 2019 21:44:46 -0800 Dan Williams > > wrote: > > > > > > > > > > > Another way to help allay these worries is commit to no new exports > > > > > without

Re: [RFC][Patch v9 0/6] KVM: Guest Free Page Hinting

On Wed, Mar 06, 2019 at 10:40:57PM +0100, David Hildenbrand wrote: > On 06.03.19 21:32, Michael S. Tsirkin wrote: > > On Wed, Mar 06, 2019 at 07:59:57PM +0100, David Hildenbrand wrote: > >> On 06.03.19 19:43, Michael S. Tsirkin wrote: > >>> On Wed, Mar 06, 2019 at 01:30:14PM -0500, Nitesh Narayan

[PATCH v1 1/5] PCI/IOV: Add support to verify PF/VF spec compliance

From: Kuppuswamy Sathyanarayanan PF/VF implementation must comply with PCIe specification as defined in r4.0, sec 9.3.4, 9.3.5, 9.3.6 and 9.3.7. And if it does not comply, return error and skip PF/VF device creation. Also add a command line parameter support to skip error when PF/VF spec

[PATCH v1 5/5] PCI/ATS: Fix ATS PF/VF dependency issues

From: Kuppuswamy Sathyanarayanan As per PCIe spec r4.0, sec 9.3.7.8, ATS Capabilities in VFs and their associated PFs may be enabled independently. But currently all VFs needs to disable ATS service before disabling the ATS service in PF. So remove this dependency logic in enable/disable code.

[PATCH v1 2/5] PCI/ATS: Fix PRI PF/VF dependency issues

From: Kuppuswamy Sathyanarayanan As per PCIe spec r4.0, sec 9.3.7.11 ("Page Request Interface (PRI)"), all VFs associated with PF can only use the Page Request Interface of the PF and not implement it. So for any PRI capability related queries on a VF device use associated PF device

<    1   2   3   4   5   6   7   8   9   10   >