2018-04-13 21:21 GMT+09:00 Masahiro Yamada :
> 2018-04-13 14:52 GMT+09:00 Kees Cook :
>> On Thu, Apr 12, 2018 at 10:06 PM, Masahiro Yamada
>> wrote:
>>> [Major Changes in V3]
>>
>> Awesome work! I don't see this
2018-04-13 21:21 GMT+09:00 Masahiro Yamada :
> 2018-04-13 14:52 GMT+09:00 Kees Cook :
>> On Thu, Apr 12, 2018 at 10:06 PM, Masahiro Yamada
>> wrote:
>>> [Major Changes in V3]
>>
>> Awesome work! I don't see this pushed to your git tree? I'd like to
>> test it, but I'd rather "git fetch" instead
Hi Linus,
Please pull dmi subsystem updates/fixes for Linux v4.17 from:
git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git dmi-for-linus
drivers/firmware/dmi_scan.c | 16
include/linux/mod_devicetable.h | 1 +
2 files changed, 13 insertions(+), 4
Hi Linus,
Please pull dmi subsystem updates/fixes for Linux v4.17 from:
git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git dmi-for-linus
drivers/firmware/dmi_scan.c | 16
include/linux/mod_devicetable.h | 1 +
2 files changed, 13 insertions(+), 4
Both buffer Transfer Length (TLEN if any) and transfer size have to be
aligned on burst size (burst beats*bus width).
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v1:
* Initial
v2:
v3:
* Get rid of while loop in favor of computed
Both buffer Transfer Length (TLEN if any) and transfer size have to be
aligned on burst size (burst beats*bus width).
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v1:
* Initial
v2:
v3:
* Get rid of while loop in favor of computed values
---
---
On 12/04/2018 17:25, Vitaly Kuznetsov wrote:
> @@ -5335,6 +5353,9 @@ static void __always_inline
> vmx_disable_intercept_for_msr(unsigned long *msr_bit
> if (!cpu_has_vmx_msr_bitmap())
> return;
>
> + if (static_branch_unlikely(_emsr_bitmap))
> +
On 12/04/2018 17:25, Vitaly Kuznetsov wrote:
> @@ -5335,6 +5353,9 @@ static void __always_inline
> vmx_disable_intercept_for_msr(unsigned long *msr_bit
> if (!cpu_has_vmx_msr_bitmap())
> return;
>
> + if (static_branch_unlikely(_emsr_bitmap))
> +
Only 1 Hw Descriptor is allocated. Loop over required Hw descriptor for
proper allocation.
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v1:
* Initial
v2:
* Fix kbuild warning format: /0x%08x/%pad/
v3:
* use of "offsetof"
Only 1 Hw Descriptor is allocated. Loop over required Hw descriptor for
proper allocation.
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v1:
* Initial
v2:
* Fix kbuild warning format: /0x%08x/%pad/
v3:
* use of "offsetof" instead of explicit
James,
Thanks for this mail.
On 2018/4/13 0:14, James Morse wrote:
> Hi gengdongjiu,
>
> On 12/04/18 06:00, gengdongjiu wrote:
>> 2018-02-16 1:55 GMT+08:00 James Morse :
>>> On 05/02/18 11:24, gengdongjiu wrote:
> Is the emulated SError routed following the routing
Fix an issue with FIFO Size and burst size.
Fix an incomplete allocator for Hardware descriptors: memory badly
allocated.
---
Version history:
v1:
* Initial
v2:
* Fix kbuild warning format: /0x%08x/%pad/
v3:
* Get rid of while loop in favor of computed values
Build.include invokes the pre-processor via GCC in order to generate a
dependency list for the input file. Since these options are passed using
'-Wp,-M...,$(depfile)' it is important that $(depfile) does not contain
any commas, so these are substituted with underscores. This substitution
will
James,
Thanks for this mail.
On 2018/4/13 0:14, James Morse wrote:
> Hi gengdongjiu,
>
> On 12/04/18 06:00, gengdongjiu wrote:
>> 2018-02-16 1:55 GMT+08:00 James Morse :
>>> On 05/02/18 11:24, gengdongjiu wrote:
> Is the emulated SError routed following the routing rules for
>
Fix an issue with FIFO Size and burst size.
Fix an incomplete allocator for Hardware descriptors: memory badly
allocated.
---
Version history:
v1:
* Initial
v2:
* Fix kbuild warning format: /0x%08x/%pad/
v3:
* Get rid of while loop in favor of computed values
Build.include invokes the pre-processor via GCC in order to generate a
dependency list for the input file. Since these options are passed using
'-Wp,-M...,$(depfile)' it is important that $(depfile) does not contain
any commas, so these are substituted with underscores. This substitution
will
On 04/07/2018 02:54 AM, Wang, Haiyue wrote:
Hi Corey,
Since IPMI 2.0 just defined minimum, no maximum:
KCS/SMIC Input : Required: 40 bytes IPMI Message, minimum
KCS/SMIC Output : Required: 38 bytes IPMI Message, minimum
Yes, though there are practical maximums that are much smaller
On 04/07/2018 02:54 AM, Wang, Haiyue wrote:
Hi Corey,
Since IPMI 2.0 just defined minimum, no maximum:
KCS/SMIC Input : Required: 40 bytes IPMI Message, minimum
KCS/SMIC Output : Required: 38 bytes IPMI Message, minimum
Yes, though there are practical maximums that are much smaller
The arm64 code indentification code was filtering out the Variant and
Revision bits when it initially read the MIDR value. It is better to
do the filtering of Variant and Revision bits in the regular
expressions in the mapsfile.csv. If some performance events do not
function for particular
The arm64 code indentification code was filtering out the Variant and
Revision bits when it initially read the MIDR value. It is better to
do the filtering of Variant and Revision bits in the regular
expressions in the mapsfile.csv. If some performance events do not
function for particular
On 13.04.2018 15:40, Michal Hocko wrote:
> On Fri 13-04-18 15:16:26, David Hildenbrand wrote:
>> online_pages()/offline_pages() theoretically allows us to work on
>> sub-section sizes. This is especially relevant in the context of
>> virtualization. It e.g. allows us to add/remove memory to Linux
On 13.04.2018 15:40, Michal Hocko wrote:
> On Fri 13-04-18 15:16:26, David Hildenbrand wrote:
>> online_pages()/offline_pages() theoretically allows us to work on
>> sub-section sizes. This is especially relevant in the context of
>> virtualization. It e.g. allows us to add/remove memory to Linux
On Thu, 12 Apr 2018 18:52:13 -0500
Tom Zanussi wrote:
> Hi Steve,
>
> On Thu, 2018-04-12 at 18:20 -0400, Steven Rostedt wrote:
> > On Thu, 12 Apr 2018 10:13:17 -0500
> > Tom Zanussi wrote:
> >
> > > diff --git a/kernel/trace/trace.h
On Thu, 12 Apr 2018 18:52:13 -0500
Tom Zanussi wrote:
> Hi Steve,
>
> On Thu, 2018-04-12 at 18:20 -0400, Steven Rostedt wrote:
> > On Thu, 12 Apr 2018 10:13:17 -0500
> > Tom Zanussi wrote:
> >
> > > diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
> > > index 6fb46a0..f2dc7e6 100644
Detailed documentation about the protectable memory allocator.
Signed-off-by: Igor Stoppa
---
Documentation/core-api/index.rst | 1 +
Documentation/core-api/pmalloc.rst | 107 +
2 files changed, 108 insertions(+)
create mode
Add basic self-test functionality for pmalloc.
The testing is introduced as early as possible, right after the main
dependency, genalloc, has passed successfully, so that it can help
diagnosing failures in pmalloc users.
Signed-off-by: Igor Stoppa
---
On Fri, Apr 13, 2018 at 03:01:11PM +0800, Jason Wang wrote:
>
>
> On 2018年04月12日 08:24, Jonathan Helman wrote:
> >
> >
> > On 04/10/2018 08:12 PM, Jason Wang wrote:
> > >
> > >
> > > On 2018年04月10日 05:11, Jonathan Helman wrote:
> > > >
> > > >
> > > > On 03/22/2018 07:38 PM, Jason Wang
Detailed documentation about the protectable memory allocator.
Signed-off-by: Igor Stoppa
---
Documentation/core-api/index.rst | 1 +
Documentation/core-api/pmalloc.rst | 107 +
2 files changed, 108 insertions(+)
create mode 100644
Add basic self-test functionality for pmalloc.
The testing is introduced as early as possible, right after the main
dependency, genalloc, has passed successfully, so that it can help
diagnosing failures in pmalloc users.
Signed-off-by: Igor Stoppa
---
include/linux/test_pmalloc.h | 24
On Fri, Apr 13, 2018 at 03:01:11PM +0800, Jason Wang wrote:
>
>
> On 2018年04月12日 08:24, Jonathan Helman wrote:
> >
> >
> > On 04/10/2018 08:12 PM, Jason Wang wrote:
> > >
> > >
> > > On 2018年04月10日 05:11, Jonathan Helman wrote:
> > > >
> > > >
> > > > On 03/22/2018 07:38 PM, Jason Wang
Jason Wang points out that it's vary hard for users to build an array of
stat names. The naive thing is to use VIRTIO_BALLOON_S_NR but that
breaks if we add more stats.
Let's add an array of reasonably readable names.
Fixes: 6c64fe7f2 ("virtio_balloon: export hugetlb page allocation counts")
Cc:
Jason Wang points out that it's vary hard for users to build an array of
stat names. The naive thing is to use VIRTIO_BALLOON_S_NR but that
breaks if we add more stats.
Let's add an array of reasonably readable names.
Fixes: 6c64fe7f2 ("virtio_balloon: export hugetlb page allocation counts")
Cc:
The MMU available in many systems running Linux can often provide R/O
protection to the memory pages it handles.
However, the MMU-based protection works efficiently only when said pages
contain exclusively data that will not need further modifications.
Statically allocated variables can be
Verify that pmalloc read-only protection is in place: trying to
overwrite a protected variable will crash the kernel.
Signed-off-by: Igor Stoppa
---
drivers/misc/lkdtm/core.c | 3 +++
drivers/misc/lkdtm/lkdtm.h | 1 +
drivers/misc/lkdtm/perms.c | 25
Verify that pmalloc read-only protection is in place: trying to
overwrite a protected variable will crash the kernel.
Signed-off-by: Igor Stoppa
---
drivers/misc/lkdtm/core.c | 3 +++
drivers/misc/lkdtm/lkdtm.h | 1 +
drivers/misc/lkdtm/perms.c | 25 +
3 files
The MMU available in many systems running Linux can often provide R/O
protection to the memory pages it handles.
However, the MMU-based protection works efficiently only when said pages
contain exclusively data that will not need further modifications.
Statically allocated variables can be
The patch
ASoC: tfa9879: switch to SPDX license tag
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
ASoC: tfa9879: switch to SPDX license tag
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
This patch-set introduces the possibility of protecting memory that has
been allocated dynamically.
The memory is managed in pools: when a memory pool is protected, all the
memory that is currently part of it, will become R/O.
A R/O pool can be expanded (adding more protectable memory).
It can
This patch-set introduces the possibility of protecting memory that has
been allocated dynamically.
The memory is managed in pools: when a memory pool is protected, all the
memory that is currently part of it, will become R/O.
A R/O pool can be expanded (adding more protectable memory).
It can
The vmap_area structure has a field of type struct llist_node, named
purge_list and is used when performing lazy purge of the area.
Such field is left unused during the actual utilization of the
structure.
This patch renames the field to a more generic "area_list", to allow for
utilization
When a page is used for virtual memory, it is often necessary to obtain
a handler to the corresponding vm_struct, which refers to the virtually
continuous area generated when invoking vmalloc.
The struct page has a "mapping" field, which can be re-used, to store a
pointer to the parent area.
The vmap_area structure has a field of type struct llist_node, named
purge_list and is used when performing lazy purge of the area.
Such field is left unused during the actual utilization of the
structure.
This patch renames the field to a more generic "area_list", to allow for
utilization
When a page is used for virtual memory, it is often necessary to obtain
a handler to the corresponding vm_struct, which refers to the virtually
continuous area generated when invoking vmalloc.
The struct page has a "mapping" field, which can be re-used, to store a
pointer to the parent area.
On 13.04.2018 15:32, David Hildenbrand wrote:
> If any page is still online, the section should stay online.
>
> Signed-off-by: David Hildenbrand
> ---
This is a duplicate, please ignore.
(get_maintainers.sh and my mail server had a little clinch, so I had to
send half of the
On 13.04.2018 15:32, David Hildenbrand wrote:
> If any page is still online, the section should stay online.
>
> Signed-off-by: David Hildenbrand
> ---
This is a duplicate, please ignore.
(get_maintainers.sh and my mail server had a little clinch, so I had to
send half of the series out
On Fri, Apr 13, 2018 at 01:47:49PM +0200, Peter Rosin wrote:
> Peter Rosin (2):
> ASoC: max9860: switch to SPDX license tag
This one didn't turn up yet - it's only just been sent though so it
might be stuck in a mail queue somewhere, I've applied patch 2 and I
expect I'll apply this one as
On Fri, Apr 13, 2018 at 01:47:49PM +0200, Peter Rosin wrote:
> Peter Rosin (2):
> ASoC: max9860: switch to SPDX license tag
This one didn't turn up yet - it's only just been sent though so it
might be stuck in a mail queue somewhere, I've applied patch 2 and I
expect I'll apply this one as
On Fri 13-04-18 15:16:26, David Hildenbrand wrote:
> online_pages()/offline_pages() theoretically allows us to work on
> sub-section sizes. This is especially relevant in the context of
> virtualization. It e.g. allows us to add/remove memory to Linux in a VM in
> 4MB chunks.
Well, theoretically
On Fri 13-04-18 15:16:26, David Hildenbrand wrote:
> online_pages()/offline_pages() theoretically allows us to work on
> sub-section sizes. This is especially relevant in the context of
> virtualization. It e.g. allows us to add/remove memory to Linux in a VM in
> 4MB chunks.
Well, theoretically
On Mon, Mar 05, 2018 at 01:37:43PM +, Roman Gushchin wrote:
> I was reported about suspicious growth of unreclaimable slabs
> on some machines. I've found that it happens on machines
> with low memory pressure, and these unreclaimable slabs
> are external names attached to dentries.
>
>
On Mon, Mar 05, 2018 at 01:37:43PM +, Roman Gushchin wrote:
> I was reported about suspicious growth of unreclaimable slabs
> on some machines. I've found that it happens on machines
> with low memory pressure, and these unreclaimable slabs
> are external names attached to dentries.
>
>
On Thu, Apr 12, 2018 at 6:08 PM, Miklos Szeredi wrote:
> Implement stacked reading.
>
I couldn't decipher the meaning of "readd" in the subject of this
and other file ops pacthes??
> Signed-off-by: Miklos Szeredi
> ---
> fs/overlayfs/file.c | 56
>
On Thu, Apr 12, 2018 at 6:08 PM, Miklos Szeredi wrote:
> Implement stacked reading.
>
I couldn't decipher the meaning of "readd" in the subject of this
and other file ops pacthes??
> Signed-off-by: Miklos Szeredi
> ---
> fs/overlayfs/file.c | 56
>
On 14/03/2018 14:11, Michal Hocko wrote:
> On Tue 13-03-18 18:59:30, Laurent Dufour wrote:
>> Changes since v8:
>> - Don't check PMD when locking the pte when THP is disabled
>>Thanks to Daniel Jordan for reporting this.
>> - Rebase on 4.16
>
> Is this really worth reposting the whole pile?
On 14/03/2018 14:11, Michal Hocko wrote:
> On Tue 13-03-18 18:59:30, Laurent Dufour wrote:
>> Changes since v8:
>> - Don't check PMD when locking the pte when THP is disabled
>>Thanks to Daniel Jordan for reporting this.
>> - Rebase on 4.16
>
> Is this really worth reposting the whole pile?
Some devices (esp. paravirtualized) might want to control
- when to online/offline a memory block
- how to online memory (MOVABLE/NORMAL)
- in which granularity to online/offline memory
So let's add a new flag "driver_managed" and disallow to change the
state by user space. Device
Some devices (esp. paravirtualized) might want to control
- when to online/offline a memory block
- how to online memory (MOVABLE/NORMAL)
- in which granularity to online/offline memory
So let's add a new flag "driver_managed" and disallow to change the
state by user space. Device
If any page is still online, the section should stay online.
Signed-off-by: David Hildenbrand
---
mm/page_alloc.c | 2 +-
mm/sparse.c | 25 -
2 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index
If any page is still online, the section should stay online.
Signed-off-by: David Hildenbrand
---
mm/page_alloc.c | 2 +-
mm/sparse.c | 25 -
2 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index
Kernel modules that want to control how/when memory is onlined/offlined
need these functions.
Signed-off-by: David Hildenbrand
---
mm/memory_hotplug.c | 4
1 file changed, 4 insertions(+)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index
Kernel modules that want to control how/when memory is onlined/offlined
need these functions.
Signed-off-by: David Hildenbrand
---
mm/memory_hotplug.c | 4
1 file changed, 4 insertions(+)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index ac14ea772792..3c374d308cf4 100644
---
Page blocks might contain references to the next page block. So
a page block cannot be offlined independently. E.g. on x86: page block
size is 2MB, MAX_ORDER -1 (10) allows 4MB allocations.
-> Right now, __offline_isolated_pages() will mark pages in the following
page block as reserved.
Let
Page blocks might contain references to the next page block. So
a page block cannot be offlined independently. E.g. on x86: page block
size is 2MB, MAX_ORDER -1 (10) allows 4MB allocations.
-> Right now, __offline_isolated_pages() will mark pages in the following
page block as reserved.
Let
If any page is still online, the section should stay online.
Signed-off-by: David Hildenbrand
---
mm/page_alloc.c | 2 +-
mm/sparse.c | 25 -
2 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index
If any page is still online, the section should stay online.
Signed-off-by: David Hildenbrand
---
mm/page_alloc.c | 2 +-
mm/sparse.c | 25 -
2 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index
This allows user space to skip pages that are offline when dumping. This is
especially relevant when dealing with pages that have been unplugged in
the context of virtualization, and their backing storage has already
been freed.
Signed-off-by: David Hildenbrand
---
This allows user space to skip pages that are offline when dumping. This is
especially relevant when dealing with pages that have been unplugged in
the context of virtualization, and their backing storage has already
been freed.
Signed-off-by: David Hildenbrand
---
kernel/crash_core.c | 3 +++
On Thu, Apr 12, 2018 at 02:39:10PM +0200, Jiri Kosina wrote:
> From: Jiri Kosina
>
> Commits 9b46a051e4 ("x86/mm: Initialize vmemmap_base at boot-time") and
> a7412546d8 ("x86/mm: Adjust vmalloc base and size at boot-time") lost the
> type information for __VMALLOC_BASE_L4,
On Thu, Apr 12, 2018 at 02:39:10PM +0200, Jiri Kosina wrote:
> From: Jiri Kosina
>
> Commits 9b46a051e4 ("x86/mm: Initialize vmemmap_base at boot-time") and
> a7412546d8 ("x86/mm: Adjust vmalloc base and size at boot-time") lost the
> type information for __VMALLOC_BASE_L4, __VMALLOC_BASE_L5,
Hi Peter,
Your commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS") broke build
for several samples/bpf programs. I'm unsure what the best way forward
is to unbreak these...
The issue is that these samples are build with LLVM/clang (which
doesn't like 'asm goto' constructs). And they end up
Hi Peter,
Your commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS") broke build
for several samples/bpf programs. I'm unsure what the best way forward
is to unbreak these...
The issue is that these samples are build with LLVM/clang (which
doesn't like 'asm goto' constructs). And they end up
On 27 March 2018 at 14:15, Suzuki K Poulose wrote:
> Expose the maximum physical address size supported by the host
> for a VM. This could be later used by the userspace to choose the
> appropriate size for a given VM. The limit is determined as the
> minimum of actual CPU
On 27 March 2018 at 14:15, Suzuki K Poulose wrote:
> Expose the maximum physical address size supported by the host
> for a VM. This could be later used by the userspace to choose the
> appropriate size for a given VM. The limit is determined as the
> minimum of actual CPU limit, the kernel limit
On Thu, Apr 12, 2018 at 11:12:17AM +0200, Peter Zijlstra wrote:
> On Thu, Apr 12, 2018 at 10:12:33AM +0800, Boqun Feng wrote:
> > A trivial fix/hack would be adding local_irq_disable() and
> > local_irq_enable() around srcu_lock_sync() like:
> >
> > static inline void srcu_lock_sync(struct
On Thu, Apr 12, 2018 at 11:12:17AM +0200, Peter Zijlstra wrote:
> On Thu, Apr 12, 2018 at 10:12:33AM +0800, Boqun Feng wrote:
> > A trivial fix/hack would be adding local_irq_disable() and
> > local_irq_enable() around srcu_lock_sync() like:
> >
> > static inline void srcu_lock_sync(struct
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
Three notable larger changes next to the usual bug fixing:
* Update the email addresses in MAINTAINERS for the s390 folks to
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
Three notable larger changes next to the usual bug fixing:
* Update the email addresses in MAINTAINERS for the s390 folks to
online_pages()/offline_pages() theoretically allows us to work on
sub-section sizes. This is especially relevant in the context of
virtualization. It e.g. allows us to add/remove memory to Linux in a VM in
4MB chunks.
While the whole section is marked as online/offline, we have to know
the state
online_pages()/offline_pages() theoretically allows us to work on
sub-section sizes. This is especially relevant in the context of
virtualization. It e.g. allows us to add/remove memory to Linux in a VM in
4MB chunks.
While the whole section is marked as online/offline, we have to know
the state
Conflicts with the possibility to online sub-section chunks. Revert it
for now.
Signed-off-by: David Hildenbrand
---
drivers/base/node.c| 2 --
include/linux/memory.h | 1 -
mm/memory_hotplug.c| 27 +++
mm/page_alloc.c| 28
Conflicts with the possibility to online sub-section chunks. Revert it
for now.
Signed-off-by: David Hildenbrand
---
drivers/base/node.c| 2 --
include/linux/memory.h | 1 -
mm/memory_hotplug.c| 27 +++
mm/page_alloc.c| 28 ++--
Let's mark all offline pages with PG_offline. We'll continue to mark
them reserved.
Signed-off-by: David Hildenbrand
---
drivers/hv/hv_balloon.c | 2 +-
mm/memory_hotplug.c | 10 ++
mm/page_alloc.c | 5 -
3 files changed, 11 insertions(+), 6
Let's mark all offline pages with PG_offline. We'll continue to mark
them reserved.
Signed-off-by: David Hildenbrand
---
drivers/hv/hv_balloon.c | 2 +-
mm/memory_hotplug.c | 10 ++
mm/page_alloc.c | 5 -
3 files changed, 11 insertions(+), 6 deletions(-)
diff --git
On Mon, Apr 09, 2018 at 04:43:40PM +0200, Arnd Bergmann wrote:
> On Mon, Apr 9, 2018 at 4:37 PM, Pablo Neira Ayuso wrote:
> > Hi Arnd,
> >
> > On Mon, Apr 09, 2018 at 12:53:12PM +0200, Arnd Bergmann wrote:
> >> We get a new link error with CONFIG_NFT_REJECT_INET=y and
> >>
On Mon, Apr 09, 2018 at 04:43:40PM +0200, Arnd Bergmann wrote:
> On Mon, Apr 9, 2018 at 4:37 PM, Pablo Neira Ayuso wrote:
> > Hi Arnd,
> >
> > On Mon, Apr 09, 2018 at 12:53:12PM +0200, Arnd Bergmann wrote:
> >> We get a new link error with CONFIG_NFT_REJECT_INET=y and
> >>
On Fri, Apr 06, 2018 at 01:38:08PM -0700, Andi Kleen wrote:
> This patchkit fixes some random minor issues in the perf user tools
Acked-by: Jiri Olsa
thanks,
jirka
On Fri, Apr 06, 2018 at 01:38:08PM -0700, Andi Kleen wrote:
> This patchkit fixes some random minor issues in the perf user tools
Acked-by: Jiri Olsa
thanks,
jirka
I had the need to understand I/O request processing in detail.
But I also had the need to enrich block traces with other trace events
including my own dynamic kprobe events. So I preferred block trace events
over blktrace to get everything nicely sorted into one ftrace output.
However, I missed
I had the need to understand I/O request processing in detail.
But I also had the need to enrich block traces with other trace events
including my own dynamic kprobe events. So I preferred block trace events
over blktrace to get everything nicely sorted into one ftrace output.
However, I missed
Complements v2.6.31 commit 55782138e47d ("tracing/events: convert block
trace points to TRACE_EVENT()") for cases where rq->rq_disk == NULL:
block_rq_requeue, block_rq_insert, block_rq_issue;
and for cases where bio == NULL:
block_getrq, block_sleeprq.
NB: The NULL pointer check for
Complements v2.6.31 commit 55782138e47d ("tracing/events: convert block
trace points to TRACE_EVENT()") to be equivalent to traditional blktrace
output. Also this allows event filtering to not always get all (un)plug
events.
NB: The NULL pointer check for q->kobj.parent is certainly racy and
I
Complements v2.6.31 commit 55782138e47d ("tracing/events: convert block
trace points to TRACE_EVENT()") for cases where rq->rq_disk == NULL:
block_rq_requeue, block_rq_insert, block_rq_issue;
and for cases where bio == NULL:
block_getrq, block_sleeprq.
NB: The NULL pointer check for
Complements v2.6.31 commit 55782138e47d ("tracing/events: convert block
trace points to TRACE_EVENT()") to be equivalent to traditional blktrace
output. Also this allows event filtering to not always get all (un)plug
events.
NB: The NULL pointer check for q->kobj.parent is certainly racy and
I
On Tue, Apr 10, 2018 at 4:05 AM, Viresh Kumar wrote:
> The OPP tables are present as separate nodes, whose phandle is used in
> the "operating-points-v2" property of devices. Currently the OF core
> creates a platform device for the OPP table unconditionally, which is
>
Just like blktrace distinguishes explicit and schedule by means of
BLK_TA_UNPLUG_IO and BLK_TA_UNPLUG_TIMER, actually make use of the
existing argument "explicit" to distinguish the two cases in the one
common tracepoint block_unplug.
Complements v2.6.39 commit 49cac01e1fa7 ("block: make unplug
On Tue, Apr 10, 2018 at 4:05 AM, Viresh Kumar wrote:
> The OPP tables are present as separate nodes, whose phandle is used in
> the "operating-points-v2" property of devices. Currently the OF core
> creates a platform device for the OPP table unconditionally, which is
> not used by any kernel
Just like blktrace distinguishes explicit and schedule by means of
BLK_TA_UNPLUG_IO and BLK_TA_UNPLUG_TIMER, actually make use of the
existing argument "explicit" to distinguish the two cases in the one
common tracepoint block_unplug.
Complements v2.6.39 commit 49cac01e1fa7 ("block: make unplug
Am Freitag, 13. April 2018, 14:53:13 CEST schrieb Theodore Y. Ts'o:
Hi Theodore,
>
> This was always the original design intent, but I screwed up and no
> one noticed until Jann reached out to be and said, "Hey this
> doesn't seem to make much sense".
I disagree, but I guess you would have
Am Freitag, 13. April 2018, 14:53:13 CEST schrieb Theodore Y. Ts'o:
Hi Theodore,
>
> This was always the original design intent, but I screwed up and no
> one noticed until Jann reached out to be and said, "Hey this
> doesn't seem to make much sense".
I disagree, but I guess you would have
701 - 800 of 1298 matches
Mail list logo