On Fri, Jan 26, 2018 at 10:41:58AM +0800, Jason Wang wrote:
>
>
> On 2018年01月26日 01:11, Michael S. Tsirkin wrote:
> > On Thu, Jan 25, 2018 at 09:49:22AM -0500, Paolo Bonzini wrote:
> > > > > Michael and Jason, any progress on implementing a fast virtio
> > > > > mechanism
> > > > > that doesn't
On Thu, Jan 25, 2018 at 06:46:49PM -0800, Joel Fernandes wrote:
> ashmem_mutex create a chain of dependencies like so:
>
> (1)
> mmap syscall ->
> mmap_sem -> (acquired)
> ashmem_mmap
> ashmem_mutex (try to acquire)
> (block)
>
> (2)
> llseek syscall ->
> ashmem_llseek ->
>
On 01/25/2018 09:03 PM, Baolin Wang wrote:
The kdb code will print the monotonic time by ktime_get_ts(), but
the ktime_get_ts() will be protected by a sequence lock, that will
introduce one deadlock risk if the lock was already held in the
context from which we entered the debugger.
Since kdb
Hi Simon and Dmitry,
On Wed, Jan 24, 2018 at 11:38:03AM -0800, Dmitry Torokhov wrote:
> From: Simon Shields
>
> The MMS114 platform data has no in-tree users, so drop it.
>
> Switch to using the standard touchscreen properties via
> touchscreen_parse_properties(), and move
If we convert one large time values to rtc_time, in the original formula
'days * 86400' can be overflowed in 'unsigned int' type to make the formula
get one incorrect remain seconds value. Thus we can use div_s64_rem()
function to avoid this situation.
Signed-off-by: Baolin Wang
Thanks,
applied to nvme-4.16.
On Wed, Jan 24, 2018 at 05:42:15PM +0200, Andy Shevchenko wrote:
> On Wed, Jan 24, 2018 at 3:07 PM, Ludovic Desroches
> wrote:
> > On Thu, Jan 18, 2018 at 04:22:28PM +0100, Ludovic Desroches wrote:
> >> On Thu, Jan 18, 2018 at 11:30:00AM +0100, Linus Walleij
On 01/25/2018 09:49 PM, Michael S. Tsirkin wrote:
On Thu, Jan 25, 2018 at 05:14:06PM +0800, Wei Wang wrote:
+
+static void report_free_page_func(struct work_struct *work)
+{
+ struct virtio_balloon *vb;
+ int ret;
+
+ vb = container_of(work, struct virtio_balloon,
On 2018/1/26 7:46, Hyunchul Lee wrote:
> On 01/25/2018 05:01 PM, Chao Yu wrote:
>> Hi Hyunchul,
>>
>> On 2018/1/25 10:47, Hyunchul Lee wrote:
>>> Hi Chao,
>>>
>>> On 01/25/2018 12:32 AM, Chao Yu wrote:
On 2018/1/22 18:49, Hyunchul Lee wrote:
> From: Hyunchul Lee
>
On 01/26/2018 06:41 AM, Andrew Morton wrote:
On Thu, 25 Jan 2018 17:38:27 +0800 Wei Wang wrote:
This patch adds support to walk through the free page blocks in the
system and report them via a callback function. Some page blocks may
leave the free list after zone->lock
On Fri, Jan 26, 2018 at 12:54:02AM +0100, Mickaël Salaün wrote:
> Make the code more readable.
>
> Signed-off-by: Mickaël Salaün
> Cc: Alexei Starovoitov
> Cc: Daniel Borkmann
> ---
> kernel/bpf/syscall.c | 5 +
> 1 file changed, 1
Hi Tyler,
On 2018/1/26 1:11, Tyler Baicar wrote:
> For this series - Tested-by: Tyler Baicar
>
> Note that this will probably need to be rebased on top of these patches:
Thank you for your testing, I'll rebase then.
>
> https://patchwork.codeaurora.org/patch/415877/
>
On 01/25/2018 06:11 PM, Liran Alon wrote:
> It is true that attacker cannot speculate to a kernel-address, but it
> doesn't mean it cannot use the leaked kernel-address together with
> another unrelated vulnerability to build a reliable exploit.
The address doesn't leak if you can't execute
> -Original Message-
> From: Liran Alon [mailto:liran.a...@oracle.com]
> Sent: Thursday, January 25, 2018 6:50 PM
> To: Hansen, Dave
> Cc: labb...@redhat.com; l...@kernel.org; janakarajan.natara...@amd.com;
> torva...@linux-foundation.org; b...@suse.de; Mallick,
On 2018年01月26日 10:44, Michael S. Tsirkin wrote:
On Fri, Jan 26, 2018 at 10:37:58AM +0800, Jason Wang wrote:
On 2018年01月26日 07:36, Michael S. Tsirkin wrote:
Lockless __ptr_ring_empty requires that consumer head is read and
written at once, atomically. Annotate accordingly to make sure
After checking all possible call chains to atmtcp_v_send() here,
my tool finds that atmtcp_v_send() is never called in atomic context.
And this function is assigned to a function pointer "dev->ops->send",
which is only called by vcc_sendmsg() (net/atm/common.c)
through vcc->dev->ops->send(), and
After checking all possible call chains to psend() here,
my tool finds that psend() is never called in atomic context.
And this function is assigned to a function pointer "dev->ops->send",
which is only called by vcc_sendmsg (net/atm/common.c)
through vcc->dev->ops->send(), and vcc_sendmsg calls
On Fri, Jan 19, 2018 at 05:11:02PM +0100, Jiri Olsa wrote:
> Current kallsyms__parse uses hex2u64, which gives
> no indication of error. Using strtoul to checkup
> on failed attempt to parse the number and stop the
> rest of the kallsyms__parse processing early.
>
> Link:
This boolean property for the GIC-V3-ITS enables resending the MAP
COLLECTIONS commands when resuming for when the state is reset on
suspend.
Signed-off-by: Derek Basehore
---
Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 4
1 file changed,
This adds functionality to resend the MAPC command to an ITS node on
resume. If the ITS is powered down during suspend and the collections
are not backed by memory, the ITS will lose that state. This just sets
up the known state for the collections after the ITS is restored.
This feature is
-Original Message-
From: Dong Aisheng [mailto:donga...@gmail.com]
Sent: 2018年1月26日 15:00
To: Anson Huang
Cc: rui.zh...@intel.com; edubez...@gmail.com; robh...@kernel.org;
mark.rutl...@arm.com; shawn...@kernel.org; ker...@pengutronix.de; Fabio Estevam
This adds documentation for the new reset-on-suspend property. This
property enables saving and restoring the ITS for when it loses state
in system suspend.
Signed-off-by: Derek Basehore
---
Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 3 +++
1
On 01/19/18 at 12:47pm, Dave Young wrote:
> On 01/18/18 at 01:57pm, Steven Rostedt wrote:
> > On Thu, 18 Jan 2018 10:02:17 -0800
> > Andi Kleen wrote:
> >
> > > Dave Young writes:
> > > > printk("%sHardware name: %s\n",
> > > >
A lot of changes in v2. The distributor and redistributor saving and
restoring is left to the PSCI/firmware implementation after
discussions with ARM. This reduces the line changes by a lot and
removes now unneeded patches.
Patches are verified on an RK3399 platform with pending patches in the
If cpu_cluster_pm_enter() fails, cpu_pm_exit() should be called. This
will put the CPU in the correct state to resume from the failure.
Signed-off-by: Derek Basehore
---
kernel/cpu_pm.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/cpu_pm.c
Some platforms power off GIC logic in suspend, so we need to
save/restore state. The distributor and redistributor registers need
to be handled in platform code due to access permissions on those
registers, but the ITS registers can be restored in the kernel.
Signed-off-by: Derek Basehore
On Fri, Jan 26, 2018 at 4:24 AM, Jason Wang wrote:
>
>
> On 2018年01月25日 15:59, syzbot wrote:
>>
>> Hello,
>>
>> syzbot hit the following crash on net-next commit
>> 43df215d99e6049d4680309c54232689e16ddd6b (Wed Jan 24 01:24:32 2018 +)
>> Merge branch
Hi Maxime,
Do you have any experience in solving this problem?
It seems the PHYS_OFFSET maybe undeclared when the ARCH is not arm.
On Fri, 26 Jan 2018 08:04:18 +0800
kbuild test robot wrote:
> Hi Yong,
>
> I love your patch! Yet something to improve:
>
> [auto build test
On Fri, Jan 26, 2018 at 01:39:30AM +0100, Mickaël Salaün wrote:
> Do not build lib/bpf/bpf.o with this Makefile but use the one from the
> library directory. This avoid making a buggy bpf.o file (e.g. missing
> symbols).
could you provide an example?
What symbols will be missing?
I don't think
On Fri, 2018-01-26 at 02:20 +0100, Adam Borowski wrote:
> On Thu, Jan 25, 2018 at 06:29:53PM -0500, Lyude Paul wrote:
> > This was made apparent by what appeared to be a regression in the
> > mainline kernel that started introducing suspend/resume issues for
> > nouveau:
> >
> >
On 2018年01月26日 07:36, Michael S. Tsirkin wrote:
Similar to bcecb4bbf88a ("net: ptr_ring: otherwise safe empty checks can
overrun array bounds") a lockless use of __ptr_ring_full might
cause an out of bounds access.
We can fix this, but it's easier to just disallow lockless
__ptr_ring_full for
On Fri, Jan 26, 2018 at 10:38:12AM +0800, Jason Wang wrote:
>
>
> On 2018年01月26日 07:36, Michael S. Tsirkin wrote:
> > In theory compiler could tear queue loads or stores in two. It does not
> > seem to be happening in practice but it seems easier to convert the
> > cases where this would be a
On 01/25/18 at 06:50pm, Kirill A. Shutemov wrote:
> On Wed, Jan 17, 2018 at 01:24:54PM +0800, Baoquan He wrote:
> > Hi Kirill,
> >
> > I setup qemu 2.9.0 to test 5-level on kexec/kdump support. While both
> > kexec and kdump reset to BIOS immediately after triggering. I saw your
> > patch adding
Hi all,
Changes since 20180119:
The powerpc tree lost its build failures.
The f2fs tree still had its build failure due to an interaction with
the btrfs tree for which I reverted a commit.
The vfs tree gained a conflict against the overlayfs tree.
The iversion tree gained a conflict against
On Jan 25, 2018, at 06:51, Eremin, Dmitry wrote:
>
> The logic of the original commit 4d99b2581eff ("staging: lustre: avoid
> intensive reconnecting for ko2iblnd") was assumed conditional free of
> struct kib_conn if the second argument free_conn in function
>
On Wed, Jan 24, 2018 at 08:10:53PM +0100, Jann Horn wrote:
> I'm not entirely convinced by the approach of marking small parts of
> kernel memory as readonly for hardening.
It depends how significant the data stored in there are. For example,
storing function pointers in read-only memory
This test verifies that the AMR, IAMR and UAMOR are being written to a
process' core file.
Signed-off-by: Thiago Jung Bauermann
---
tools/testing/selftests/powerpc/ptrace/Makefile| 5 +-
tools/testing/selftests/powerpc/ptrace/core-pkey.c | 460
This test exercises read and write access to the AMR, IAMR and UAMOR.
Signed-off-by: Thiago Jung Bauermann
---
tools/testing/selftests/powerpc/include/reg.h | 1 +
tools/testing/selftests/powerpc/ptrace/Makefile| 5 +-
On Mon, Jan 22, 2018 at 03:25:49PM +0800, Anson Huang wrote:
> This patch adds i.MX7 thermal sensor support, most
> of the i.MX7 thermal sensor functions are same with
> i.MX6 except the registers offset/layout, so we move
> those registers offset/layout definitions to soc data
> structure.
>
>
Hallo,
Sind Sie in einer schwierigen Situation, für die Sie sich für ein
Darlehen suchen? Benötigen Sie eine Finanzierung, um eine Schuld zu
begleichen oder eine Aktivität zu finanzieren? Haben Sie einen
Verbraucherkredit, eine Hypothek, einen persönlichen Kredit, eine
Hypothek, Investition
After checking all possible call chains to fs_send() here,
my tool finds that fs_send() is never called in atomic context.
And this function is assigned to a function pointer "dev->ops->send",
which is only called by vcc_sendmsg() (net/atm/common.c)
through vcc->dev->ops->send(), and vcc_sendmsg()
Hi leilei.lin,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.15-rc9 next-20180119]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Andrew,
On Thu, 25 Jan 2018 16:21:33 -0800 a...@linux-foundation.org wrote:
>
> * include-linux-mtd-rawnandh-fix-build-with-gcc-444.patch
This one clashed with a similar (but not identical) commit in another
tree, so I dropped it.
> *
On Fri, Jan 26, 2018 at 10:37:58AM +0800, Jason Wang wrote:
>
>
> On 2018年01月26日 07:36, Michael S. Tsirkin wrote:
> > Lockless __ptr_ring_empty requires that consumer head is read and
> > written at once, atomically. Annotate accordingly to make sure compiler
> > does it correctly. Switch
On 2018年01月26日 10:49, Michael S. Tsirkin wrote:
On Fri, Jan 26, 2018 at 10:41:58AM +0800, Jason Wang wrote:
On 2018年01月26日 01:11, Michael S. Tsirkin wrote:
On Thu, Jan 25, 2018 at 09:49:22AM -0500, Paolo Bonzini wrote:
Michael and Jason, any progress on implementing a fast virtio mechanism
From: Dong Bo
This fixs the following comile warnings with ATA_DEBUG enabled,
which detected by Linaro GCC 5.2-2015.11:
In file included from ./include/linux/printk.h:7:0,
from ./include/linux/kernel.h:14,
from
On 2018年01月26日 07:36, Michael S. Tsirkin wrote:
This fixes a bunch of issues around ptr_ring use in net core.
One of these: "tap: fix use-after-free" is also needed on net,
but can't be backported cleanly.
I will post a net patch separately.
Lightly tested - Jason, could you pls confirm this
On 2018-01-25 01:48, Corey Minyard wrote:
On 01/24/2018 10:06 AM, Haiyue Wang wrote:
The KCS (Keyboard Controller Style) interface is used to perform in-band
IPMI communication between a server host and its BMC (BaseBoard
Management
Controllers).
This driver exposes the KCS interface on
On Wed, Jan 24, 2018 at 1:37 AM, Mark Brown wrote:
> On Tue, Jan 23, 2018 at 07:08:15PM +0200, Andy Shevchenko wrote:
>
>> If it's not critical, I would suggest to wait till v4.16-rc1, where I
>> would like to push [1], and switch to DEFINE_SHOW_ATTRIBUTE() macro.
>
> Too
On 25 January 2018 at 23:12, Arnd Bergmann wrote:
> On Thu, Jan 25, 2018 at 3:49 PM, Jason Wessel
> wrote:
>> On 01/25/2018 05:38 AM, Daniel Thompson wrote:
>>>
>>> On Thu, Jan 25, 2018 at 05:18:54PM +0800, Baolin Wang wrote:
On 25 January
After checking all possible call chains to fore200e_open here,
my tool finds that fore200e_open is never called in atomic context.
And fore200e_open calls mutex_lock which can sleep later,
thus it is supposed fore200e_open can call functions which may sleep.
Thus GFP_ATOMIC is not necessary, and
After checking all possible call chains to fore200e_send here,
my tool finds that fore200e_send is never called in atomic context.
And this function is assigned to a function pointer "dev->ops->send",
which is only called by vcc_sendmsg (net/atm/common.c)
through vcc->dev->ops->send, and
On 01/25/2018 03:29 AM, Arnd Bergmann wrote:
> On Thu, Jan 25, 2018 at 4:27 AM, Taras Kondratiuk wrote:
>> Many of the Linux security/integrity features are dependent on file
>> metadata, stored as extended attributes (xattrs), for making decisions.
>> These features need to
On 2018年01月26日 07:36, Michael S. Tsirkin wrote:
Lockless __ptr_ring_empty requires that consumer head is read and
written at once, atomically. Annotate accordingly to make sure compiler
does it correctly. Switch locked callers to __ptr_ring_peek which does
not support the lockless operation.
On 2018年01月26日 07:36, Michael S. Tsirkin wrote:
In theory compiler could tear queue loads or stores in two. It does not
seem to be happening in practice but it seems easier to convert the
cases where this would be a problem to READ/WRITE_ONCE than worry about
it.
Signed-off-by: Michael S.
- dave.han...@intel.com wrote:
> On 01/25/2018 06:11 PM, Liran Alon wrote:
> > It is true that attacker cannot speculate to a kernel-address, but
> it
> > doesn't mean it cannot use the leaked kernel-address together with
> > another unrelated vulnerability to build a reliable exploit.
>
>
On 01/25/2018 09:41 PM, Michael S. Tsirkin wrote:
On Wed, Jan 24, 2018 at 06:42:41PM +0800, Wei Wang wrote:
This patch adds support to walk through the free page blocks in the
system and report them via a callback function. Some page blocks may
leave the free list after zone->lock is released,
On 2018年01月26日 01:31, Michael S. Tsirkin wrote:
On Thu, Jan 25, 2018 at 10:17:38PM +0800, Jason Wang wrote:
On 2018年01月25日 21:45, Michael S. Tsirkin wrote:
On Thu, Jan 25, 2018 at 03:31:42PM +0800, Jason Wang wrote:
We try to allocate one more entry for lockless peeking. The adding
Hi Jeremy,
On 2018/1/25 23:56, Jeremy Linton wrote:
> Hi,
>
> On 01/25/2018 06:15 AM, Xiongfeng Wang wrote:
>> Hi Jeremy,
>>
>> I have tested the patch with the newest UEFI. It prints the below error:
>>
>> [4.017371] BUG: arch topology borken
>> [4.021069] BUG: arch topology borken
>> [
On Thu, 25 Jan 2018 16:42:31 +
Will Deacon wrote:
> On Thu, Jan 25, 2018 at 02:29:32PM +0900, Masami Hiramatsu wrote:
> > Fix %p uses in error messages by removing it because
> > those are redundant or meaningless.
> >
> > Signed-off-by: Masami Hiramatsu
Howdy. Here is your bi-weekly request API redesign! ;)
Again, this is a simple version that only implements the flow of requests,
without applying controls. The intent is to get an agreement on a base to work
on, since the previous versions went straight back to the redesign board.
Highlights of
On Thu, Jan 25, 2018 at 02:44:59PM -0800, Srinivas Pandruvada wrote:
> On Thu, 2018-01-25 at 19:08 +0800, Yu Chen wrote:
>
> Thanks for debugging.
>
> > The following warning was triggered after resumed from S3 -
> > if all the nonboot CPUs were put offline before suspend:
> >
> > [
In the commit 05f80300dc8b ("iommu: Finish making iommu_group support
mandatory"), the iommu framework has supposed all the iommu drivers have
their owner iommu-group, it get rid of the FIXME workarounds while the
group is NULL. But the flow of Mediatek M4U gen1 looks a bit trick that
it will hang
On Thu, Jan 25, 2018 at 08:23:15AM -0800, Palmer Dabbelt wrote:
> Now that we're upstream in Linux we've been able to make some
> infrastructure changes so our port works a bit more like other ports.
> Specifically:
>
> * We now have a mailing list specific to the RISC-V Linux port, hosted
> at
On Wed, Jan 24, 2018 at 12:04:58PM -0800, Florian Fainelli wrote:
> This looks nicer than the current shape, but this still requires to
> register a PCI fixup to override phys_to_dma() and dma_to_phys(), and it
> would appear that you have dodged my question about how this is supposed
> to fit
On Fri, Jan 26, 2018 at 09:40:44AM +0800, Wei Wang wrote:
> On 01/25/2018 09:49 PM, Michael S. Tsirkin wrote:
> > On Thu, Jan 25, 2018 at 05:14:06PM +0800, Wei Wang wrote:
> > > +
> > > +static void report_free_page_func(struct work_struct *work)
> > > +{
> > > + struct virtio_balloon *vb;
> > > +
On 2018年01月26日 01:11, Michael S. Tsirkin wrote:
On Thu, Jan 25, 2018 at 09:49:22AM -0500, Paolo Bonzini wrote:
Michael and Jason, any progress on implementing a fast virtio mechanism
that doesn't rely on undefined behavior?
(Encode writing instruction length into last 4 bits of MMIO address,
On 01/24/2018 09:27 PM, Taras Kondratiuk wrote:
> diff --git a/usr/gen_init_cpio.c b/usr/gen_init_cpio.c
> index 7a2a6d85345d..78a47a5bdcb1 100644
> --- a/usr/gen_init_cpio.c
> +++ b/usr/gen_init_cpio.c
> @@ -10,6 +10,7 @@
> #include
> #include
> #include
> +#include
You're adding an
On 01/24/2018 09:27 PM, Taras Kondratiuk wrote:
> diff --git a/Documentation/early-userspace/buffer-format.txt
> b/Documentation/early-userspace/buffer-format.txt
> index e1fd7f9dad16..d818df4f72dc 100644
> --- a/Documentation/early-userspace/buffer-format.txt
> +++
Hi Maxime,
On Fri, 26 Jan 2018 09:46:58 +0800
Yong wrote:
> Hi Maxime,
>
> Do you have any experience in solving this problem?
> It seems the PHYS_OFFSET maybe undeclared when the ARCH is not arm.
Got it.
Should I add 'depends on ARM' in Kconfig?
>
> On Fri, 26 Jan
This enables BLCG optimization for kepler1. When using clockgating,
nvidia's firmware has a set of registers which are initially programmed
by the vbios with various engine delays and other mysterious settings
that are safe enough to bring up the GPU. However, the values used by
the vbios are more
Same as the previous patch, but for Kepler2 now
Signed-off-by: Lyude Paul
---
drivers/gpu/drm/nouveau/include/nvkm/subdev/fb.h | 1 +
drivers/gpu/drm/nouveau/nvkm/engine/device/base.c | 8 +--
drivers/gpu/drm/nouveau/nvkm/engine/gr/gk110.c| 62
This adds support for enabling automatic clockgating on nvidia GPUs for
Kepler1. While this is not technically a clockgating level, it does
enable clockgating using the clockgating values initially set by the
vbios (which should be safe to use).
This introduces two therm helpers for controlling
Next version of my patchseries for adding clockgating support for
kepler1 and 2 on nouveau. The first version of this series can be found
here:
https://patchwork.freedesktop.org/series/36504/
Some minor changes:
- Clarified that SLCG stands for 'secondary level clockgating', thanks
for the
Hi Dmitry,
On Wed, Jan 24, 2018 at 11:38:02AM -0800, Dmitry Torokhov wrote:
> mms14 is a touchscreen and thus a direct input device; let's mark it
> as such. This also allows us to drop some initialization code as
> input_init_mt_slots() will do that for us.
>
> Also add error handling for
Hi Dmitry,
On Wed, Jan 24, 2018 at 11:38:01AM -0800, Dmitry Torokhov wrote:
> Rely on the platform (device tree, ACPI, etc) to properly configure
> interrupt trigger/polarity instead of hardcoding the falling edge.
>
> Signed-off-by: Dmitry Torokhov
Reviewed-by: Andi
On 2018-01-25 01:48, Corey Minyard wrote:
On 01/24/2018 10:06 AM, Haiyue Wang wrote:
The KCS (Keyboard Controller Style) interface is used to perform in-band
IPMI communication between a server host and its BMC (BaseBoard
Management
Controllers).
This driver exposes the KCS interface on
On Thu, Jan 25, 2018 at 06:29:53PM -0500, Lyude Paul wrote:
> This was made apparent by what appeared to be a regression in the
> mainline kernel that started introducing suspend/resume issues for
> nouveau:
>
> a0c9259dc4e1 (irq/matrix: Spread interrupts on allocation)
I'm just a dumb
On 2018年01月25日 15:59, syzbot wrote:
Hello,
syzbot hit the following crash on net-next commit
43df215d99e6049d4680309c54232689e16ddd6b (Wed Jan 24 01:24:32 2018 +)
Merge branch 'bpf-and-netdevsim-test-updates'
So far this crash happened 2 times on net-next.
Unfortunately, I don't have any
After checking all possible call chains to idt77252_preset() here,
my tool finds that idt77252_preset() is never called in atomic context,
namely never in an interrupt handler or holding a spinlock.
And idt77252_preset() calls deinit_card, which calls free_irq (can sleep),
so it indicates that
That's right, there's still more power saving to go! Starting with
kepler 2, nvidia hardware has an additional level of clockgating known
as second level clockgating. The details of this are not exact, but it
seems to work by waiting for a collection of dependent hardware blocks
to be gated
Hi Simon and Dmitry,
On Wed, Jan 24, 2018 at 01:32:01PM -0800, Dmitry Torokhov wrote:
> From: Simon Shields
>
> MMS152 has no configuration registers, but the packet format used in
> interrupts is identical to mms114.
>
> Signed-off-by: Simon Shields
On 2018-01-25 01:05, Andy Shevchenko wrote:
On Thu, 2018-01-25 at 00:06 +0800, Haiyue Wang wrote:
The KCS (Keyboard Controller Style) interface is used to perform in-
band
IPMI communication between a server host and its BMC (BaseBoard
Management
Controllers).
+config ASPEED_KCS_IPMI_BMC
+
From: Hans Verkuil
When queuing buffers allow for passing the request ID that
should be associated with this buffer.
Signed-off-by: Hans Verkuil
[acour...@chromium.org: make request ID 32-bit]
Signed-off-by: Alexandre Courbot
Make vb2 aware of requests. Drivers can specify whether a given queue
can accept requests or not. Queues that accept requests will block on a
buffer that is part of a request until that request is submitted.
Signed-off-by: Alexandre Courbot
---
Set the necessary ops for supporting requests in vim2m.
Signed-off-by: Alexandre Courbot
---
drivers/media/platform/vim2m.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/drivers/media/platform/vim2m.c b/drivers/media/platform/vim2m.c
Request API requires a media node. Add one to the vim2m driver so we can
use requests with it.
Signed-off-by: Alexandre Courbot
---
drivers/media/platform/vim2m.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/media/platform/vim2m.c
Document how the request API can be used along with the existing V4L2
interface.
Signed-off-by: Alexandre Courbot
---
Documentation/media/uapi/v4l/buffer.rst | 10 +-
Documentation/media/uapi/v4l/common.rst | 1 +
Documentation/media/uapi/v4l/request-api.rst
Support the request argument of the QBUF ioctl.
Signed-off-by: Alexandre Courbot
---
drivers/media/v4l2-core/v4l2-ioctl.c | 79 +++-
1 file changed, 78 insertions(+), 1 deletion(-)
diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c
From: Laurent Pinchart
The media request API is made of a new ioctl to implement request
management. Document it.
Signed-off-by: Laurent Pinchart
[acour...@chromium.org: adapt for newest API]
Signed-off-by:
-Original Message-
From: Dong Aisheng [mailto:donga...@gmail.com]
Sent: 2018年1月25日 23:30
To: Anson Huang
Cc: shawn...@kernel.org; ker...@pengutronix.de; Fabio Estevam
; robh...@kernel.org; A.s. Dong ;
On Fri, 26 Jan 2018, Wanpeng Li wrote:
Folks, can you please stop this corporate email style nonsense?
> On 1/26/18 12:55 AM, Arisetty, Chakravarthy wrote:
> >> IIRC,the race which KVM: LAPIC: Fix reentrancy issues with preempt
> >>
On Fri, Jan 19, 2018 at 05:11:03PM +0100, Jiri Olsa wrote:
> Current perf report is real slow on newer kernels,
> with following commit:
> c0f3ea158939 ("stop using '%pK' for /proc/kallsyms pointer values")
>
> which prevent pointers in /proc/kallsyms, in case
> kernel.perf_event_paranoid=2.
>
On Wed, Jan 24, 2018 at 06:14:39PM +0100, Sebastian Reichel wrote:
> Traditionally, PORTSC should be set before initializing ULPI phys. But
> setting PORTSC before powering on the phy results in a kernel freeze
> on imx53 based GE PPD. As a workaround this initializes the phy early
> in the imx
On 01/23/18 at 06:20pm, Weilong Chen wrote:
> Hi,
>
> We came across this problem:
> Second kernel hang with intel_iommu=on
>
> We can reproduce the problem by the following steps:
> 1. start the kernel with intel_iommu=on
> 2. ifconfig eth6 up;ifconfig eth8 up.(eth6 is Intel Corporation 82599ES
- dave.han...@intel.com wrote:
> On 01/23/2018 03:13 AM, Liran Alon wrote:
> > Therefore, breaking KASLR. In order to handle this, every exit from
> > kernel-mode to user-mode should stuff RSB. In addition, this
> stuffing
> > of RSB may need to be done from a fixed address to avoid leaking
ashmem_mutex create a chain of dependencies like so:
(1)
mmap syscall ->
mmap_sem -> (acquired)
ashmem_mmap
ashmem_mutex (try to acquire)
(block)
(2)
llseek syscall ->
ashmem_llseek ->
ashmem_mutex -> (acquired)
inode_lock ->
inode->i_rwsem (try to acquire)
(block)
(3)
Stephen Rothwell writes:
> Hi Eric,
>
> After merging the userns tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> arch/powerpc/kernel/mce.c: In function 'machine_process_ue_event':
> arch/powerpc/kernel/mce.c:276:5: error: too many arguments to
On Fri, Jan 26, 2018 at 10:38:05AM +0800, Jason Wang wrote:
>
>
> On 2018年01月26日 07:36, Michael S. Tsirkin wrote:
> > Similar to bcecb4bbf88a ("net: ptr_ring: otherwise safe empty checks can
> > overrun array bounds") a lockless use of __ptr_ring_full might
> > cause an out of bounds access.
> >
The kdb code will print the monotonic time by ktime_get_ts(), but
the ktime_get_ts() will be protected by a sequence lock, that will
introduce one deadlock risk if the lock was already held in the
context from which we entered the debugger.
Since kdb is only interested in the second field, we can
1 - 100 of 1498 matches
Mail list logo