> -Original Message-
> From: Marco Martin [mailto:notm...@gmail.com]
> Sent: Thursday, February 22, 2018 9:16 AM
> To: Jeremy Cline
> Cc: Limonciello, Mario ; Pali Rohár
> ; Andy Shevchenko ;
> Matthew Garrett ; Darren Hart ;
> Platform Driver ; Linux Kernel Mailing
> List
>
> Subject: R
On Thu, Feb 22, 2018 at 08:51:30AM -0600, Shanker Donthineni wrote:
> +#define CTR_B31_SHIFT31
Since this is just a RES1 bit, I think we don't need a mnemonic for it,
but I'll defer to Will and Catalin on that.
> ENTRY(invalidate_icache_range)
> +#ifdef CONFIG_ARM64_SKIP_CACHE_PO
Add missing pin group uart5nocts (all pins except cts), which has been
supported by the artpec6 pinctrl driver since its initial submission.
Fixes: 00df0582eab1 ("pinctrl: Add pincontrol driver for ARTPEC-6 SoC")
Signed-off-by: Niklas Cassel
---
Documentation/devicetree/bindings/pinctrl/axis,art
Add group configuration for uarts that are cut down
variants, the standard being full, i.e. all signals,
flow control, i.e. rx/tx and cts/rts, and rx/tx only.
This allows us to be more precise in which pins we're
actually using.
Unfortunately the existing naming scheme leaves things
to be desired
> I have found one bug in v7. We were not able to initialize NOP
> struct klp_func when the patches module is not loaded. It was
> because func->new_func was NULL. I have fixed it in separate patch
> for an easier review.
This is embarassing. I'd swear I tested this. At least it was a part of my
On Wed, 21 Feb 2018, Petr Mladek wrote:
> From: Jason Baron
>
> We are going to add a feature called atomic replace. It will allow to
> create a patch that would replace all already registered patches.
> For this, we will need to dynamically create funcs and objects
> for functions that are no l
On Thu, 22 Feb 2018, Daniel Schultz wrote:
> The Rockchip PMIC driver can automatically detect connected component
> versions by reading the ID_MSB and ID_LSB registers. The probe function
> will always fail with RK818 PMICs because the ID_MSK is 0xFFF0 and the
> RK818 template ID is 0x8181.
>
>
On Thu, 22 Feb 2018 20:15:58 +0530
Shreeya Patel wrote:
> On Thu, 2018-02-22 at 15:30 +0100, Richard Weinberger wrote:
> > Am Donnerstag, 22. Februar 2018, 14:10:14 CET schrieb Shreeya Patel:
> > >
> > > @@ -438,7 +438,7 @@ static void __init doc2000_count_chips(struct
> > > mtd_info
> > > *mt
Hi
On 02/22/2018 03:03 PM, Herbert Xu wrote:
On Thu, Feb 15, 2018 at 02:03:07PM +0100, Lionel Debieve wrote:
This set of patches add extended functionalities for stm32 rng
driver.
Patch #1 includes a reset during probe to avoid any error status
which can occur during bootup process and keep saf
The log levels embedded with the name are more concise than
printk.
Replace printks having a log level with the appropriate
pr_*() macros.
Define pr_fmt() and remove other additional macros from
the replaced printks.
Signed-off-by: Shreeya Patel
---
Changes in v2
-Merge previous patches of the
On Mon, Feb 19, 2018 at 8:23 PM, Marc Zyngier wrote:
>> Am Montag, 19. Februar 2018, 19:03:27 CET schrieb Florian Fainelli:
>> > Can you indicate which DTS file is used for your Chromebook model? Sorry
>> > about the breakage.
>>
>> that should be
>> https://git.kernel.org/pub/scm/linux/kernel/g
On Thu, Feb 22, 2018 at 11:12:10PM +0800, Boqun Feng wrote:
> On Thu, Feb 22, 2018 at 03:26:14PM +0100, Peter Zijlstra wrote:
> > However, I would suggest:
> >
> > static inline bool is_xr(u16 dep)
> > {
> > return !!(dep & (DEP_NR_MASK | DEP_RR_MASK));
> > }
> >
> > static inline bool is_rx
On 02/22/2018 02:44 PM, Linus Walleij wrote:
> On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay
> wrote:
>
> Thanks for working on this complex expander driver.
> It is a bit daunting. Sorry if there are lots of comments and
> considerations, but it reflects the complexity of the hardware.
>
>
On Thu 22-02-18 18:13:11, Andrey Ryabinin wrote:
>
>
> On 02/22/2018 05:09 PM, Michal Hocko wrote:
> > On Thu 22-02-18 16:50:33, Andrey Ryabinin wrote:
> >> On 02/21/2018 11:17 PM, Andrew Morton wrote:
> >>> On Fri, 19 Jan 2018 16:11:18 +0100 Michal Hocko wrote:
> >>>
> And to be honest, I
On 02/22/2018 02:47 PM, Linus Walleij wrote:
> On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay
> wrote:
>
>> ST Multi-Function eXpander (MFX) can be used as GPIO expander.
>> It has 16 fast GPIOs and can have 8 extra alternate GPIOs
>> when other MFX features are not enabled.
>>
>> Signed-off-
On Mon, Feb 19, 2018 at 11:29 PM, David Lechner wrote:
> This makes use of the gpio-ranges feature that connects GPIO
> controllers and PINMUX controllers.
>
> In da850.dtsi, pinctrl-single,gpio-range is added to the pinmux node
> and gpio-ranges is added to the GPIO node. Unfortunately, the way
On 02/22/2018 02:54 PM, Linus Walleij wrote:
> On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay
> wrote:
>
>> MFX is used as gpio expander on stm32746g-eval.
>>
>> Signed-off-by: Amelie Delaunay
>
> (...)
>> + mfx: mfx@42 {
>> + compatible = "st,mfx";
>> + re
On 2/21/2018 2:13 PM, Raj, Ashok wrote:
> On Wed, Feb 21, 2018 at 08:06:11PM +0100, Borislav Petkov wrote:
>>> arch/x86/kernel/cpu/microcode/core.c | 113
>>> +-
>>
>> This is generic so Tom needs to ack whatever we end up doing for the AMD
>> side.
>
> Yes, i did
On 02/22/2018 06:33 PM, Michal Hocko wrote:
> On Thu 22-02-18 18:13:11, Andrey Ryabinin wrote:
>>
>>
>> On 02/22/2018 05:09 PM, Michal Hocko wrote:
>>> On Thu 22-02-18 16:50:33, Andrey Ryabinin wrote:
On 02/21/2018 11:17 PM, Andrew Morton wrote:
> On Fri, 19 Jan 2018 16:11:18 +0100 Micha
On 02/22/2018 02:52 PM, Linus Walleij wrote:
> Hi Amelie,
>
> thanks for your patch.
>
> On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay
> wrote:
>
>> The joystick on stm32746g-eval uses gpios on MFX gpio expander.
>>
>> Signed-off-by: Amelie Delaunay
> (...)
>> + joystick {
>> +
On Thu, Feb 22, 2018 at 02:28:46PM +0100, Geert Uytterhoeven wrote:
> Hi Arnd,
>
> On Thu, Feb 22, 2018 at 12:39 PM, Arnd Bergmann wrote:
> > On Wed, Feb 21, 2018 at 6:15 PM, Simon Horman wrote:
> >> On Tue, Feb 20, 2018 at 04:46:23PM +0100, Geert Uytterhoeven wrote:
> >>> On Tue, Feb 20, 2018 a
The only reason why I added this array on-stack was to allow consumers
that did not use ib_alloc_cq api to call it, but that seems like a
wrong decision when thinking it over again (as probably these users
did not set the wr_cqe correctly).
How about we make ib_process_cq_direct use the cq wc a
vfio-ccw only supports command mode for channel programs, not transport
mode. User space is supposed to already take care of that and pass us
command-mode ORBs only, but better make sure and return an error to
the caller instead of trying to process tcws as ccws.
Signed-off-by: Cornelia Huck
---
I'm currently prototyping hsch()/csch() support for vfio-ccw, and
stumbled over this: We currently expect any I/O to be in command-mode,
but don't take care to actively reject transport-mode. This is not an
issue with QEMU (which rejects transport-mode ORBs before even the css
backend gets to it),
On Thu, Feb 22, 2018 at 04:16:26PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 22, 2018 at 03:54:34PM +0100, Peter Zijlstra wrote:
> > On Thu, Feb 22, 2018 at 03:08:53PM +0800, Boqun Feng wrote:
> >
> > > +static inline int hlock_conflict(struct lock_list *entry, void *data)
> > > +{
> > > + struct
Two tiny patches for the IBRS code. They should go in
through the x86/pti tree and should apply to both 4.9 and 4.14 trees.
Thanks,
Paolo
v1->v2: remove patch 2, the same bug has already been fixed
Paolo Bonzini (3):
KVM: x86: use native MSR ops for SPEC_CTRL
KVM: VMX: mark RDMSR path as u
Having a paravirt indirect call in the IBRS restore path is not a
good idea, since we are trying to protect from speculative execution
of bogus indirect branch targets. It is also slower, so use
native_wrmsrl on the vmentry path too.
Fixes: d28b387fb74da95d69d2615732f50cceb38e9a4d
Cc: x...@kernel
vmx_vcpu_run and svm_vcpu_run are large functions, and this can actually
make a substantial cycle difference by keeping the fast path contiguous
in memory. Without it, the retpoline guest/retpoline host case is about
50 cycles slower.
Cc: x...@kernel.org
Cc: Radim Krčmář
Cc: KarimAllah Ahmed
Cc
On Thu 22-02-18 18:38:11, Andrey Ryabinin wrote:
>
>
> On 02/22/2018 06:33 PM, Michal Hocko wrote:
> > On Thu 22-02-18 18:13:11, Andrey Ryabinin wrote:
> >>
> >>
> >> On 02/22/2018 05:09 PM, Michal Hocko wrote:
> >>> On Thu 22-02-18 16:50:33, Andrey Ryabinin wrote:
> On 02/21/2018 11:17 PM,
On Thu, 22 Feb 2018 20:59:27 +0530
Shreeya Patel wrote:
> The log levels embedded with the name are more concise than
> printk.
If you don't mind, I'll replace the above sentence by:
"
Using pr_() is more concise than printk(KERN_).
"
The patch looks good otherwise, so I should apply it soon.
While building the cross-toolchains, I noticed that overall, we can build almost
all linux target architectures with upstream binutils and gcc these days,
however there are still some exceptions, and I'd like to find out if anyone
has objections to removing the ones that do not have upstream suppor
On Thu, 22 Feb 2018, Raj, Ashok wrote:
> On Thu, Feb 22, 2018 at 01:15:06PM +0100, Borislav Petkov wrote:
> > On Thu, Feb 22, 2018 at 03:55:54AM -0800, Raj, Ashok wrote:
> > > The current code wasn't trying to enforce checking the loaded microcode
> > > revision on a thread
> > > before attempting
On Thu, Feb 22, 2018 at 4:38 PM, Simon Horman wrote:
> On Thu, Feb 22, 2018 at 02:28:46PM +0100, Geert Uytterhoeven wrote:
>> Removing the .dts file removes the ability to boot the newly added board...
>>
>> The issue here is that we are sharing board .dtsi for boards that can be
>> equipped with
On Wed, Feb 21, 2018 at 09:54:55PM +0100, Alexandre Belloni wrote:
> Hello,
>
> This series:
> - removes useless calls to rtc_valid_tm in .read_time, .set_time and
>.set_alarm
> - removes code setting default values for RTCs (and lets the core
>handle it)
> - removes useless "time is in
> > In the past the only guidance was to not load microcode at the same time to
> the
> > thread siblings of a core. We now have new guidance that the sibling must be
> > spinning and not doing other things that can introduce instability around
> loading
> > microcode.
>
> Document that properly
On Thu, Feb 22, 2018 at 2:58 PM, Waiman Long wrote:
> On 02/22/2018 06:45 AM, Arnd Bergmann wrote:
>> The removal of the batched object freeing has caused the debug_objects_freed
>> to become read-only, and the reading is inside an ifdef, so gcc warns that it
>> is completely unused without CONFIG
On Thu, Feb 22, 2018 at 04:30:34PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 22, 2018 at 11:12:10PM +0800, Boqun Feng wrote:
> > On Thu, Feb 22, 2018 at 03:26:14PM +0100, Peter Zijlstra wrote:
>
> > > However, I would suggest:
> > >
> > > static inline bool is_xr(u16 dep)
> > > {
> > > return
The removal of the batched object freeing has caused the debug_objects_freed
to become read-only, and the reading is inside an ifdef, so gcc warns that it
is completely unused without CONFIG_DEBUG_FS:
lib/debugobjects.c:71:14: error: 'debug_objects_freed' defined but not used
[-Werror=unused-vari
On Wed, Feb 21, 2018 at 09:53:58PM +0300, Sergei Shtylyov wrote:
> On 02/21/2018 09:23 PM, Simon Horman wrote:
>
> > ...
> >
> +clocks = <&cpg CPG_MOD 812>;
> +power-domains = <&sysc 32>;
> +resets = <&cpg 812>
gcc-8 has a new warning that detects overlapping input and output arguments
in memcpy(). It triggers for sit_init_net() calling ipip6_tunnel_clone_6rd(),
which is actually correct:
net/ipv6/sit.c: In function 'sit_init_net':
net/ipv6/sit.c:192:3: error: 'memcpy' source argument is the same as
des
gcc-6.3 and earlier show a new warning after a seemingly unrelated change
to the arm64 PAGE_KERNEL definition:
In file included from drivers/md/dm-bufio.c:14:0:
drivers/md/dm-bufio.c: In function 'alloc_buffer':
include/linux/sched/mm.h:182:56: warning: 'noio_flag' may be used uninitialized
in th
On 22.02.2018 01:28, Kees Cook wrote:
> The header files for some structures could get included in such a way
> that struct attributes (specifically __randomize_layout from path.h) would
> be parsed as variable names instead of attributes. This could lead to
> some instances of a structure being un
On 02/21/2018 02:18 PM, Al Viro wrote:
On Wed, Feb 21, 2018 at 01:59:55PM -0600, Brijesh Singh wrote:
Sure, checking access_ok() does not guarantee that later
copy_from_user() will not fail. But it does eliminate one possible
reason for the failure. We are trying to validate most of the user
Access to the socket API and the root network namespace is only available
when networking is enabled:
ERROR: "kernel_sendmsg" [drivers/soc/qcom/qmi_helpers.ko] undefined!
ERROR: "sock_release" [drivers/soc/qcom/qmi_helpers.ko] undefined!
ERROR: "sock_create_kern" [drivers/soc/qcom/qmi_helpers.ko]
On 02/22/2018 10:21 AM, mario.limoncie...@dell.com wrote:> I guess that
means we got this wrong and the patch should be reverted
> until we figure this out.
>
> Jeremy,
>
> Can you please confirm what BIOS version you are on?
> Also Is this a 9360 with 7th or 8th gen Intel CPU?
Hi Mario,
I've g
On 02/22/2018 06:44 PM, Michal Hocko wrote:
> On Thu 22-02-18 18:38:11, Andrey Ryabinin wrote:
with the patch:
best: 1.04 secs, 9.7G reclaimed
worst: 2.2 secs, 16G reclaimed.
without:
best: 5.4 sec, 35G reclaimed
worst: 22.2 sec, 136G reclaimed
>>>
>>> Co
On 22/02/2018 at 07:48:03 -0800, Christoph Hellwig wrote:
> On Wed, Feb 21, 2018 at 09:54:55PM +0100, Alexandre Belloni wrote:
> > Hello,
> >
> > This series:
> > - removes useless calls to rtc_valid_tm in .read_time, .set_time and
> >.set_alarm
> > - removes code setting default values for
This patch renames error recovery to generic name with pci prefix
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/pcie/aer/aerdrv_core.c
b/drivers/pci/pcie/aer/aerdrv_core.c
index a4bfea5..306bf2f 100644
--- a/drivers/pci/pcie/aer/aerdrv_core.c
+++ b/drivers/pci/pcie/aer/aerdrv_core.c
@@
This patch factors out error reporting callbacks, which are currently
tightly coupled with AER.
DPC should be able to register callbacks and attmept recovery when DPC
trigger event occurs.
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
index fcd8191..a5a79f0 1006
Implement error_resume callback in DPC so, after DPC trigger event
enumerates the devices beneath.
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/pcie/pcie-dpc.c b/drivers/pci/pcie/pcie-dpc.c
index 0524bd3..382d5c5 100644
--- a/drivers/pci/pcie/pcie-dpc.c
+++ b/drivers/pci/pcie/pcie-dpc.c
Clients such as pciehp, dpc are using pcie_wait_link_active, which waits
till the link becomes active or inactive.
Made generic function and moved it to drivers/pci/pci.c
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/hotplug/pciehp_hpc.c b/drivers/pci/hotplug/pciehp_hpc.c
index 18a42f8.
On 2/22/18 7:52 AM, Arnd Bergmann wrote:
The removal of the batched object freeing has caused the debug_objects_freed
to become read-only, and the reading is inside an ifdef, so gcc warns that it
is completely unused without CONFIG_DEBUG_FS:
lib/debugobjects.c:71:14: error: 'debug_objects_free
This patch moves AER error defines to drivers/pci/pci.h.
So that it unifies the error repoting codes at single place along with dpc
Signed-off-by: Oza Pawandeep
diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
index 1efefe9..7ae9bb3 100644
--- a/drivers/acpi/apei/ghes.c
+++ b/dri
This patch protects pci_do_recovery with mutex.
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/pcie/pcie-err.c b/drivers/pci/pcie/pcie-err.c
index a532fe0..8318c84 100644
--- a/drivers/pci/pcie/pcie-err.c
+++ b/drivers/pci/pcie/pcie-err.c
@@ -20,6 +20,8 @@
#include
#include "portdrv.h"
Current DPC driver does not do recovery, e.g. calling end-point's driver's
callbacks, which sanitize the sw.
DPC driver implements link_reset callback, and calls pci_do_recovery.
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
index a5a79f0..124f42e 100644
--- a/
On Thu, Feb 22 2018 at 10:56am -0500,
Arnd Bergmann wrote:
> gcc-6.3 and earlier show a new warning after a seemingly unrelated change
> to the arm64 PAGE_KERNEL definition:
>
> In file included from drivers/md/dm-bufio.c:14:0:
> drivers/md/dm-bufio.c: In function 'alloc_buffer':
> include/linux
On Thu, Feb 22, 2018 at 04:45:06PM +0100, Arnd Bergmann wrote:
> There are also a couple of architectures that are more or less
> unmaintained but do have working gcc support: FR-V and M32R
> have been orphaned for a while and are not getting updated
> MN10300 is still maintained officially by Davi
This patch set brings in error handling support for DPC
The current implementation of AER and error message broadcasting to the
EP driver is tightly coupled and limited to AER service driver.
It is important to factor out broadcasting and other link handling
callbacks. So that not only when AER ge
On 2018-02-22 21:32, Oza Pawandeep wrote:
This patch moves AER error defines to drivers/pci/pci.h.
So that it unifies the error repoting codes at single place along with
dpc
Signed-off-by: Oza Pawandeep
diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
index 1efefe9..7ae9bb3 1
Hi Wolfram,
Thank you for the patch.
On Monday, 5 February 2018 22:09:58 EET Wolfram Sang wrote:
> Due to a typo, the mask was destroyed by a comparison instead of a bit
> shift. No regression since the mask has not been used yet.
>
> Signed-off-by: Wolfram Sang
Oops.
Reviewed-by: Laurent Pin
Hi all,
We agree to remove the Score arch.
I have discussed the status with Sunplus, and they plan to replace the
arch with ARM.
I will make a request to remove Linux kernel, too.
Best,
Lennox
2018-02-22 23:45 GMT+08:00 Arnd Bergmann :
> While building the cross-toolchains, I noticed that overall,
On Thu, Feb 22, 2018 at 11:12:10PM +0800, Boqun Feng wrote:
> On Thu, Feb 22, 2018 at 03:26:14PM +0100, Peter Zijlstra wrote:
> > On Thu, Feb 22, 2018 at 03:08:52PM +0800, Boqun Feng wrote:
> > > Now we have four kinds of dependencies in the dependency graph, and not
> > > all the pathes carry stro
On 02/22/2018 10:52 AM, Arnd Bergmann wrote:
> The removal of the batched object freeing has caused the debug_objects_freed
> to become read-only, and the reading is inside an ifdef, so gcc warns that it
> is completely unused without CONFIG_DEBUG_FS:
>
> lib/debugobjects.c:71:14: error: 'debug_obj
On Thu, Feb 22, 2018 at 08:12:48AM +0200, Oleksandr Andrushchenko wrote:
> On 02/22/2018 08:09 AM, Oleksandr Andrushchenko wrote:
> > From: Oleksandr Andrushchenko
> >
> > It is possible that drm_simple_kms_plane_atomic_check called
> > with no CRTC set, e.g. when user-space application sets CRTC
> -Original Message-
> From: Jeremy Cline [mailto:jer...@jcline.org]
> Sent: Thursday, February 22, 2018 9:59 AM
> To: Limonciello, Mario ; notm...@gmail.com
> Cc: pali.ro...@gmail.com; andriy.shevche...@linux.intel.com;
> mj...@srcf.ucam.org; dvh...@infradead.org; platform-driver-
> x...@v
On 02/22/2018 11:14 AM, mario.limoncie...@dell.com wrote:
>> -Original Message-
>> From: Jeremy Cline [mailto:jer...@jcline.org]
>> Sent: Thursday, February 22, 2018 9:59 AM
>> To: Limonciello, Mario ; notm...@gmail.com
>> Cc: pali.ro...@gmail.com; andriy.shevche...@linux.intel.com;
>> mj..
> -Original Message-
> From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-x86-
> ow...@vger.kernel.org] On Behalf Of Jeremy Cline
> Sent: Thursday, February 22, 2018 10:17 AM
> To: Limonciello, Mario ; notm...@gmail.com
> Cc: pali.ro...@gmail.com; andriy.shevche...@linu
tches can be found here also:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/tag/?h=keys-fixes-20180222
And also on the keys-fixes branch.
David
---
David Howells (1):
KEYS: Use individual pages in big_key for crypto buffers
Eric Biggers (5):
PKCS#7
On Thu, Feb 22, 2018 at 03:21:45PM +, mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Marco Martin [mailto:notm...@gmail.com]
> > Sent: Thursday, February 22, 2018 9:16 AM
> > To: Jeremy Cline
> > Cc: Limonciello, Mario ; Pali Rohár
> > ; Andy Shevchenko ;
> > Matthe
>> >
>> > So lets call it a day and drop the Meta architecture port from the
>> > kernel. RIP Meta.
Oh, and James, I meant to ask/note - I guess that just leaves parisc
using STACK_GROWSUP... shame we could not ditch that as well then eh?
Graham
On 2018-02-16 16:46:41 [-0500], Alan Stern wrote:
> > The theaded interrupt runs SCHED_FIFO priority 50 by default. The only
> > thing that can interrupt it are interrupts, a softirq (not ksoftirqd)
> > and other tasks with a higher priority than 50.
> > There should be no downside performance wise
From: Ondrej Jirman
I noticed that with 4.16-rc1 LVDS output on A83T based TBS A711 tablet doesn't
work (there's output but it's garbled). I compared some older patches for LVDS
support with the mainlined ones and this change is missing from mainline Linux.
I don't know what the register does ex
On Thu, Feb 22, 2018 at 12:47:51PM +0100, Arnd Bergmann wrote:
> When comparing two variables with min()/max(), they should be the same type:
>
> drivers/gpu/drm/drm_memory.c: In function 'drm_get_max_iomem':
> include/linux/kernel.h:821:16: error: comparison of distinct pointer types
> lacks a c
tches can be found here also:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/tag/?h=keys-fixes-20180222
And also on the keys-fixes branch.
David
---
David Howells (1):
KEYS: Use individual pages in big_key for crypto buffers
Eric Biggers (5):
PKCS#7
From: Eric Biggers
When pkcs7_verify_sig_chain() is building the certificate chain for a
SignerInfo using the certificates in the PKCS#7 message, it is passing
the wrong arguments to public_key_verify_signature(). Consequently,
when the next certificate is supposed to be used to verify the previ
From: Eric Biggers
If none of the certificates in a SignerInfo's certificate chain match a
trusted key, nor is the last certificate signed by a trusted key, then
pkcs7_validate_trust_one() tries to check whether the SignerInfo's
signature was made directly by a trusted key. But, it actually fail
From: Eric Biggers
If there is a blacklisted certificate in a SignerInfo's certificate
chain, then pkcs7_verify_sig_chain() sets sinfo->blacklisted and returns
0. But, pkcs7_verify() fails to handle this case appropriately, as it
actually continues on to the line 'actual_ret = 0;', indicating th
From: Eric Biggers
The X.509 parser mishandles the case where the certificate's signature's
hash algorithm is not available in the crypto API. In this case,
x509_get_sig_params() doesn't allocate the cert->sig->digest buffer;
this part seems to be intentional. However,
public_key_verify_signatu
From: Eric Biggers
The asymmetric key type allows an X.509 certificate to be added even if
its signature's hash algorithm is not available in the crypto API. In
that case 'payload.data[asym_auth]' will be NULL. But the key
restriction code failed to check for this case before trying to use the
kmalloc() can't always allocate large enough buffers for big_key to use for
crypto (1MB + some metadata) so we cannot use that to allocate the buffer.
Further, vmalloc'd pages can't be passed to sg_init_one() and the aead
crypto accessors cannot be called progressively and must be passed all the
da
On Wed, 21 Feb 2018, Andy Shevchenko wrote:
> > Change-Id: I0d1b6fd652395b85f82b11c43bf9b7db512854d1
>
> First of all, this shouldn't be here.
>
Please excuse me. I know that I have to remove this, but
unfortunately I forgot to do so (here and also in the other patch).
> > Signed-off-by: Rolf
On 2018/2/15 21:34, Ludovic Barre wrote:
From: Ludovic Barre
...
+
+static ssize_t stm32_sdmmc_stat_reset(struct file *filp,
+ const char __user *ubuf,
+ size_t count, loff_t *ppos)
+{
+ struct seq_file *seqf = fi
From: Or Idgar
This patch is a driver which expose the Virtual Machine Generation ID
via sysfs. The ID is a UUID value used to differentiate between virtual
machines.
The VM-Generation ID is a feature defined by Microsoft (paper:
http://go.microsoft.com/fwlink/?LinkId=260709) and supported by mu
The S390 architecture does not support any graphics hardware,
but with the latest support for Virtio GPU in Linux and Virtio
GPU emulation in QEMU, it's possible to enable graphics for
S390 using the Virtio GPU device.
To enable display we need to enable the Linux Virtual Terminal (VT)
layer for S
The Linux Virtual Terminal (VT) layer provides a default keymap
which is compiled when VT layer is enabled. But at the same time
we are also compiling the EBCDIC keymap and this causes the linker
to complain.
So let's rename the EBCDIC keymap variables to prevent linker
conflict.
Signed-off-by: F
The 'commit e25df1205f37 ("[S390] Kconfig: menus with depends on HAS_IOMEM.")'
added the HAS_IOMEM dependecy for "Graphics support". This disabled the
"Graphics support" menu for S390. But if we enable VT layer for S390,
we would also need to enable the dummy console. So let's remove the
HAS_IOMEM
Hi,
This series of patches add support for an additional tty
and console for a S390 KVM guest using a virtio-gpu device[1].
Patch 1 enables the "Graphics support" menu which is
needed to enable dummy console, since the VT layer needs it.
The dependency is moved to sub menu items and console
drive
We cannot select a symbol without meeting its other dependencies:
warning: (DRM_PL111) selects DRM_DUMB_VGA_DAC which has unmet direct
dependencies (HAS_IOMEM && DRM && DRM_BRIDGE && OF)
drivers/gpu/drm/bridge/dumb-vga-dac.c: In function 'dumb_vga_probe':
drivers/gpu/drm/bridge/dumb-vga-dac.c:207
On Mon, Feb 19, 2018 at 05:02:28PM +0200, Andy Shevchenko wrote:
> In all cases list_for_each() followed by list_entry(),
> so, replace them by list_for_each_entry() macro.
>
> Signed-off-by: Andy Shevchenko
Nice cleanup Andy, thanks.
Reviewed-by: Darren Hart (VMware)
--
Darren Hart
VMware O
On Thu, Feb 22, 2018 at 5:02 PM, Christoph Hellwig wrote:
> On Thu, Feb 22, 2018 at 04:45:06PM +0100, Arnd Bergmann wrote:
>> There are also a couple of architectures that are more or less
>> unmaintained but do have working gcc support: FR-V and M32R
>> have been orphaned for a while and are not
Sorry, that RFC shouldn't be there in the subject.
David
[Apologies to keep elbowing in, and if I'm being thick here...]
On 22/02/18 15:22, Mark Rutland wrote:
On Thu, Feb 22, 2018 at 08:51:30AM -0600, Shanker Donthineni wrote:
+#define CTR_B31_SHIFT 31
Since this is just a RES1 bit, I think we don't need a mnemonic for it,
but I'll defer
On Thu, Feb 22, 2018 at 04:51:43PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 22, 2018 at 04:30:34PM +0100, Peter Zijlstra wrote:
> > On Thu, Feb 22, 2018 at 11:12:10PM +0800, Boqun Feng wrote:
> > > On Thu, Feb 22, 2018 at 03:26:14PM +0100, Peter Zijlstra wrote:
> >
> > > > However, I would sugge
> -Original Message-
> From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-x86-
> ow...@vger.kernel.org] On Behalf Of Darren Hart
> Sent: Thursday, February 22, 2018 10:19 AM
> To: Limonciello, Mario
> Cc: notm...@gmail.com; jer...@jcline.org; pali.ro...@gmail.com;
> an
Hi Arnd,
On Thu, Feb 22, 2018 at 04:45:06PM +0100, Arnd Bergmann wrote:
> * Meta was ImgTec's own architecture and they upstreamed the kernel
> port just before they acquired MIPS. Apparently Meta was abandoned
> shortly afterwards and disappeared from imgtec's website in 2014.
> The maintai
Hi,
A single patch changing my email address. I think it is worth having it
in MAINTAINERS sooner rather than later.
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the Git repository at:
git://git.ker
On Thu 22-02-18 19:01:58, Andrey Ryabinin wrote:
>
>
> On 02/22/2018 06:44 PM, Michal Hocko wrote:
> > On Thu 22-02-18 18:38:11, Andrey Ryabinin wrote:
>
>
> with the patch:
> best: 1.04 secs, 9.7G reclaimed
> worst: 2.2 secs, 16G reclaimed.
>
> without:
> bes
On Thu, Feb 22, 2018 at 05:08:11PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 22, 2018 at 11:12:10PM +0800, Boqun Feng wrote:
> > On Thu, Feb 22, 2018 at 03:26:14PM +0100, Peter Zijlstra wrote:
> > > On Thu, Feb 22, 2018 at 03:08:52PM +0800, Boqun Feng wrote:
> > > > Now we have four kinds of depen
On Thu, Feb 22, 2018 at 10:10:40AM +0100, Benjamin Tissoires wrote:
> On Thu, Feb 22, 2018 at 1:13 AM, Pierre-Loup A. Griffais
> wrote:
> >
> >
> > On 02/21/2018 12:21 PM, Rodrigo Rivas Costa wrote:
> >>
> >> On Tue, Feb 20, 2018 at 04:09:39PM -0800, Pierre-Loup A. Griffais wrote:
> >>>
> >>> On 0
Using pr_() is more concise than
printk(KERN_).
Replace printks having a log level with the appropriate
pr_*() macros.
Define pr_fmt() and remove other additional macros from
the replaced printks.
Signed-off-by: Shreeya Patel
---
Changes in v5
-Make the commit message more appropriate and plac
401 - 500 of 952 matches
Mail list logo
