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 Howell
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
cc: Dave Young
cc: linux-a...
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
---
kernel/params.c
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.
Rep
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
cc: linux-a...@vger.ke
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 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 thi
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: James Morris
cc: linux...@vger.
From: Bjorn Helgaas
pcie-xilinx-nwl.c is the only driver to use mask_msi_irq() and
unmask_msi_irq(), which are trivial wrappers around PCI-specific functions.
We obviously know we need the PCI versions in this driver, so use them
directly, as all the other PCI host controller drivers do, and remo
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 load
From: Bjorn Helgaas
Change pcie-xilinx-nwl.c to use pci_msi_mask_irq() and pci_msi_unmask_irq()
like all other PCI host controller drivers. Remove the now-unused
mask_msi_irq() and unmask_msi_irq().
Signed-off-by: Bjorn Helgaas
CC: Michal Simek
CC: linux-arm-ker...@lists.infradead.org
---
dr
From: Bjorn Helgaas
Remove unused __write_msi_msg() and write_msi_msg().
These were added by 83a18912b0e8 ("PCI/MSI: Rename write_msi_msg() to
pci_write_msi_msg()"), they served their purpose, and they're no longer
needed.
Signed-off-by: Bjorn Helgaas
CC: Jiang Liu# 83a18912b0e8 author
From: David Howells
Provide a single call to allow kernel code to determine whether the system
should be locked down, thereby disallowing various accesses that might
allow the running kernel image to be changed including the loading of
modules that aren't validly signed with a key we recognise, f
On Mon, Mar 25, 2019 at 3:04 PM Daniel Borkmann wrote:
>
> I'm fine either way, I think the rcu_destroy_inode would indeed simplify
> it nicely. In any case fwiw, here's what I'd have ready for standby on bpf
> side and tested as well. Decided to get rid of bpf_evict_inode() entirely
> since the o
If __get_free_pages() fails, the patch returns -ENOMEM to avoid
NULL pointer dereference.
Signed-off-by: Kangjie Lu
---
v3: remove "unlikely", as suggested by Bjorn Helgaas.
v2: caller is redefined to accept the error code, as suggested by
Steven Price
---
drivers/pci/controller/pcie-xilinx.c |
On 3/25/2019 3:02 PM, Joe Perches wrote:
On Mon, 2019-03-25 at 14:58 -0700, Casey Schaufler wrote:
The include/linux/selinux.h file has been removed.
Remove the entry from the MAINTAINERS file.
This looks like it doesn't apply correctly as there
are one too many spaces before each context lines
pci_ioremap_bar could fail. The patch returns in case of failure to
acquire IOMEM. It also releases the acquired resource in the exit path.
Signed-off-by: Aditya Pakki
---
v5: change pci_iounmap to iounmap to pass kbuild errors in other arch
v4: Missed resource release in dma_probe failure.
v3:
On Fri, Mar 22, 2019 at 07:36:51PM -0500, Alexandru Gagniuc wrote:
> A threaded IRQ with a NULL handler does not work with level-triggered
> interrupts. request_threaded_irq() will return an error:
>
> genirq: Threaded irq requested with handler=NULL and !ONESHOT for irq 16
> pcie_bw_notificat
On 3/25/19 5:25 PM, Bjorn Helgaas wrote:
On Fri, Mar 22, 2019 at 07:36:51PM -0500, Alexandru Gagniuc wrote:
A threaded IRQ with a NULL handler does not work with level-triggered
interrupts. request_threaded_irq() will return an error:
genirq: Threaded irq requested with handler=NULL and !ONE
On Wed, 20 Feb 2019 12:01:59 +, Anson Huang wrote:
> Update i.MX SCU resource ID table according to latest
> system controller firmware.
>
> Latest system controller firmware removes below resources
> which are never be used:
> IMX_SC_R_DC_0_CAPTURE0
> IMX_SC_R_DC_0_CAPTURE1
>
On Wed, 20 Feb 2019 22:44:33 -0800, Bjorn Andersson wrote:
> Add the shared cx/mx and the low-power-island's cx and mx power-domains
> found on QCS404.
>
> Signed-off-by: Bjorn Andersson
> ---
> .../devicetree/bindings/power/qcom,rpmpd.txt | 1 +
> drivers/soc/qcom/rpmpd.c
Hi Linus,
On Mon, Mar 25, 2019 at 9:49 PM Linus Torvalds
wrote:
>
> On Mon, Mar 25, 2019 at 2:13 PM Sudip Mukherjee
> wrote:
> >
> > We do not need to search for ports and bind the initial list of ports
> > to daisy driver as daisy driver is always the first driver to use the
> > new found parpo
On Mon, Mar 25, 2019 at 10:07 PM Daniel Colascione wrote:
>
> On Mon, Mar 25, 2019 at 2:55 PM Jonathan Kowalski wrote:
> >
> > On Mon, Mar 25, 2019 at 9:43 PM Joel Fernandes
> > wrote:
> > >
> > > On Mon, Mar 25, 2019 at 10:19:26PM +0100, Jann Horn wrote:
> > > > On Mon, Mar 25, 2019 at 10:11 P
On Mon, 25 Mar 2019, Thomas Gleixner wrote:
> That has nothing to do with 'nosmt'. It's a general bug in the rollback
> code when HOTPLUG_CPU=n. 'nosmt' is using the rollback mechanism and is
> just a reliable way to trigger the problem. This happens in the same way
> when the bringup of a CPU fail
On Mon, Mar 25, 2019 at 12:42 PM Paul E. McKenney wrote:
>
> On Mon, Mar 25, 2019 at 12:33:37PM -0400, Joel Fernandes wrote:
> > On Mon, Mar 25, 2019 at 11:02 AM Paul E. McKenney
> > wrote:
> > >
> > > On Fri, Mar 22, 2019 at 11:46:19PM -0400, Joel Fernandes (Google) wrote:
> > > > The rcutortur
On 03/25/2019 11:13 PM, Linus Torvalds wrote:
> On Mon, Mar 25, 2019 at 3:04 PM Daniel Borkmann wrote:
>>
>> I'm fine either way, I think the rcu_destroy_inode would indeed simplify
>> it nicely. In any case fwiw, here's what I'd have ready for standby on bpf
>> side and tested as well. Decided to
On Mon, Mar 11, 2019 at 06:29:49PM -0600, Jesús Castro wrote:
> The if/else block from hvt_op_open function can be written
> as a switch/case block, and the bool issue_reset variable
> is avoided.
>
> No functional change made.
>
> Suggested-by: Joe Perches
> Signed-off-by: Jesús Castro
> ---
On Mon, Mar 25, 2019 at 07:43:32PM +, Al Viro wrote:
> On Mon, Mar 25, 2019 at 11:36:01AM -0700, Linus Torvalds wrote:
> > Right. Not just move the existing destroy_inode() - because as you
> > say, people may not be able to to do that in RCU contect, but split it
> > up, and add a "final_free_
On Mon, Mar 25, 2019 at 11:04:53PM +0100, Daniel Borkmann wrote:
> +static void bpf_destroy_inode_deferred(struct rcu_head *head)
> +{
> + struct inode *inode = container_of(head, struct inode, i_rcu);
> + enum bpf_type type;
> +
> + if (S_ISLNK(inode->i_mode))
> + kfree(in
On Mon, 2019-03-25 at 11:07 +0800, Wu Hao wrote:
> In early partial reconfiguration private feature, it only
> supports 32bit data width when writing data to hardware for
> PR. 512bit data width PR support is an important optimization
> for some specific solutions (e.g. XEON with FPGA integrated),
dma_async_tx_descriptor can contain a NULL variable and using
it in dmaengine_submit without checking can crash the process.
This patch avoids such a scenario.
Signed-off-by: Aditya Pakki
---
v1: Return error in case of failure to desc variable to avoid hang up.
---
drivers/ata/sata_dwc_460ex.c
Ralph,
On Mon, 25 Mar 2019, Ralph Campbell wrote:
> On 3/23/19 12:02 PM, Thomas Gleixner wrote:
> > > --- a/arch/x86/mm/mmap.c
> > > +++ b/arch/x86/mm/mmap.c
> > > @@ -230,7 +230,7 @@ bool mmap_address_hint_valid(unsigned long addr,
> > > unsigned long len)
> > > /* Can we access it for direct r
On Mon, 2019-03-25 at 17:53 -0500, Scott Wood wrote:
> On Mon, 2019-03-25 at 11:07 +0800, Wu Hao wrote:
> > In early partial reconfiguration private feature, it only
> > supports 32bit data width when writing data to hardware for
> > PR. 512bit data width PR support is an important optimization
> >
[+cc Borislav]
Hi Borislav, sorry; I meant to cc: you when I applied the patch below.
I did add a Reported-by for you.
On Mon, Mar 25, 2019 at 05:25:02PM -0500, Bjorn Helgaas wrote:
> On Fri, Mar 22, 2019 at 07:36:51PM -0500, Alexandru Gagniuc wrote:
> > A threaded IRQ with a NULL handler does no
Hi all,
After merging the sound-asoc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
sound/soc/codecs/tlv320aic32x4-clk.c: In function 'clk_aic32x4_pll_recalc_rate':
sound/soc/codecs/tlv320aic32x4-clk.c:149:38: warning: 'settings.d' may be used
uninitialized in this f
On Tue, Mar 26, 2019 at 09:48:23AM +1100, Dave Chinner wrote:
> And when it comes to VFS inode reclaim, XFS does not implement
> ->evict_inode because there is nothing at the VFS level to do.
> And ->destroy_inode ends up doing cleanup work (e.g. freeing on-disk
> inodes) which is non-trivial, blo
Hi all,
On Mon, 18 Mar 2019 11:00:50 +1100 Stephen Rothwell
wrote:
>
> On Mon, 4 Feb 2019 09:33:34 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the vfs tree, today's linux-next build (arm
> > multi_v7_defconfig) produced this warning:
> >
> > In file included from include/linux/print
Hi all,
On Fri, 22 Mar 2019 08:30:48 +1100 Stephen Rothwell
wrote:
>
> After merging the sunxi tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> WARNING: unmet direct dependencies detected for MFD_SUN6I_PRCM
> Depends on [n]: HAS_IOMEM [=y] && ARCH_SUNXI
> Se
Le 25/03/2019 à 20:29, Dan Williams a écrit :
> Perhaps "path" might be a suitable replacement identifier rather than
> type. I.e. memory that originates from an ACPI.NFIT root device is
> likely "pmem".
Could work.
What kind of "path" would we get for other types of memory? (DDR,
non-ACPI-bas
On Mon, Mar 25, 2019 at 3:37 PM Jonathan Kowalski wrote:
>
> On Mon, Mar 25, 2019 at 10:07 PM Daniel Colascione wrote:
> >
> > On Mon, Mar 25, 2019 at 2:55 PM Jonathan Kowalski
> > wrote:
> > >
> > > On Mon, Mar 25, 2019 at 9:43 PM Joel Fernandes
> > > wrote:
> > > >
> > > > On Mon, Mar 25, 2
On Fri, 22 Mar 2019 18:20:35 -0500
Parav Pandit wrote:
> There are five problems with current code structure.
> 1. mdev device is placed on the mdev bus before it is created in the
> vendor driver. Once a device is placed on the mdev bus without creating
> its supporting underlying vendor device,
On Mon, Mar 25, 2019 at 12:28 PM Yang Shi wrote:
>
>
>
> On 3/23/19 10:21 AM, Dan Williams wrote:
> > On Fri, Mar 22, 2019 at 9:45 PM Yang Shi wrote:
> >> When running applications on the machine with NVDIMM as NUMA node, the
> >> memory allocation may end up on NVDIMM node. This may result in s
The include/linux/selinux.h file has been removed.
Remove the entry from the MAINTAINERS file.
Signed-off-by: Casey Schaufler
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3e5a5d263f29..1039c34dff3c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@
Code refactoring to share some source code with a new
EDAC driver resulted in renaming one file (skx_edac.c
became skx_base.c) and adding a new file (skx_common.c).
Update the file pattern in MAINTAINERS to take account of
this change.
Reported-by: Joe Perches
Fixes: 98f2fc829e3b ("EDAC, skx_eda
A file pattern line in this section of the MAINTAINERS file in linux-next
does not have a match in the linux source files.
This could occur because a matching filename was never added, was deleted
or renamed in some other commit.
The commits that added and if found renamed or removed the file pat
Hi John,
On Thu, Mar 21, 2019 at 02:14:08AM +0800, John Garry wrote:
> Currently when we request an IO port region, the request is made directly
> to the top resource, ioport_resource.
Let's be explicit here, e.g.,
Currently request_region() requests an IO port region directly from the
top r
> -Original Message-
> From: Alex Williamson
> Sent: Monday, March 25, 2019 6:19 PM
> To: Parav Pandit
> Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org;
> kwankh...@nvidia.com
> Subject: Re: [PATCH 8/8] vfio/mdev: Improve the create/remove sequence
>
> On Fri, 22 Mar 2019 18:2
Code restructuring renamed arch/x86/kernel/cpu/mcheck/ to
be arch/x86/kernel/cpu/mce/
Update the MAINTAINERS file pattern to account for this change.
Fixes: 21afaf181362 ("x86/mce: Streamline MCE subsystem's naming")
Reported-by: Joe Perches
Signed-off-by: Tony Luck
---
MAINTAINERS | 2 +-
1 f
On Mon, 25 Mar 2019 15:09:47 -0700
Matthew Garrett wrote:
> 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
On 3/25/19 4:18 PM, Dan Williams wrote:
On Mon, Mar 25, 2019 at 12:28 PM Yang Shi wrote:
On 3/23/19 10:21 AM, Dan Williams wrote:
On Fri, Mar 22, 2019 at 9:45 PM Yang Shi wrote:
When running applications on the machine with NVDIMM as NUMA node, the
memory allocation may end up on NVDIMM
On Mon, Mar 25, 2019 at 4:09 PM Brice Goglin wrote:
>
>
> Le 25/03/2019 à 20:29, Dan Williams a écrit :
> > Perhaps "path" might be a suitable replacement identifier rather than
> > type. I.e. memory that originates from an ACPI.NFIT root device is
> > likely "pmem".
>
>
> Could work.
>
> What kin
On Mon, Mar 25, 2019 at 02:45:00PM -0700, Linus Torvalds wrote:
> On Mon, Mar 25, 2019 at 2:14 PM Al Viro wrote:
> >
> > Maybe, but we really need to come up with sane documentation on the
> > entire drop_inode/evict_inode/destroy_inode/rcu_destroy_inode
> > group ;-/
>
> Yeah.
>
> I actually th
On Mon, Mar 25, 2019 at 9:56 AM David Howells wrote:
>
> Daniel Colascione wrote:
>
> > System calls are cheap.
>
> Only to a point. x86_64 will have an issue when we hit syscall 512. We're
> currently at 427.
>
I don't consider this to be a problem. I have patches to make this
problem go awa
Matthew,
On Mon, 25 Mar 2019, Matthew Garrett wrote:
> 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 purpos
On Mon, Mar 25, 2019 at 4:36 PM Yang Shi wrote:
[..]
> >>> Hmm, no, I don't think we should do this. Especially considering
> >>> current generation NVDIMMs are energy backed DRAM there is no
> >>> performance difference that should be assumed by the non-volatile
> >>> flag.
> >> Actually, here I
On Mon, Mar 25, 2019 at 1:23 PM Daniel Colascione wrote:
>
> On Mon, Mar 25, 2019 at 1:14 PM Jann Horn wrote:
> >
> > On Mon, Mar 25, 2019 at 8:44 PM Andy Lutomirski wrote:
> > One ioctl on procfs roots to translate pidfds into that procfs,
> > subject to both the normal lookup permission check
On Mon, Mar 25, 2019 at 11:37:32PM +, Al Viro wrote:
>
> For debugfs it's clearly "use default ->evict_inode(), have explicit
> ->destroy_inode() using free_inode_nonrcu()" - there we have nothing
> else done in ->evict_inode() and kfree is obviously safe in softirq.
> I'll post that (or push
On Mon, Mar 25, 2019 at 04:42:14PM -0700, Andy Lutomirski wrote:
> On Mon, Mar 25, 2019 at 1:23 PM Daniel Colascione wrote:
> >
> > On Mon, Mar 25, 2019 at 1:14 PM Jann Horn wrote:
> > >
> > > On Mon, Mar 25, 2019 at 8:44 PM Andy Lutomirski wrote:
>
> > > One ioctl on procfs roots to translate
This patch introduces SECURE_KEEP_FSUID to allow fsuid/fsgid to be
preserved across execve. I ran into a need for a patch trying to
implement a set-uid-root wrapper for perf.
My set-uid-root wrapper implements local policies, allowing only
certain users to run perf and only with certain arguments.
On Mon, Mar 25, 2019 at 7:21 PM Casey Schaufler wrote:
> The include/linux/selinux.h file has been removed.
> Remove the entry from the MAINTAINERS file.
>
> Signed-off-by: Casey Schaufler
> ---
> MAINTAINERS | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> ind
On Sun, Mar 24, 2019 at 1:59 AM Xing, Cedric wrote:
>
> Hi Andy,
>
> Thank you for your valuable feedbacks!
>
> Per what you have been saying, your feedbacks come from different angles -
> i.e. functionality vs. security, but they are mixed up somehow.
I think you're misunderstanding me. I'm no
We forgot to update the MAINTAINERS file when adding this
new driver.
Fixes: d4dc89d069aa ("EDAC, i10nm: Add a driver for Intel 10nm server
processors")
Signed-off-by: Tony Luck
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index e5f3230d3f1
The regulators array should never need to be modified, make it const so
compiler can put it to .rodata.
Signed-off-by: Axel Lin
---
drivers/regulator/sc2731-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/sc2731-regulator.c
b/drivers/regulator/s
On Mon, Mar 25, 2019 at 11:03 AM Sean Christopherson
wrote:
>
> On Sun, Mar 24, 2019 at 01:59:48AM -0700, Xing, Cedric wrote:
> > As said in my previous email, this vDSO API isn't even compliant to
> > x86_64 ABI and is absolutely NOT for average developers. Instead,
> > host/enclave communication
On Mon, Mar 25, 2019 at 4:45 PM Christian Brauner wrote:
>
> On Mon, Mar 25, 2019 at 04:42:14PM -0700, Andy Lutomirski wrote:
> > On Mon, Mar 25, 2019 at 1:23 PM Daniel Colascione wrote:
> > >
> > > On Mon, Mar 25, 2019 at 1:14 PM Jann Horn wrote:
> > > >
> > > > On Mon, Mar 25, 2019 at 8:44 PM
On Mon, 25 Mar 2019, Liang, Kan wrote:
> On 3/23/2019 5:56 AM, Peter Zijlstra wrote:
> > On Fri, Mar 22, 2019 at 10:22:50AM -0700, Andi Kleen wrote:
> > > > > diff --git a/arch/x86/include/uapi/asm/perf_regs.h
> > > > > b/arch/x86/include/uapi/asm/perf_regs.h
> > > > > index f3329cabce5c..b33995313
On Mon, 25 Mar 2019 23:34:28 +
Parav Pandit wrote:
> > -Original Message-
> > From: Alex Williamson
> > Sent: Monday, March 25, 2019 6:19 PM
> > To: Parav Pandit
> > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org;
> > kwankh...@nvidia.com
> > Subject: Re: [PATCH 8/8] vfio/md
Many kernel interfaces require real and/or effective root uid instead
of relying solely of capabilities. An executable that uses such
interfaces has to be set-uid-root or be executed by a thread with
effective root uid. Presently, fsuid and saved uid will reset to the
effective uid during execve. A
On Fri, 22 Mar 2019, kan.li...@linux.intel.com wrote:
>
> + PERF_REG_X86_XMM15 = 62,
> +
> + /* All registers include the XMMX registers */
> + PERF_REG_X86_MAX = PERF_REG_X86_XMM15 + 2,
Ergo: PERF_REG_X86_MAX == 64
> -#define REG_RESERVED (~((1ULL << PERF_REG_X86_MAX) - 1ULL))
> +#d
On Mon, Mar 25, 2019 at 05:00:17PM -0700, Andy Lutomirski wrote:
> On Mon, Mar 25, 2019 at 4:45 PM Christian Brauner
> wrote:
> >
> > On Mon, Mar 25, 2019 at 04:42:14PM -0700, Andy Lutomirski wrote:
> > > On Mon, Mar 25, 2019 at 1:23 PM Daniel Colascione
> > > wrote:
> > > >
> > > > On Mon, Mar
From: Ralph Campbell
valid_phys_addr_range() is used to sanity check the physical address range
of an operation, e.g., access to /dev/mem. It uses __pa(high_memory)
internally.
If memory is populated at the end of the physical address space, then
__pa(high_memory) is outside of the physical addr
From: Ralph Campbell
I was debugging with v5.1.0-rc1 and while booting I hit a
kernel BUG at arch/x86/mm/physaddr.c:27
which I fixed with the following patch but now I can't seem
to reproduce the exact setup that triggered it.
Still, it seems like a valid problem and maybe my difficulty
in reprod
On Mon, Mar 25, 2019 at 04:44:40PM -0700, Alexei Starovoitov wrote:
> On Mon, Mar 25, 2019 at 11:37:32PM +, Al Viro wrote:
> >
> > For debugfs it's clearly "use default ->evict_inode(), have explicit
> > ->destroy_inode() using free_inode_nonrcu()" - there we have nothing
> > else done in ->ev
On Mon, Mar 25, 2019 at 5:12 PM Christian Brauner wrote:
>
> On Mon, Mar 25, 2019 at 05:00:17PM -0700, Andy Lutomirski wrote:
> > On Mon, Mar 25, 2019 at 4:45 PM Christian Brauner
> > wrote:
> > >
> > > On Mon, Mar 25, 2019 at 04:42:14PM -0700, Andy Lutomirski wrote:
> > > > On Mon, Mar 25, 2019
On Mon, Mar 25, 2019 at 03:09:52PM -0700, Matthew Garrett wrote:
> 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
On Mon, Mar 25, 2019 at 5:35 PM Greg Kroah-Hartman
wrote:
> On Mon, Mar 25, 2019 at 03:09:52PM -0700, Matthew Garrett wrote:
> > Normal device interaction should be done through configfs, sysfs or a
> > miscdev, not debugfs.
>
> Then why not just not allow debugfs at all if it is such a "big
> pro
>So on user space to kernel space transitions swapping in kernel GS should
>simply do:
> userGS = RDGSBASE()
> WRGSBASE(kernelGS)
This would also need to find kernelGS first, by doing RDPID and then
reading it from memory in the right index
(which might be a full cache miss if y
On Fri, Mar 15, 2019 at 1:07 PM Chang S. Bae wrote:
>
> Updates from v5 [5]:
> * Drop the new tain flag (TAINT_INSECURE)
> * Cleanup copy_thread_tls(), some changelog, and unnecessary comments on
> assembly macros
> * Rearrange some helper updates appropriately (from patch 4 to 6)
I think this
On Mon, Mar 25, 2019 at 12:50:40PM -0500, Alan Tull wrote:
> On Sun, Mar 24, 2019 at 10:23 PM Wu Hao wrote:
>
> Hi Hao,
>
> Looks good, one question below.
>
> >
> > Current driver checks if input bitstream file size is aligned or
> > not per PR data width (default 32bits). It requires one addi
On Mon, Mar 25, 2019 at 05:38:09PM -0700, Matthew Garrett wrote:
> On Mon, Mar 25, 2019 at 5:35 PM Greg Kroah-Hartman
> wrote:
> > On Mon, Mar 25, 2019 at 03:09:52PM -0700, Matthew Garrett wrote:
> > > Normal device interaction should be done through configfs, sysfs or a
> > > miscdev, not debugfs
Currently kernel/bpf/cgroup.c contains only one program type and one
proto function cgroup_dev_func_proto(). It'd be useful to have base
proto function that can be reused for new cgroup-bpf program types
coming soon.
Introduce cgroup_base_func_proto().
Signed-off-by: Andrey Ignatov
---
kernel/b
On 3/25/19 5:27 PM, shenghui wrote:
On 3/26/19 1:06 AM, Bart Van Assche wrote:
On Mon, 2019-03-25 at 17:45 +0800, shenghui wrote:
[ 47.103637] vboxdrv: loading out-of-tree module taints kernel.
[ 47.111919] vboxdrv: Found 2 processor cores
[ 47.119013] vboxdrv: fAsync=0 offMin=0x2ee offMa
Hi, Rob
Best Regards!
Anson Huang
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: 2019年3月26日 4:42
> To: Anson Huang
> Cc: thierry.red...@gmail.com; mark.rutl...@arm.com;
> shawn...@kernel.org; s.ha...@pengutronix.de; ker...@pengutronix.de;
> feste...@gmail.com;
On 2019年03月25日 16:30, Thomas Gleixner wrote:
On Mon, 25 Mar 2019, Zhao, Yakui wrote:
-Original Message-
From: Thomas Gleixner [mailto:t...@linutronix.de]
Sent: Saturday, March 23, 2019 12:02 AM
To: Zhao, Yakui
Cc: linux-kernel@vger.kernel.org; x...@kernel.org; Chen, Jason CJ
Subje
On 2019年03月25日 16:27, Thomas Gleixner wrote:
On Mon, 25 Mar 2019, Zhao, Yakui wrote:
+/* SPDX-License-Identifier: GPL-2.0 */ #ifndef _ASM_X86_ACRNHYPER_H
+#define _ASM_X86_ACRNHYPER_H
+
+#include
+#include
+
+#ifdef CONFIG_ACRN
+/* ACRN Hypervisor callback */
+void acrn_hv_callback_vector(v
On Fri, Mar 22, 2019 at 04:43:53PM +0100, Arnd Bergmann wrote:
> From: Ravindra Lokhande
>
> Compress offload does not support ioctl calls from a 32bit userspace
> in a 64 bit kernel. This patch adds support for ioctls from a 32bit
> userspace in a 64bit kernel
>
> Signed-off-by: Ravindra Lokhan
On Fri, Mar 22, 2019 at 04:43:52PM +0100, Arnd Bergmann wrote:
> From: Julia Lawall
>
> The mmc_pwrseq_ops structures are never modified, so declare them as const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
> Signed-off-by: Ulf Hansson
> (cherry picked from commit f
On Fri, Mar 22, 2019 at 04:44:10PM +0100, Arnd Bergmann wrote:
> From: Wei Qiao
>
> SPRD_TIMEOUT was 256, which is too small to wait until the status
> switched to workable in a while loop, so that the earlycon could
> not work correctly.
>
> Signed-off-by: Wei Qiao
> Signed-off-by: Chunyan Zha
On Fri, Mar 22, 2019 at 04:43:55PM +0100, Arnd Bergmann wrote:
> From: Josh Boyer
>
> The iowarrior driver expects at least one valid endpoint. If given
> malicious descriptors that specify 0 for the number of endpoints,
> it will crash in the probe function. Ensure there is at least
> one endp
On Fri, Mar 22, 2019 at 04:44:08PM +0100, Arnd Bergmann wrote:
> From: Ziyuan Xu
>
> Per spec, block size should always be 512 bytes for dual rate mode,
> so any attempts to switch the block size under dual rate mode should
> be neglected.
>
> Signed-off-by: Ziyuan Xu
> Signed-off-by: Shawn Lin
On Fri, Mar 22, 2019 at 04:44:11PM +0100, Arnd Bergmann wrote:
> From: Al Viro
>
> It's not hard to trigger a bunch of d_invalidate() on the same
> dentry in parallel. They end up fighting each other - any
> dentry picked for removal by one will be skipped by the rest
> and we'll go for the next
On Mon, Mar 25, 2019 at 09:59:31AM -0700, Mark Salyzyn wrote:
On 03/25/2019 05:16 AM, Fengguang Wu wrote:
Martin,
On Fri, Mar 22, 2019 at 11:46:11PM +0800, Martin Liu wrote:
As the discussion https://lore.kernel.org/patchwork/patch/334982/
We know an open file's ra_pages might run out of sync
On Fri, Mar 22, 2019 at 04:44:12PM +0100, Arnd Bergmann wrote:
> From: Qiao Zhou
>
> In current die(), the irq is disabled for __die() handle, not
> including the possible panic() handling. Since the log in __die()
> can take several hundreds ms, new irq might come and interrupt
> current die().
On Fri, Mar 22, 2019 at 04:44:14PM +0100, Arnd Bergmann wrote:
> From: Lanqing Liu
>
> On Spreadtrum's serial device, nearly all of interrupts would be cleared
> by hardware except timeout interrupt. This patch removed the operation
> of clearing all interrupt in irq handler, instead added an if
On Sun, 23 Sep 2018 12:11:33 +
YueHaibing wrote:
> 'cnt' should be used to calculate ring buffer size rather than data->cnt
I just found this patch in my inbox (was traveling at the time. But now
I have patchwork attached to my INBOX so patches like these shouldn't
be missed anymore!)
Yes,
On Fri, Mar 22, 2019 at 04:44:15PM +0100, Arnd Bergmann wrote:
> From: Peter Zijlstra
>
> The current int_sqrt() computation is sub-optimal for the case of small
> @x. Which is the interesting case when we're going to do cumulative
> distribution functions on idle times, which we assume to be a
free the symlink body after the same RCU delay we have for freeing the
struct inode itself, so that traversal during RCU pathwalk wouldn't step
into freed memory.
Signed-off-by: Al Viro
---
diff --git a/fs/ceph/inode.c b/fs/ceph/inode.c
index e3346628efe2..2d61ddda9bf5 100644
--- a/fs/ceph/inode.
free the symlink body after the same RCU delay we have for freeing the
struct inode itself, so that traversal during RCU pathwalk wouldn't step
into freed memory.
Signed-off-by: Al Viro
---
diff --git a/fs/jffs2/readinode.c b/fs/jffs2/readinode.c
index 389ea53ea487..bccfc40b3a74 100644
--- a/fs
In this patchset, I introduce a new macro TRACE_EVENT_NONE(), which will
define a tracepoint as a do-nothing inline function.
#define TRACE_EVENT_NONE(name, proto) \
static inline void trace_##name(proto) \
{ }
Sometimes we want define a tracepoint as a do-nothing function.
So I introduce this TRACE_EVENT_NONE() for this kind of usage.
Signed-off-by: Yafang Shao
---
include/linux/tracepoint.h | 8
include/trace/define_trace.h | 4
2 files changed, 12 insertions(+)
diff --git a/include/
901 - 1000 of 1175 matches
Mail list logo
