On Fri, Jan 11, 2019 at 12:46:39PM -0800, Linus Torvalds wrote:
> On Fri, Jan 11, 2019 at 12:31 PM Josh Poimboeuf wrote:
> >
> > I was referring to the fact that a single static call key update will
> > usually result in patching multiple call sites. But you're right, it's
> > only 1-2
Dear RT Folks,
I'm pleased to announce the 4.14.87-rt50 stable release.
Note, I added:
drm/i915: skip DRM_I915_LOW_LEVEL_TRACEPOINTS with NOTRACE
since -rc1.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch:
Hi Jagan.
Gave this another more detailed read - triggered some additional comments.
Depite the comments it looks good, and this is all more or
less cosmetic improvements.
Sam
> +struct st7701_panel_desc {
> + const struct drm_display_mode *mode;
> + unsigned int lanes;
> +
On Fri, Jan 11, 2019 at 1:05 PM Andy Lutomirski wrote:
>
> > Yeah, my suggestion doesn't allow for batching, since it would
> > basically generate one trampoline for every rewritten instruction.
>
> Sure it does. Just make 1000 trampolines and patch 1000 sites in a
> batch :) As long as the
On Thu, 10 Jan 2019 at 21:16, Gerd Hoffmann wrote:
>
> Also set prime_handle_to_fd and prime_fd_to_handle to NULL,
> so drm will not advertive DRM_PRIME_CAP_{IMPORT,EXPORT} to
> userspace.
Reviewed-by: Dave Airlie
>
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/virtio/virtgpu_drv.h
Hi,
On Wed, Jan 9, 2019 at 9:00 AM Sibi Sankar wrote:
>
> This patch adds Q6V5 MSS remoteproc node for SDM845 SoCs.
>
> Signed-off-by: Sibi Sankar
> Reviewed-by: Douglas Anderson
> ---
>
> v5:
> * Use qmp_aop updated dt binding
nit: since this is now a singleton patch in v5 (because patches
On Thu, 10 Jan 2019 at 18:17, Gerd Hoffmann wrote:
>
> Also set prime_handle_to_fd and prime_fd_to_handle to NULL,
> so drm will not advertive DRM_PRIME_CAP_{IMPORT,EXPORT} to
> userspace.
>
> Signed-off-by: Gerd Hoffmann
Reviewed-by: Dave Airlie
> ---
> drivers/gpu/drm/qxl/qxl_drv.c | 4
On Fri, Jan 11, 2019 at 12:42 PM Dave Hansen wrote:
>
> >> The second process could easily have the page's old TLB entry. It could
> >> abuse that entry as long as that CPU doesn't context switch
> >> (switch_mm_irqs_off()) or otherwise flush the TLB entry.
> >
> > That is an interesting
On Fri, Jan 11, 2019 at 12:54 PM Linus Torvalds
wrote:
>
> On Fri, Jan 11, 2019 at 12:31 PM Josh Poimboeuf wrote:
> >
> > I was referring to the fact that a single static call key update will
> > usually result in patching multiple call sites. But you're right, it's
> > only 1-2 trampolines per
This patch is the result of seeing this message:
psmouse serio1: synaptics: Your touchpad (PNP: DLL087c PNP0f13) says it can
support a different bus. If i2c-hid and hid-rmi are not used, you might want to
try setting psmouse.synaptics_intertouch to 1 and report this to
On Fri, 11 Jan 2019, Matthew Wilcox wrote:
> On Fri, Jan 11, 2019 at 08:19:33PM +0100, Thomas Gleixner wrote:
> > On Fri, 11 Jan 2019, Thomas Gleixner wrote:
> > > --- a/kernel/irq/internals.h
> > > +++ b/kernel/irq/internals.h
> > > @@ -246,6 +246,7 @@ static inline void kstat_incr_irqs_this_
> >
Hi Shakeel,
On Thu, Jan 10, 2019 at 09:44:32AM -0800, Shakeel Butt wrote:
> If a memcg is over high limit, memory reclaim is scheduled to run on
> return-to-userland. However it is assumed that the memcg is the current
> process's memcg. With remote memcg charging for kmem or swapping in a
>
A GPF was reported,
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: [#1] SMP KASAN
kasan_die_handler.cold.22+0x11/0x31
notifier_call_chain+0x17b/0x390
atomic_notifier_call_chain+0xa7/0x1b0
On 1/11/19 1:24 AM, Peter Zijlstra wrote:
> diff --git a/include/linux/bitops.h b/include/linux/bitops.h
> index 705f7c442691..2060d26a35f5 100644
> --- a/include/linux/bitops.h
> +++ b/include/linux/bitops.h
> @@ -241,10 +241,10 @@ static __always_inline void __assign_bit(long nr,
> volatile
Use dev_* variants to print messages in drivers.
Signed-off-by: Stefan Agner
---
drivers/bluetooth/btmrvl_sdio.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/bluetooth/btmrvl_sdio.c b/drivers/bluetooth/btmrvl_sdio.c
index fb3d03928460..6f9a1735039d 100644
The platform specific wake-up interrupt is optional. Don't print
an error message in case it is missing, merely inform the user in
this case.
Signed-off-by: Stefan Agner
---
drivers/bluetooth/btmrvl_sdio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This commit allow the driver to work with device-tree.
Signed-off-by: Sebastien Bourdelin
---
v1 -> v2:
- add missing of.h header in bme680_spi.c
---
drivers/iio/chemical/bme680_i2c.c | 7 +++
drivers/iio/chemical/bme680_spi.c | 9 +
2 files changed, 16 insertions(+)
diff --git
BME680 is a pressure/temperature/humidity/voc sensor.
Signed-off-by: Sebastien Bourdelin
---
.../devicetree/bindings/iio/chemical/bme680.txt | 11 +++
1 file changed, 11 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/chemical/bme680.txt
diff --git
Hello,
On Fri, Jan 11, 2019 at 10:51:15AM +0530, Sheetal Tigadoli wrote:
> From: Praveen Kumar B
>
> Add support for new version of pwm-kona.
> Add support to make PWM changes configured and stable.
>
> Signed-off-by: Praveen Kumar B
> Reviewed-by: Ray Jui
> Reviewed-by: Scott Branden
>
On Fri, Jan 11, 2019 at 12:54 PM Stephen Boyd wrote:
>
> Quoting Rob Herring (2019-01-11 10:27:48)
> > On Fri, Jan 11, 2019 at 11:44 AM Stephen Boyd wrote:
> > >
> > > Quoting Rob Herring (2019-01-10 14:19:01)
> > > > Convert the fixed-clock binding to DT schema format using json-schema.
> > > >
On Fri, Jan 11, 2019 at 10:51:14AM +0530, Sheetal Tigadoli wrote:
> From: Praveen Kumar B
>
> Add new compatible string for new version of pwm-kona
>
> Signed-off-by: Praveen Kumar B
> Reviewed-by: Ray Jui
> Reviewed-by: Scott Branden
> Signed-off-by: Sheetal Tigadoli
> ---
>
On Fri, Jan 11, 2019 at 12:31 PM Josh Poimboeuf wrote:
>
> I was referring to the fact that a single static call key update will
> usually result in patching multiple call sites. But you're right, it's
> only 1-2 trampolines per text_poke_bp() invocation. Though eventually
> we may want to
Daniel,
On Tue, 8 Jan 2019, Daniel Vacek wrote:
> I'm wondering, was x86/timers branch of tip tree merged to linus' tree
> for v5.0-rc1? Somehow I do not see this patch make it through...
>
> Am I doing something wrong?
No. The branch was not sent to Linus during the merge window due to
Paul,
On Mon, 7 Jan 2019, Paul Menzel wrote:
> On 01/07/19 16:24, Thomas Gleixner wrote:
> >> Linux 4.19.13 from Debian Sid/unstable logs the message below on the board
> >> MSI
> >> MS-7A37/B350M MORTAR with the processor AMD Ryzen 3 2200G.
> >>
> >> As a result, the early time stamps do not
>> The second process could easily have the page's old TLB entry. It could
>> abuse that entry as long as that CPU doesn't context switch
>> (switch_mm_irqs_off()) or otherwise flush the TLB entry.
>
> That is an interesting scenario. Working through this scenario, physmap
> TLB entry for a page
On 11.01.2019 23:33, Eric W. Biederman wrote:
> zzoru writes:
>
>> net/core: BUG in copy_net_ns() (net_namespace.c)
>
> I don't understand this failure report at all.
>
> I don't see the connection to copy_net_ns(). And I don't see how the
> suggested patch short of covering up a memory stomp
The pull request you sent on Fri, 11 Jan 2019 19:56:52 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-current
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4b3c31c8d4dda4d70f3f24a165f3be99499e0328
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 11 Jan 2019 18:20:57 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c3405d68997432c12a4f3a5e72dedc660c0b
Thank you!
--
Deet-doot-dot, I am
Commit-ID: 7e6fc2f50a3197d0e82d1c0e86282976c9e6c8a4
Gitweb: https://git.kernel.org/tip/7e6fc2f50a3197d0e82d1c0e86282976c9e6c8a4
Author: Daniel Drake
AuthorDate: Mon, 7 Jan 2019 11:40:24 +0800
Committer: Thomas Gleixner
CommitDate: Fri, 11 Jan 2019 21:35:47 +0100
x86/kaslr: Fix
On 1/11/19 7:08 AM, Juergen Gross wrote:
> @@ -421,6 +424,11 @@ void xen_restore_time_memory_area(void)
> if (ret != 0)
> pr_notice("Cannot restore secondary vcpu_time_info (err %d)",
> ret);
> +
> +out:
> + /* Need pvclock_resume() before using
Sensor can periodically trigger self cleaning. Period can be changed by
writing a new value to a dedicated attribute. Upon attribute read
current period gets returned.
Signed-off-by: Tomasz Duszynski
---
v2:
* return available values formated as a range
* tweak naming a little (interval ->
On Fri, Jan 11, 2019 at 04:47:15PM +0530, Amit Kucheria wrote:
> On Fri, Jan 11, 2019 at 6:00 AM Matthias Kaehlcke wrote:
> >
> > On Thu, Jan 10, 2019 at 05:30:56AM +0530, Amit Kucheria wrote:
> > > Since the big and little cpus are in the same frequency domain, use all
> > > of them for
zzoru writes:
> net/core: BUG in copy_net_ns() (net_namespace.c)
I don't understand this failure report at all.
I don't see the connection to copy_net_ns(). And I don't see how the
suggested patch short of covering up a memory stomp could possibly make
a difference.
What am I missing?
>
On Fri, Jan 11, 2019 at 12:12:30PM -0800, Linus Torvalds wrote:
> On Fri, Jan 11, 2019 at 12:04 PM Josh Poimboeuf wrote:
> >
> > But really, to me, having to create and manage all those custom
> > trampolines still feels a lot more complex than just making a gap on the
> > stack.
>
> There are
The pull request you sent on Fri, 11 Jan 2019 18:02:26 +0100:
> https://github.com/ceph/ceph-client.git tags/ceph-for-5.0-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f87092c4337fc064b52bfad1df499a5b82f6d088
Thank you!
--
Deet-doot-dot, I am a bot.
The rwlock is spinning while acquiring a lock. Therefore it must become
a sleeping lock on RT and preserve its task state while sleeping and
waiting for the lock.
Reported-by: Joe Korty
Signed-off-by: Sebastian Andrzej Siewior
---
kernel/locking/rwlock-rt.c | 2 +-
1 file changed, 1
On Mon, 7 Jan 2019, Daniel Drake wrote:
> I asked the motherboard vendor if they have any idea why the 8254 is
> not ticking and they sent me a new BIOS where it is now working. So we
> can probably consider this a non issue, although there are a few other
> curious points to mention:
>
> 1.
On Fri, Jan 04, 2019 at 10:56:56PM +0100, Lubomir Rintel wrote:
> A pair of rather trivial ones.
>
> Signed-off-by: Lubomir Rintel
>
> ---
> Changes since v1:
> - s/identifier/identifiers/ as suggested by Rob Herring
>
> Documentation/devicetree/bindings/clock/marvell,mmp2.txt | 2 +-
> 1
On Fri, Jan 11, 2019 at 12:04 PM Josh Poimboeuf wrote:
>
> But really, to me, having to create and manage all those custom
> trampolines still feels a lot more complex than just making a gap on the
> stack.
There are no "all those custom trampolines".
There is literally *one* custom trampoline
At LPC last year, Boaz Harrosh asked why he had to 'jump through hoops'
to get an address returned by mmap() suitably aligned for THP. It seems
that if mmap is asking for a mapping length greater than huge page
size, it should align the returned address to huge page size.
THP alignment has
On Fri, Jan 04, 2019 at 01:56:21PM -0800, Jolly Shah wrote:
> From: Nava kishore Manne
>
> Add documentation to describe Xilinx ZynqMP reset driver
> bindings.
>
> Signed-off-by: Nava kishore Manne
> Signed-off-by: Jolly Shah
> ---
> .../bindings/reset/xlnx,zynqmp-reset.txt | 148
On Fri, 11 Jan 2019, Greg Kroah-Hartman wrote:
> On Fri, Jan 11, 2019 at 01:33:09PM -0500, Nicolas Pitre wrote:
> > I use Linux with the help of a braille display and the brltty daemon. It
> > turns out that the latest mainline kernel I can work with comes from
> > commit 231f8fd0cc. Anything
From: George Rimar
Linux kernel uses OUTPUT_FORMAT in it's linker scripts. Most of the time
-m option is passed to the linker with correct architecture, but
sometimes (at least for x86_64) the -m option contradicts OUTPUT_FORMAT
directive. Specifically, arch/x86/boot and arch/x86/realmode/rm
On Fri, 4 Jan 2019 13:56:20 -0800, Jolly Shah wrote:
> From: Rajan Vaja
>
> Add documentation to describe Xilinx ZynqMP power management
> bindings.
>
> Signed-off-by: Rajan Vaja
> Signed-off-by: Jolly Shah
> ---
> .../bindings/power/reset/xlnx,zynqmp-power.txt | 25
>
On Fri, 4 Jan 2019 13:56:19 -0800, Jolly Shah wrote:
> From: Rajan Vaja
>
> Add documentation to describe ZynqMP power domain bindings.
>
> Signed-off-by: Rajan Vaja
> Signed-off-by: Jolly Shah
> ---
> .../bindings/power/xlnx,zynqmp-genpd.txt | 34 +++
>
On Fri, Jan 04, 2019 at 01:56:22PM -0800, Jolly Shah wrote:
> From: Rajan Vaja
>
> Add documentation to describe Xilinx ZynqMP pin controller
> bindings.
>
> Signed-off-by: Rajan Vaja
> Signed-off-by: Jolly Shah
> ---
> .../bindings/pinctrl/xlnx,zynqmp-pinctrl.txt | 275
>
On 12/26/2018 12:48 AM, Kangjie Lu wrote:
> When match_int fails, "arg" is left uninitialized and may contain random
> value, thus should not be used.
> The fix checks if match_int fails, and if so, break.
>
> Signed-off-by: Kangjie Lu
> ---
> drivers/target/target_core_rd.c | 3 ++-
> 1 file
On Fri, Jan 11, 2019 at 1:58 PM Rob Herring wrote:
>
> On Thu, Jan 10, 2019 at 11:34 AM John Stultz wrote:
> >
> > Some dma channels can be reserved for secure mode or other
> > hardware on the SoC, so provide a binding for a bitmask
> > listing the available channels for the kernel to use.
> >
On Fri, Jan 11, 2019 at 11:03:30AM -0800, Linus Torvalds wrote:
> The we'd change the end of poke_int3_handler() to do something like
> this instead:
>
> void *newip = bp_int3_handler;
> ..
> if (new == magic_static_call_bp_int3_handler) {
> if (regs->flags
On Fri, Jan 11, 2019 at 09:16:53AM +0530, Viresh Kumar wrote:
> On 10-01-19, 10:42, Matthias Kaehlcke wrote:
> > Thanks for the pointer, there's always something new to learn!
> >
> > Ok, so the policy CPU and hence the CPU registered as cooling
> > device may vary. I understand that this
On Thu, Jan 10, 2019 at 11:34 AM John Stultz wrote:
>
> Some dma channels can be reserved for secure mode or other
> hardware on the SoC, so provide a binding for a bitmask
> listing the available channels for the kernel to use.
>
> Cc: Vinod Koul
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc:
Per Jonathan Cameron, the buffer needs to allocate room for a
64 bit timestamp as well as the channels. Change the buffer
to allocate this additional space.
Fixes: 2a86487786b5c ("iio: adc: ti-ads8688: add trigger and buffer support")
Signed-off-by: Dan Murphy
---
v3 - Updated the buffer
Introduce the TI ADS124S08 and the ADS124S06 ADC
devices from TI. The ADS124S08 is the 12 channel ADC
and the ADS124S06 is the 6 channel ADC device
These devices share a common datasheet:
http://www.ti.com/lit/gpn/ads124s08
Signed-off-by: Dan Murphy
---
v3 - Fixed the IIO channel definition,
Adding binding documentation for Texas Instruments ADS124S08
and ADS124S06 ADC.
S08 is a 12 channel ADC
S06 is a 6 channel ADC
Datesheet can be found here:
http://www.ti.com/lit/gpn/ads124s08
Signed-off-by: Dan Murphy
---
v3 - Fixed the compatible made the colon spacing consistent -
Hi,
I've now applied this patchset, so please send any further fixups as
incremental on top of for-5.1/atomic-replace.
Thanks to everybody involved (especially Petr) for the patience and all
the invested effort.
--
Jiri Kosina
SUSE Labs
Martin Blumenstingl writes:
> Hi,
>
> some nit-picks as well as my Tested-by (in case it's not too late) below.
> thank you for taking care of this!
>
> On Thu, Jan 10, 2019 at 4:40 PM Loys Ollivier wrote:
>>
>> Commit 89a5e15bcba8 ("gpio/mmc/of: Respect polarity in the device tree")
>> changed
Em Fri, 11 Jan 2019 19:17:31 +0100
Christoph Hellwig escreveu:
> vb2_dc_get_userptr pokes into arm direct mapping details to get the
> resemblance of a dma address for a a physical address that does is
> not backed by a page struct. Not only is this not portable to other
> architectures with
USB Bluetooth controller QCA ROME (0cf3:e007) sometimes stops working
after S3:
[ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_usb_0302.bin
[ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110)
After some experiments, I found that disabling LPM can workaround the
Use new helpers to make LPM enabling/disabling more clear.
This is a preparation to subsequent patch.
Signed-off-by: Kai-Heng Feng
---
v5:
- Split to two patches. The first one uses the new LPM helpers, the
second one consolidates the LPM checks to solve the issue.
v4:
- Use
On Fri, Jan 04, 2019 at 08:53:35AM -0800, Andrey Smirnov wrote:
> Add code needed to support i.MX8MQ variant.
>
> Cc: Bjorn Helgaas
> Cc: Fabio Estevam
> Cc: Chris Healy
> Cc: Lucas Stach
> Cc: Leonard Crestez
> Cc: "A.s. Dong"
> Cc: Richard Zhu
> Cc: Rob Herring ,
> Cc:
On Wed, 19 Dec 2018, Waiman Long wrote:
> With the default SPEC_STORE_BYPASS_SECCOMP/SPEC_STORE_BYPASS_PRCTL mode,
> the TIF_SSBD bit will be inherited when a new task is fork'ed or cloned.
>
> As only certain class of applications (like Java) requires disabling
> speculative store bypass for
On Fri, Jan 11, 2019 at 03:21:39PM +0100, Linus Walleij wrote:
> On Tue, Jan 8, 2019 at 7:02 PM Andy Shevchenko
> wrote:
>
> > New quirk enforces search for GPIO based on its type.
> > Note, supplied index in the mapping table must be 0.
> >
> > Signed-off-by: Andy Shevchenko
>
> (...)
>
> >
On Fri, Jan 11, 2019 at 11:28:19AM -0700, Khalid Aziz wrote:
> On 1/11/19 7:54 AM, Tycho Andersen wrote:
> > On Thu, Jan 10, 2019 at 02:09:39PM -0700, Khalid Aziz wrote:
> >> From: Juerg Haefliger
> >>
> >> If the page is unmapped by XPFO, a data cache flush results in a fatal
> >> page fault, so
On Fri, Jan 11, 2019 at 09:49:29PM +0200, Andy Shevchenko wrote:
> On Fri, Jan 11, 2019 at 03:21:39PM +0100, Linus Walleij wrote:
> I hope to get Hans' Tested-by on this.
Btw there is v2 of it with Mika's Ack (not enough, I know).
--
With Best Regards,
Andy Shevchenko
On 1/11/2019 12:45 PM, Rob Herring wrote:
On Fri, Jan 04, 2019 at 09:50:47AM -0700, Jeffrey Hugo wrote:
MSM8998 contains a single QMP v3 USB3 phy similar to the existing sdm845
support, however MSM8998 does not have display port (DP) support.
Signed-off-by: Jeffrey Hugo
---
Hi,
some nit-picks as well as my Tested-by (in case it's not too late) below.
thank you for taking care of this!
On Thu, Jan 10, 2019 at 4:40 PM Loys Ollivier wrote:
>
> Commit 89a5e15bcba8 ("gpio/mmc/of: Respect polarity in the device tree")
> changed the behavior of "cd-inverted" to follow
On Fri, Jan 04, 2019 at 09:50:47AM -0700, Jeffrey Hugo wrote:
> MSM8998 contains a single QMP v3 USB3 phy similar to the existing sdm845
> support, however MSM8998 does not have display port (DP) support.
>
> Signed-off-by: Jeffrey Hugo
> ---
> .../devicetree/bindings/phy/qcom-qmp-phy.txt
Hi Alexey,
> From: Alexey Khoroshilov [mailto:khoroshi...@ispras.ru]
> Sent: Saturday, December 22, 2018 9:55 PM
> To: Zhuangyuzeng (Yisen) ; Salil Mehta
> ; lipeng (Y)
> Cc: Alexey Khoroshilov ; David S. Miller
> ; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org;
There is possibility, that when probing driver, regulators are not yet
initialized. In this case we should return EPROBE_DEFER and wait till
they're initialized, since they're required currently for cpufreq driver
to work. Also move regulator initialization code at beginning of probe,
so we can
On Fri, 11 Jan 2019, h...@zytor.com wrote:
> I still don't see why can't simply spin in the #BP handler until the
> patch is complete.
I think this brings us to the already discussed possible deadlock, when
one CPU#0 is in the middle of text_poke_bp(), CPU#1 is spinning inside
The ability to add kerneldoc comments for fields in embedded structures is
useful, but it brought along a whole bunch of warnings for fields that
could not be described before. In many cases, there's little value in
adding docs for these nested fields, and in cases like:
struct a {
On Fri, 11 Jan 2019, Vito Caputo wrote:
> On Fri, Jan 11, 2019 at 01:33:09PM -0500, Nicolas Pitre wrote:
> > I use Linux with the help of a braille display and the brltty daemon. It
> > turns out that the latest mainline kernel I can work with comes from
> > commit 231f8fd0cc. Anything past
On Fri, Jan 11, 2019 at 11:24 AM wrote:
>
> I still don't see why can't simply spin in the #BP handler until the patch is
> complete.
So here's at least one problem:
text_poke_bp()
text_poke(addr, , sizeof(int3));
*interrupt*
interrupt has a static call
*BP*
Dmitry Vyukov writes:
> On Wed, Jan 2, 2019 at 5:09 PM Dmitry Vyukov wrote:
>>
>> On Tue, Dec 18, 2018 at 9:58 AM Sergey Senozhatsky
>> wrote:
>> >
>> > On (12/18/18 09:39), Petr Mladek wrote:
>> > >
>> > > Sergey, are you okay with this squashed patch, please?
>> > >
>> >
>> > Yeah. There are
> On Jan 11, 2019, at 11:23 AM, h...@zytor.com wrote:
>
> On January 11, 2019 11:03:30 AM PST, Linus Torvalds
> wrote:
>> On Fri, Jan 11, 2019 at 7:15 AM Josh Poimboeuf
>> wrote:
Now, in the int3 handler can you take the faulting RIP and search
>> for it in
the “static-calls” table,
This commit allow the driver to work with device-tree.
Signed-off-by: Sebastien Bourdelin
---
drivers/iio/chemical/bme680_i2c.c | 7 +++
drivers/iio/chemical/bme680_spi.c | 7 +++
2 files changed, 14 insertions(+)
diff --git a/drivers/iio/chemical/bme680_i2c.c
BME680 is a pressure/temperature/humidity/voc sensor.
Signed-off-by: Sebastien Bourdelin
---
.../devicetree/bindings/iio/chemical/bme680.txt | 11 +++
1 file changed, 11 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/chemical/bme680.txt
diff --git
On Fri, Jan 11, 2019 at 01:33:09PM -0500, Nicolas Pitre wrote:
> I use Linux with the help of a braille display and the brltty daemon. It
> turns out that the latest mainline kernel I can work with comes from
> commit 231f8fd0cc. Anything past that and I lose the ability to read the
> console
On Fri, 4 Jan 2019 11:05:59 +0800, Yunfei Dong wrote:
> Fix MTK binding document for MT8173 dtsi changed in order
> to use standard CCF interface.
> MT8173 SoC from Mediatek.
>
> Signed-off-by: Yunfei Dong
> Signed-off-by: Qianqian Yan
> ---
> change note:
> v2: modify subject
> ---
>
On Thu, 3 Jan 2019 23:40:23 -0200, Otavio Salvador wrote:
> rv1108-elgin-r1 board is based on Rockchip RV1108 SoC.
>
> Signed-off-by: Otavio Salvador
> ---
>
> .../devicetree/bindings/arm/rockchip.yaml | 5 +
> arch/arm/boot/dts/Makefile| 1 +
>
On Fri, Jan 11, 2019 at 11:14 AM Tri Vo wrote:
>
> From: George Rimar
>
> Linux kernel uses OUTPUT_FORMAT in it's linker scripts. Most of the time
> -m option is passed to the linker with correct architecture, but
> sometimes (at least for x86_64) the -m option contradicts OUTPUT_FORMAT
>
On 1/3/19 5:59 PM, Roman Penyaev wrote:
> __vmalloc_area_node() calls vfree() on error path, which in turn calls
> kmemleak_free(), but area is not yet accounted by kmemleak_vmalloc().
>
> Signed-off-by: Roman Penyaev
> Cc: Andrew Morton
> Cc: Michal Hocko
> Cc: Andrey Ryabinin
> Cc: Joe
On January 11, 2019 11:03:30 AM PST, Linus Torvalds
wrote:
>On Fri, Jan 11, 2019 at 7:15 AM Josh Poimboeuf
>wrote:
>>
>> >
>> > Now, in the int3 handler can you take the faulting RIP and search
>for it in
>> > the “static-calls” table, writing the RIP+5 (offset) into R10
>(return
>> > address)
> On Jan 11, 2019, at 10:44 AM, Arnaldo Carvalho de Melo
> wrote:
>
> Em Thu, Jan 10, 2019 at 04:19:33PM -0800, Song Liu escreveu:
>> This patch synthesize PERF_RECORD_KSYMBOL and PERF_RECORD_BPF_EVENT for
>> BPF programs loaded before perf-record. This is achieved by gathering
>>
On Fri, Jan 11, 2019 at 08:19:33PM +0100, Thomas Gleixner wrote:
> On Fri, 11 Jan 2019, Thomas Gleixner wrote:
> > --- a/kernel/irq/internals.h
> > +++ b/kernel/irq/internals.h
> > @@ -246,6 +246,7 @@ static inline void kstat_incr_irqs_this_
> > {
> > __this_cpu_inc(*desc->kstat_irqs);
> >
> On Jan 11, 2019, at 11:03 AM, Linus Torvalds
> wrote:
>
> On Fri, Jan 11, 2019 at 7:15 AM Josh Poimboeuf wrote:
>>> Now, in the int3 handler can you take the faulting RIP and search for it in
>>> the “static-calls” table, writing the RIP+5 (offset) into R10 (return
>>> address) and the
On Fri, 11 Jan 2019, Thomas Gleixner wrote:
> --- a/kernel/irq/internals.h
> +++ b/kernel/irq/internals.h
> @@ -246,6 +246,7 @@ static inline void kstat_incr_irqs_this_
> {
> __this_cpu_inc(*desc->kstat_irqs);
> __this_cpu_inc(kstat.irqs_sum);
> + desc->tot_count++;
There is one
On 1/3/19 5:59 PM, Roman Penyaev wrote:
> vmalloc_user*() calls differ from normal vmalloc() only in that they
> set VM_USERMAP flags for the area. During the whole history of
> vmalloc.c changes now it is possible simply to pass VM_USERMAP flags
> directly to __vmalloc_node_range() call
On 1/3/19 5:59 PM, Roman Penyaev wrote:
> area->size can include adjacent guard page but get_vm_area_size()
> returns actual size of the area.
>
> This fixes possible kernel crash when userspace tries to map area
> on 1 page bigger: size check passes but the following vmalloc_to_page()
>
From: George Rimar
Linux kernel uses OUTPUT_FORMAT in it's linker scripts. Most of the time
-m option is passed to the linker with correct architecture, but
sometimes (at least for x86_64) the -m option contradicts OUTPUT_FORMAT
directive. Specifically, arch/x86/boot and arch/x86/realmode/rm
The RFC5869 compliant Key Derivation Function is implemented as a
random number generator considering that it behaves like a deterministic
RNG.
The extract and expand phases use different instances of the underlying
keyed message digest cipher to ensure that while the extraction phase
generates a
Hi Herbert, Eric,
key derivation functions behave like a random number generator requiring
a seed and can generate arbitrarily-sized bit sequences. As KDFs wrap
ciphers, the first patch adds template support for the RNG part of the
kernel crypto API. This allows the KDFs to be implemented as
Add known answer tests to the testmgr for the KDF (SP800-108) cipher.
Signed-off-by: Stephan Mueller
---
crypto/testmgr.c | 226 +++
crypto/testmgr.h | 110 +++
2 files changed, 336 insertions(+)
diff --git a/crypto/testmgr.c
The SP800-108 compliant Key Derivation Function is implemented as a
random number generator considering that it behaves like a deterministic
RNG.
All three KDF types specified in SP800-108 are implemented.
The code comments provide details about how to invoke the different KDF
types.
Add known answer tests to the testmgr for the HKDF (RFC5869) cipher.
The known answer tests are derived from RFC 5869 appendix A.
Note, the HKDF is considered to be a FIPS 140-2 allowed (not approved)
cipher as of now. Yet, an allowed cipher is usable under FIPS 140-2
rules.
Signed-off-by:
Add ability to register templates for RNGs. RNGs are
"meta" mechanisms using raw cipher primitives. Thus, RNGs can now be
implemented as templates to allow the complete flexibility the kernel
crypto API provides.
Signed-off-by: Stephan Mueller
---
crypto/rng.c | 44
Enable testing of the SP800-108 and RFC5869 KDFs.
Signed-off-by: Stephan Mueller
---
crypto/tcrypt.c | 8
1 file changed, 8 insertions(+)
diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c
index e7fb87e114a5..5606e59e80ec 100644
--- a/crypto/tcrypt.c
+++ b/crypto/tcrypt.c
@@ -2054,6
On Tue, Jan 08, 2019 at 01:05:43PM +, Viorel Suman wrote:
> The patchset adds NXP Audio Mixer (AUDMIX) device and machine
> drivers and related DT bindings documentation.
>
> Changes since V1:
> 1. Original patch split into distinct patches for the device driver and
> DT binding
On Fri, Jan 11, 2019 at 01:33:09PM -0500, Nicolas Pitre wrote:
> I use Linux with the help of a braille display and the brltty daemon. It
> turns out that the latest mainline kernel I can work with comes from
> commit 231f8fd0cc. Anything past that and I lose the ability to read the
> console
On Sat 12-01-19 02:55:13, Yang Shi wrote:
> mem_cgroup_is_root() is preferred API to check if memcg is root or not.
> Use it instead of deferencing css->parent.
>
> Cc: Huang Ying
> Cc: Tim Chen
> Signed-off-by: Yang Shi
Yes, this is more readable.
Acked-by: Michal Hocko
> ---
>
201 - 300 of 1414 matches
Mail list logo
