On Tue, Apr 3, 2018 at 11:14 AM, Omar Sandoval wrote:
> Just wanted to make sure this doesn't get missed because I misspelled
> the stable email address in the patch. It applies to v4.13+.
The "sta...@kernel.org" address for a stable cc is actually better
than stable@vger" imho, because afaik it
On Mon, Apr 02, 2018 at 04:23:35PM +0100, Mark Brown wrote:
> I only seem to have patches 1 and 2 here (and they aren't threaded with
> each other which is a bit odd too). I seem to recall this has been
> happening quite a bit with your patches - in general if you're sending
> things you should al
On Tue, Apr 03, 2018 at 09:37:06AM +0200, Peter Zijlstra wrote:
> On Mon, Apr 02, 2018 at 04:24:49PM -0700, Luck, Tony wrote:
> > Any guesses before I start to bisect?
>
> That doesn't sound good. The only guess I have at this moment is you
> accidentially enabled RANDSTRUCT_PLUGIN and that messes
On Tue, Apr 03, 2018 at 08:07:11PM +0200, Lukas Wunner wrote:
> On Tue, Apr 03, 2018 at 10:33:25AM +0200, Hans de Goede wrote:
> > I asked Peter Jones for suggestions how to extract this during boot and
> > he suggested seeing if there was a copy of the firmware in the
> > EFI_BOOT_SERVICES_CODE me
On Mon, Apr 2, 2018 at 9:34 AM, Mark Brown wrote:
>
> A very small set of updates for the regulator API this time around,
> there's a few bug fixes and also:
Heh. This one was "very small", and the regmap update was "fairly large".
I think the regmap one was smaller. This one actually has a new
On Tue, Apr 3, 2018 at 11:45 AM, Kees Cook wrote:
> On Tue, Apr 3, 2018 at 9:45 AM, Andy Lutomirski wrote:
>> On Tue, Apr 3, 2018 at 9:29 AM, Matthew Garrett wrote:
>>> On Tue, Apr 3, 2018 at 8:11 AM Andy Lutomirski wrote:
Can you explain that much more clearly? I'm asking why booting via
> On Apr 3, 2018, at 10:16 AM, David Howells wrote:
>
> Andy Lutomirski wrote:
>
>>> A kernel that allows users arbitrary access to ring 0 is just an
>>> overfeatured bootloader. Why would you want secure boot in that case?
>>
>> To get a chain of trust.
>
> You don't have a chain of trust that y
This patch leads to errors "space prohibited before open square
bracket '['" for the asm statement.
In the inline assembler statement the bracket is not used for an index.
Adding a space after a colon or a comma should be allowable.
Signed-off-by: Heinrich Schuchardt
---
foo.c | 11 +++
Hi all,
this series adds support for the Lattice MachXO2 FPGA chip, programmed
over slave SPI.
Tested on a raspberry pi3, beaglebone black (little endian mode) and imx6
hummingboard (big endian mode) + bugblat's pif2 fpga hat (machxo2 7000HC) or
tinyfpga A1/A2 (machxo2 256HC / 1200HC), in SPI slav
This patch adds support to the FPGA manager for programming
MachXO2 device’s internal flash memory, via slave SPI.
Signed-off-by: Paolo Pisati
---
drivers/fpga/Kconfig | 7 +
drivers/fpga/Makefile | 1 +
drivers/fpga/machxo2-spi.c | 413
Add dt binding documentation details for Lattice MachXO2 FPGA configuration
over Slave SPI interface.
Signed-off-by: Paolo Pisati
Acked-by: Rob Herring
Acked-by: Moritz Fischer
Acked-by: Alan Tull
---
.../bindings/fpga/lattice-machxo2-spi.txt | 29 ++
1 file chang
On Tue, Apr 3, 2018 at 11:27 AM, Michael S. Tsirkin wrote:
> On Tue, Apr 03, 2018 at 10:32:00AM -0700, Alexander Duyck wrote:
>> On Tue, Apr 3, 2018 at 6:12 AM, Michael S. Tsirkin wrote:
>> > On Fri, Mar 16, 2018 at 09:40:34AM -0700, Alexander Duyck wrote:
>> >> On Fri, Mar 16, 2018 at 9:34 AM, M
On Sun, Apr 01, 2018 at 07:56:55PM +0100, Ben Hutchings wrote:
> On Mon, 2018-03-19 at 19:06 +0100, Greg Kroah-Hartman wrote:
> > 4.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: "Luis R. Rodriguez"
> >
> >
> > [ Upstream comm
On Tue, Apr 03, 2018 at 03:31:15PM +0200, Michal Hocko wrote:
> On Mon 02-04-18 09:24:22, Buddy Lumpkin wrote:
> > The presence of direct reclaims 10 years ago was a fairly reliable
> > indicator that too much was being asked of a Linux system. Kswapd was
> > likely wasting time scanning pages that
On 01/04/2018 03:41, Finn Thain wrote:
> This patch series has fixes for bugs in the SWIM floppy disk controller
> driver, including an oops and a soft lockup.
>
> There are also patches to add support for SWIM devices connected to IOPs.
>
> Geert, would you please take this series through the m6
On Tue, Apr 3, 2018 at 12:01 PM, Andy Lutomirski wrote:
> On Tue, Apr 3, 2018 at 11:45 AM, Kees Cook wrote:
>> On Tue, Apr 3, 2018 at 9:45 AM, Andy Lutomirski wrote:
>>> On Tue, Apr 3, 2018 at 9:29 AM, Matthew Garrett wrote:
On Tue, Apr 3, 2018 at 8:11 AM Andy Lutomirski wrote:
> Can
On Tue, Mar 13, 2018 at 06:59:36PM +0100, Laurent Dufour wrote:
> pte_unmap_same() is making the assumption that the page table are still
> around because the mmap_sem is held.
> This is no more the case when running a speculative page fault and
> additional check must be made to ensure that the fi
Hi Linus,
Please pull LED updates for 4.17-rc1:
New LED class driver:
- add driver for Mellanox regmap LEDs
Improvement to ledtrig-activity:
- extend disk trigger for reads and writes
Improvements and fixes to existing LED class drivers:
- add more product/board names for PC Engines APU2
2018-04-02 18:10+0200, Vitaly Kuznetsov:
> Implement HvFlushVirtualAddress{List,Space} hypercalls in a simplistic way:
> do full TLB flush with KVM_REQ_TLB_FLUSH and rely on kvm_vcpu_kick()
> kicking only vCPUs which are currently IN_GUEST_MODE.
>
> Signed-off-by: Vitaly Kuznetsov
> ---
> arch/x
On 04/03/2018 09:09 PM, Jacek Anaszewski wrote:
> Hi Linus,
>
> Please pull LED updates for 4.17-rc1:
>
> New LED class driver:
> - add driver for Mellanox regmap LEDs
>
> Improvement to ledtrig-activity:
It should be of course: "Improvement to ledtrig-disk".
> - extend disk trigger for re
Linus,
Please pull the userns-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
userns-linus
HEAD: 2236d4d39035b9839944603ec4b65ce71180a9ea ipc/shm: Fix pid freeing.
There was a lot of work this cycle fixing bugs that were discover
Allow a space between a colon and subsequent opening bracket.
This sequence may occur in inline assembler statements like
asm(
"ldr %[out], [%[in]]\n\t"
: [out] "=r" (ret)
: [in] "r" (addr)
);
Signed-off-by: Heinrich Schuchardt
---
Hi Dimitry,
I reapplied the 3 commits I had to revert earlier and applied your patch. Have
correct battery level reading on my BT mouse back!
/sys/class/power_supply/hid-00:1f:20:fd:cb:be-battery# grep "" *
capacity:53
grep: device: Is a directory
model_name:Bluetooth Mouse M336/M337/M535
online
On Apr 3, 2018, at 11:27 AM, Michael S. Tsirkin wrote:
I'm not sure why you would need a feature bit. The capability is
controlled via PCI configuration space. If it is present the device
has the capability. If it is not then it does not.
Basically if the PCI configuration space is not present
Em Wed, Mar 28, 2018 at 03:26:31PM +0800, Du, Changbin escreveu:
> Hi Arnaldo,
> Just a kind reminder. Hope you didn't forget this.
Ok, applied.
- Arnaldo
> On Fri, Mar 16, 2018 at 09:50:45AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Mar 16, 2018 at 03:51:09PM +0800, Du, Changbin escre
Am Mon, 2 Apr 2018 08:34:35 -0400
schrieb Jason Andryuk :
> The HP EliteBook G3 850 has a weird bug where a subsequent cold boot
> hangs while plugged in if Linux enables the Host Notify features of
> i2c-i801. The cold boot hang depends on how the system boots. It
> does not hang on UEFI Grub
Hi Linus,
please pull the updates regarding the parisc architecture for kernel 4.17 from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-4.17-1
Lots of small enhancements and fixes in this patchset:
- improved the x86-64 compatibility for PCI cards by returning -
2018-03-30 02:06-0700, Wanpeng Li:
> From: Wanpeng Li
>
> There is no easy way to force KVM to run an instruction through the emulator
> (by design as that will expose the x86 emulator as a significant
> attack-surface).
> However, we do wish to expose the x86 emulator in case we are testing it
On 4/3/18 1:16 PM, Kirill Marinushkin wrote:
On 04/03/18 19:21, Pierre-Louis Bossart wrote:
On 04/03/2018 12:15 AM, Kirill Marinushkin wrote:
On 04/03/18 02:57, Pierre-Louis Bossart wrote:
On 04/02/2018 04:17 PM, Kirill Marinushkin wrote:
Hello Pierre-Louis,
I explicitly clarified with Ta
On Tue, Apr 3, 2018 at 9:46 AM Andy Lutomirski wrote:
> On Tue, Apr 3, 2018 at 9:29 AM, Matthew Garrett wrote:
> > A kernel that allows users arbitrary access to ring 0 is just an
> > overfeatured bootloader. Why would you want secure boot in that case?
> To get a chain of trust. I can provisio
From: Michal Hocko
David has noticed that THP memcg charge can trigger the oom killer
since 2516035499b9 ("mm, thp: remove __GFP_NORETRY from khugepaged and
madvised allocations"). We have used an explicit __GFP_NORETRY
previously which ruled the OOM killer automagically.
Memcg charge path shoul
On Tue, Apr 03, 2018 at 04:23:07PM +0100, David Howells wrote:
> Andrea Parri wrote:
>
> > Sorry, but I don't understand your objection: are you suggesting to add
> > something like "Always return 0 on !SMP" to the comment? what else?
>
> Something like that, possibly along with a warning that
On Fri, Mar 30, 2018 at 10:38:58AM -0500, Gustavo A. R. Silva wrote:
> Check on return values and goto label mbx_err are unnecessary.
>
> Addresses-Coverity-ID: 1271151 ("Identical code for different branches")
> Addresses-Coverity-ID: 1268788 ("Identical code for different branches")
> Signed-off
On Tue, Apr 03 2018 at 2:24pm -0400,
Dan Williams wrote:
> On Fri, Mar 30, 2018 at 9:03 PM, Dan Williams
> wrote:
> > In preparation for allowing filesystems to augment the dev_pagemap
> > associated with a dax_device, add an ->fs_claim() callback. The
> > ->fs_claim() callback is leveraged by
On Tue, Mar 13, 2018 at 06:59:45PM +0100, Laurent Dufour wrote:
> When dealing with the speculative fault path we should use the VMA's field
> cached value stored in the vm_fault structure.
>
> Currently vm_normal_page() is using the pointer to the VMA to fetch the
> vm_flags value. This patch pro
While debugging an issue I needed to see if the pointers were being
processed correctly with trace_printk() and after using "%p" and
triggering my bug and trace output, I was disappointed that all my
pointers were random garbage and didn't produce anything useful for me.
I had to rewrite all the tr
[The subject could mention "x86:" as well]
2018-04-01 17:54+0200, Stefan Fritsch:
> This is very similar to the aligned versions movaps/movapd.
>
> We have seen the corresponding emulation failures with openbsd as guest
> and with Windows 10 with intel HD graphics pass through.
>
> Signed-off-by
* Pavel Machek [180403 15:51]:
> Hi!
>
> > > OK thanks for checking. So probably only n_gsm channel 1 is for normal
> > > Qualcomm at commands, and then channel 2 and others are commands
> > > implemented by Motorola on the mdm6600.
> > >
> > > I guess we'd have to add support for reading and wr
On Tue, Apr 3, 2018 at 12:39 PM, Mike Snitzer wrote:
> On Tue, Apr 03 2018 at 2:24pm -0400,
> Dan Williams wrote:
>
>> On Fri, Mar 30, 2018 at 9:03 PM, Dan Williams
>> wrote:
>> > In preparation for allowing filesystems to augment the dev_pagemap
>> > associated with a dax_device, add an ->fs_
Hi Matt,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.16 next-20180403]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Andy Lutomirski wrote:
> >>> A kernel that allows users arbitrary access to ring 0 is just an
> >>> overfeatured bootloader. Why would you want secure boot in that case?
> >>
> >> To get a chain of trust.
> >
> > You don't have a chain of trust that you can trust in that case.
> >
> Please elabor
Hello,
On Tue, 3 Apr 2018 17:07:06 +0800
Chen-Yu Tsai wrote:
> On Tue, Apr 3, 2018 at 2:18 PM, Mylène Josserand
> wrote:
> > The R_CPUCFG is a collection of registers needed for SMP bringup
> > on clusters and cluster's reset.
> > For the moment, documentation about this register is found in
>
Hi Steve, did you get a chance to take a look? cc'ing myself and a
personal email. When I sent the patchset I forgot to include.
Tianyang
On 2018-03-26 04:08 PM, Tim Tianyang Chen wrote:
This patch set will let users define a mailer, an email address and when to
receive
notifications during
On Sat, Mar 31, 2018 at 02:19:44PM +0200, Hans de Goede wrote:
> diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
> index fddc5f706fd2..1a5ea950f58f 100644
> --- a/drivers/firmware/efi/efi.c
> +++ b/drivers/firmware/efi/efi.c
> @@ -455,6 +455,7 @@ int __init efi_mem_desc_lookup(
On 2018-03-26 04:08 PM, Tim Tianyang Chen wrote:
> This patch set will let users define a mailer, an email address and when to
> receive
> notifications during automated testings. Users need to setup the specified
> mailer
> prior to using this feature.
>
> Tim Tianyang Chen (4):
> Ktest: add
On Tue, Apr 3, 2018 at 12:48 PM, Ben Hutchings
wrote:
> Commit 65c79230576 tried to clear the custom firmware path on exit by
> writing a single space to the firmware_class.path parameter. This
> doesn't work because nothing strips this space from the value stored
> and fw_get_filesystem_firmware
On 04/02/2018 11:52 PM, Chen-Yu Tsai wrote:
> On Tue, Apr 3, 2018 at 2:18 PM, Mylène Josserand
> wrote:
>> To add the support for SMP on sun8i-a83t, we will use some
>> definitions in an assembly file so move definitions into
>> another file to separate C functions and macro defintions.
>
> Inste
Add standard interrupt handler annotations to
hyperv_vector_handler().
Signed-off-by: Michael Kelley
---
arch/x86/kernel/cpu/mshyperv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x86/kernel/cpu/mshyperv.c
index 4488cf0..20f6849 10064
On Tue, Apr 03, 2018 at 07:42:28AM +, Kalderon, Michal wrote:
> > From: Sinan Kaya [mailto:ok...@codeaurora.org]
> > Sent: Tuesday, April 03, 2018 5:30 AM
> > To: linux-r...@vger.kernel.org; ti...@codeaurora.org;
> > sulr...@codeaurora.org
> > Cc: linux-arm-...@vger.kernel.org; linux-arm-ker...
On Tue, 3 Apr 2018, Andrea Parri wrote:
> On Tue, Apr 03, 2018 at 04:23:07PM +0100, David Howells wrote:
> > Andrea Parri wrote:
> >
> > > Sorry, but I don't understand your objection: are you suggesting to add
> > > something like "Always return 0 on !SMP" to the comment? what else?
> >
> > S
Hello,
Thank you for the review.
On Tue, 3 Apr 2018 11:12:18 +0200
Maxime Ripard wrote:
> On Tue, Apr 03, 2018 at 08:18:31AM +0200, Mylène Josserand wrote:
> > Add the initialization of CNTVOFF for sun8i-a83t.
> >
> > For boot CPU, Create a new machine that handles this
> > function's call in
On Tue, Apr 3, 2018 at 12:41 PM, Steven Rostedt wrote:
> Both trace_debug is set and kptr_restrict is set to zero in the same
> code that produces the above banner. This will allow trace_printk() to
> not be affected by security code, as trace_printk() should never be run
> on a machine that needs
Hi,
On Tue, 3 Apr 2018 16:48:41 +0800
Chen-Yu Tsai wrote:
> On Tue, Apr 3, 2018 at 4:46 PM, Maxime Ripard
> wrote:
> > On Tue, Apr 03, 2018 at 08:18:34AM +0200, Mylène Josserand wrote:
> >> To prepare the support of sun8i-a83t, add a field in the smp_data
> >> structure to enable the case of
Add null checks on lookup_tid() return value in order to prevent
null pointer dereferences.
Addresses-Coverity-ID: 1467422 ("Dereference null return value")
Addresses-Coverity-ID: 1467443 ("Dereference null return value")
Addresses-Coverity-ID: 1467445 ("Dereference null return value")
Addresses-C
On Tue, Apr 03, 2018 at 12:57:35PM -0700, Michael Kelley wrote:
> Add standard interrupt handler annotations to
> hyperv_vector_handler().
>
> Signed-off-by: Michael Kelley
Does not match the From: line :(
On Tue, 2018-04-03 at 12:54 -0700, Luis R. Rodriguez wrote:
> On Tue, Apr 3, 2018 at 12:48 PM, Ben Hutchings
> > wrote:
> > Commit 65c79230576 tried to clear the custom firmware path on exit by
> > writing a single space to the firmware_class.path parameter. This
> > doesn't work because nothing
On Tue, Apr 3, 2018 at 1:10 PM, Ben Hutchings
wrote:
> On Tue, 2018-04-03 at 12:54 -0700, Luis R. Rodriguez wrote:
>> On Tue, Apr 3, 2018 at 12:48 PM, Ben Hutchings
>> > wrote:
>> > Commit 65c79230576 tried to clear the custom firmware path on exit by
>> > writing a single space to the firmware_c
Very sorry, I forgot to send my last response as plain text.
> On Apr 3, 2018, at 6:31 AM, Michal Hocko wrote:
>
> On Mon 02-04-18 09:24:22, Buddy Lumpkin wrote:
>> Page replacement is handled in the Linux Kernel in one of two ways:
>>
>> 1) Asynchronously via kswapd
>> 2) Synchronously, via di
... chop chop removing unneeded recipients
Arnd Bergmann writes:
> Ok, I looked at the driver in more detail now and found the scary parts.
> So it's using the async DMA interface to do synchronous DMA in
> interrupt context in order to transfer the rx data faster than an readsl()
> would,
Hello Chen-Yu,
Thanks for your review.
On Tue, 3 Apr 2018 16:47:53 +0800
Chen-Yu Tsai wrote:
> On Tue, Apr 3, 2018 at 2:18 PM, Mylène Josserand
> wrote:
> > Add the support for A83T.
> >
> > A83T SoC has an additional register than A80 to handle CPU configurations:
> > R_CPUS_CFG. Information
- On Apr 3, 2018, at 12:36 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Apr 2, 2018, at 11:33 AM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
>
>> - On Apr 1, 2018, at 12:13 PM, One Thousand Gnomes
>> gno...@lxorguk.ukuu.org.uk wrote:
>>
[...]
>>>
Hi Matt,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.16 next-20180403]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Tue, Mar 13, 2018 at 06:59:30PM +0100, Laurent Dufour wrote:
> This is a port on kernel 4.16 of the work done by Peter Zijlstra to
> handle page fault without holding the mm semaphore [1].
>
> The idea is to try to handle user space page faults without holding the
> mmap_sem. This should allow
On Tue, 3 Apr 2018, Jerome Glisse wrote:
> > diff --git a/mm/memory.c b/mm/memory.c
> > index 21b1212a0892..4bc7b0bdcb40 100644
> > --- a/mm/memory.c
> > +++ b/mm/memory.c
> > @@ -2309,21 +2309,29 @@ static bool pte_map_lock(struct vm_fault *vmf)
> > * parts, do_swap_page must check under lock b
On 04/03/2018 09:45 AM, Al Viro wrote:
> On Tue, Apr 03, 2018 at 12:33:05PM -0400, David Miller wrote:
>
>> Yes Al, however the pattern choosen here is probably cheaper on little
>> endian:
>>
>> __beXX val = x;
>> switch (val) {
>> case htons(ETH_P_FOO):
>> ...
>> }
>>
On Tue, 3 Apr 2018, Jerome Glisse wrote:
> > When dealing with the speculative fault path we should use the VMA's field
> > cached value stored in the vm_fault structure.
> >
> > Currently vm_normal_page() is using the pointer to the VMA to fetch the
> > vm_flags value. This patch provides a new
On Monday 02 April 2018 22:39:59 Ondrej Zary wrote:
> On Sunday 01 April 2018 23:21:55 Ondrej Zary wrote:
> > Hello,
> > I got a Sony Vaio VGN-CS31S laptop with Synaptics touchpad that exhibits
> > weird behavior. It seems to work until I touch the "Touch Sensor Buttons"
> > bar above the keyboard
On Fri, 2018-03-23 at 10:54 +0100, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Keerthy
>
>
> [ Upstream commit 85fdaf8eb9bbec1f0f8a52fd5d85659d60738816 ]
>
> POWERHOLD signal has higher priority over
> On Apr 3, 2018, at 12:07 PM, Matthew Wilcox wrote:
>
> On Tue, Apr 03, 2018 at 03:31:15PM +0200, Michal Hocko wrote:
>> On Mon 02-04-18 09:24:22, Buddy Lumpkin wrote:
>>> The presence of direct reclaims 10 years ago was a fairly reliable
>>> indicator that too much was being asked of a Linux s
On Tue, Apr 3, 2018 at 9:29 AM, Matthew Garrett wrote:
> On Tue, Apr 3, 2018 at 8:11 AM Andy Lutomirski wrote:
>> Can you explain that much more clearly? I'm asking why booting via
>> UEFI Secure Boot should enable lockdown, and I don't see what this has
>> to do with kexec. And "someone blackl
On Tue, Apr 3, 2018 at 1:53 PM Linus Torvalds
wrote:
> On Tue, Apr 3, 2018 at 9:29 AM, Matthew Garrett wrote:
> > On Tue, Apr 3, 2018 at 8:11 AM Andy Lutomirski wrote:
> >> Can you explain that much more clearly? I'm asking why booting via
> >> UEFI Secure Boot should enable lockdown, and I do
On Tue, Apr 03, 2018 at 10:22:53AM -0700, rao.sho...@oracle.com wrote:
> +++ b/mm/slab.h
> @@ -80,6 +80,29 @@ extern const struct kmalloc_info_struct {
> unsigned long size;
> } kmalloc_info[];
>
> +#define RCU_MAX_ACCUMULATE_SIZE 25
> +
> +struct rcu_bulk_free_container {
> + str
Hi Matt,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.16 next-20180403]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
From: Michael Kelley
Add standard interrupt handler annotations to
hyperv_vector_handler().
Signed-off-by: Michael Kelley
---
Changes in v2:
* Fixed From: line
---
arch/x86/kernel/cpu/mshyperv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/mshyperv.c
On Fri, 2018-03-23 at 10:54 +0100, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Ming Lei
>
>
> [ Upstream commit a4e84aae8139aca9fbfbced1f45c51ca81b57488 ]
>
> mtip32xx supposes that 'request_idx' pass
tcon->ses is being dereferenced before it is null checked, hence
there is a potential null pointer dereference.
Fix this by moving the pointer dereference after tcon->ses has
been properly null checked.
Addresses-Coverity-ID: 1467426 ("Dereference before null check")
Fixes: 93012bf98416 ("cifs: a
On Tue, Apr 3, 2018 at 1:54 PM, Matthew Garrett wrote:
>
>> .. maybe you don't *want* secure boot, but it's been pushed in your
>> face by people with an agenda?
>
> Then turn it off, or build a self-signed kernel that doesn't do this?
Umm. So you asked a question, and then when you got an answer
Hi,
I noticed the subject was incorrect. Drop this patch, please.
I just sent v2.
Thanks
--
Gustavo
On 04/03/2018 03:55 PM, Gustavo A. R. Silva wrote:
tcon->ses is being dereferenced before it is null checked, hence
there is a potential null pointer dereference.
Fix this by moving the pointe
On Tue, Apr 03, 2018 at 01:40:18PM -0700, David Rientjes wrote:
> On Tue, 3 Apr 2018, Jerome Glisse wrote:
>
> > > diff --git a/mm/memory.c b/mm/memory.c
> > > index 21b1212a0892..4bc7b0bdcb40 100644
> > > --- a/mm/memory.c
> > > +++ b/mm/memory.c
> > > @@ -2309,21 +2309,29 @@ static bool pte_map_
Hi Rui,
I love your patch! Yet something to improve:
[auto build test ERROR on v4.16]
[cannot apply to linuxtv-media/master next-20180403]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Rui
On Tue, 3 Apr 2018 13:07:58 -0700
Kees Cook wrote:
> On Tue, Apr 3, 2018 at 12:41 PM, Steven Rostedt wrote:
> > Both trace_debug is set and kptr_restrict is set to zero in the same
> > code that produces the above banner. This will allow trace_printk() to
> > not be affected by security code, as
On Tue, Apr 3, 2018 at 2:01 PM Linus Torvalds
wrote:
> On Tue, Apr 3, 2018 at 1:54 PM, Matthew Garrett wrote:
> >
> >> .. maybe you don't *want* secure boot, but it's been pushed in your
> >> face by people with an agenda?
> >
> > Then turn it off, or build a self-signed kernel that doesn't do t
new_range is being dereferenced before it is null checked, hence
there is a potential null pointer dereference.
Fix this by moving the pointer dereference after new_range has
been properly null checked.
Addresses-Coverity-ID: 1466163 ("Dereference before null check")
Fixes: 0a7198426259 ("lib: Ad
From: Alison Schofield
Intel's Skylake Server CPUs have a different LLC topology than previous
generations. When in Sub-NUMA-Clustering (SNC) mode, the package is
divided into two "slices", each containing half the cores, half the LLC,
and one memory controller and each slice is enumerated to Lin
On Tue, Apr 03, 2018 at 01:49:25PM -0700, Buddy Lumpkin wrote:
> > Yes, very much this. If you have a single-threaded workload which is
> > using the entirety of memory and would like to use even more, then it
> > makes sense to use as many CPUs as necessary getting memory out of its
> > way. If
new_range is being dereferenced before it is null checked, hence
there is a potential null pointer dereference.
Fix this by moving the pointer dereference after new_range has
been properly null checked.
Addresses-Coverity-ID: 1466163 ("Dereference before null check")
Fixes: 0a7198426259 ("lib: Ad
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git tags/audit-pr-
20180403
for you to fetch changes up to ea841bafda3f7f9aa8b06a09f0f3e41c207af84f:
audit: add refused symlink to audit_names (2018-
Split section "Comparison with old cropping API" in paragraphs for
easier reading and improve visible links text.
Cc: Hans Verkuil
Signed-off-by: Luca Ceresoli
---
.../media/uapi/v4l/selection-api-vs-crop-api.rst | 55 --
1 file changed, 29 insertions(+), 26 deletions(-)
Having two somewhat similar and largely overlapping APIs is confusing,
especially since the older one appears in the docs before the newer
and most featureful counterpart.
Clarify all of this in several ways:
- swap the two sections
- give a name to the two APIs in the section names
- add a not
Cc: Hans Verkuil
Signed-off-by: Luca Ceresoli
---
Documentation/media/uapi/v4l/selection-api-004.rst | 2 +-
Documentation/media/uapi/v4l/selection.svg | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/media/uapi/v4l/selection-api-004.rst
b/Documenta
The API limitation described here is about the CROP API, not about the
entire V4L2.
Cc: Hans Verkuil
Signed-off-by: Luca Ceresoli
---
Documentation/media/uapi/v4l/selection-api-vs-crop-api.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/media/uapi/v4l/selec
These files have an automatically-generated numbering. Replaname them
to something that suggests their meaning.
Reported-by: Hans Verkuil
Cc: Hans Verkuil
Signed-off-by: Luca Ceresoli
---
.../{selection-api-004.rst => selection-api-configuration.rst} | 0
.../v4l/{selection-api-006.rst => sel
On Tue, 2018-04-03 at 21:16 +0200, Heinrich Schuchardt wrote:
> Allow a space between a colon and subsequent opening bracket.
> This sequence may occur in inline assembler statements like
>
> asm(
> "ldr %[out], [%[in]]\n\t"
> : [out] "=r" (ret)
> :
On Tue, Apr 03, 2018 at 09:08:54PM +, Matthew Garrett wrote:
> > The fact is, some hardware pushes secure boot pretty hard. That has
> > *nothing* to do with some "lockdown" mode.
>
> Secure Boot ensures that the firmware will only load signed bootloaders. If
> a signed bootloader loads a ker
tcon->ses is being dereferenced before it is null checked, hence
there is a potential null pointer dereference.
Fix this by moving the pointer dereference after tcon->ses has
been properly null checked.
Addresses-Coverity-ID: 1467426 ("Dereference before null check")
Fixes: 93012bf98416 ("cifs: a
On Tue, Apr 3, 2018 at 2:08 PM, Matthew Garrett wrote:
>
> Secure Boot ensures that the firmware will only load signed bootloaders. If
> a signed bootloader loads a kernel that's effectively an unsigned
> bootloader, there's no point in using Secure Boot
Bullshit.
I may want to know that I'm run
Add null check on kmalloc() return value in order to prevent
a null pointer dereference.
Addresses-Coverity-ID: 1467429 ("Dereference null return value")
Fixes: 37c3347eb247 ("net: thunderx: add ndo_set_rx_mode callback
implementation for VF")
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/
From: Steven Rostedt (VMware)
While debugging an issue I needed to see if the pointers were being
processed correctly with trace_printk() and after using "%p" and
triggering my bug and trace output, I was disappointed that all my
pointers were random garbage and didn't produce anything useful for
On Fri, 2018-03-23 at 10:54 +0100, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Shaohua Li
>
>
> [ Upstream commit b506335e5d2b4ec687dde392a3bdbf7601778f1d ]
>
> Commit 6f287ca(md/raid10: reset the 'fi
On Tue, Apr 3, 2018 at 2:26 PM Linus Torvalds
wrote:
> On Tue, Apr 3, 2018 at 2:08 PM, Matthew Garrett wrote:
> >
> > Secure Boot ensures that the firmware will only load signed
bootloaders. If
> > a signed bootloader loads a kernel that's effectively an unsigned
> > bootloader, there's no point
501 - 600 of 918 matches
Mail list logo
