Re: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line

On Mon, Nov 13, 2017 at 10:52 AM, Andi Kleen wrote: > > It works for me. No it clearly does not. > % ./linux/scripts/faddr2line obj/vmlinux schedule+10 > schedule+10/0x80: > schedule at arch/x86/include/asm/current.h:15 That's obviously garbage and the problem. Just look

Re: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line

On Mon, Nov 13, 2017 at 10:52 AM, Andi Kleen wrote: > > It works for me. No it clearly does not. > % ./linux/scripts/faddr2line obj/vmlinux schedule+10 > schedule+10/0x80: > schedule at arch/x86/include/asm/current.h:15 That's obviously garbage and the problem. Just look at it. It claims it

Re: [btrfs] WARNING: CPU: 0 PID: 6379 at fs/direct-io.c:293 dio_complete+0x1d4/0x220

On Sun, Nov 05, 2017 at 05:13:06PM -0800, Eric Biggers wrote: > On Tue, Oct 31, 2017 at 02:54:17PM +0800, Eryu Guan wrote: > > On Tue, Oct 31, 2017 at 01:10:41AM +0100, Fengguang Wu wrote: > > > Hi Eryu, > > > > > > On Mon, Oct 30, 2017 at 03:44:29PM +0800, Eryu Guan wrote: > > > > Hi Fengguang,

Re: [btrfs] WARNING: CPU: 0 PID: 6379 at fs/direct-io.c:293 dio_complete+0x1d4/0x220

On Sun, Nov 05, 2017 at 05:13:06PM -0800, Eric Biggers wrote: > On Tue, Oct 31, 2017 at 02:54:17PM +0800, Eryu Guan wrote: > > On Tue, Oct 31, 2017 at 01:10:41AM +0100, Fengguang Wu wrote: > > > Hi Eryu, > > > > > > On Mon, Oct 30, 2017 at 03:44:29PM +0800, Eryu Guan wrote: > > > > Hi Fengguang,

Re: [PATCH] mm: show stats for non-default hugepage sizes in /proc/meminfo

On Mon, Nov 13, 2017 at 06:45:01PM +, Roman Gushchin wrote: > Or, at least, some total counter, e.g. how much memory is consumed > by hugetlb pages? I'm not a big fan of the verbose breakdown for every huge page size. As others have pointed out such detail exists elswhere. But I do think we

Re: [PATCH] mm: show stats for non-default hugepage sizes in /proc/meminfo

On Mon, Nov 13, 2017 at 06:45:01PM +, Roman Gushchin wrote: > Or, at least, some total counter, e.g. how much memory is consumed > by hugetlb pages? I'm not a big fan of the verbose breakdown for every huge page size. As others have pointed out such detail exists elswhere. But I do think we

Re: [PATCH v2] fs: fsnotify: account fsnotify metadata to kmemcg

On 11/9/17 5:54 AM, Michal Hocko wrote: [Sorry for the late reply] On Tue 31-10-17 11:12:38, Jan Kara wrote: On Tue 31-10-17 00:39:58, Yang Shi wrote: [...] I do agree it is not fair and not neat to account to producer rather than misbehaving consumer, but current memcg design looks not

Re: [PATCH v2] fs: fsnotify: account fsnotify metadata to kmemcg

On 11/9/17 5:54 AM, Michal Hocko wrote: [Sorry for the late reply] On Tue 31-10-17 11:12:38, Jan Kara wrote: On Tue 31-10-17 00:39:58, Yang Shi wrote: [...] I do agree it is not fair and not neat to account to producer rather than misbehaving consumer, but current memcg design looks not

Re: drivers/firmware/google/vpd.c: duplicate sysfs file

On Mon, Nov 13, 2017 at 11:04 AM, Dmitry Torokhov wrote: > > On Mon, Nov 13, 2017 at 10:18:35AM -0800, Randy Dunlap wrote: > > On 11/13/2017 06:41 AM, Guenter Roeck wrote: > > > > > > > > > On Sun, Nov 12, 2017 at 10:36 PM, Randy Dunlap > >

Re: drivers/firmware/google/vpd.c: duplicate sysfs file

On Mon, Nov 13, 2017 at 11:04 AM, Dmitry Torokhov wrote: > > On Mon, Nov 13, 2017 at 10:18:35AM -0800, Randy Dunlap wrote: > > On 11/13/2017 06:41 AM, Guenter Roeck wrote: > > > > > > > > > On Sun, Nov 12, 2017 at 10:36 PM, Randy Dunlap > > > wrote: > > > > > >

Re: Firmware signing -- Re: [PATCH 00/27] security, efi: Add kernel lockdown

On Mon, Nov 13, 2017 at 07:50:35PM +0100, Luis R. Rodriguez wrote: > On Fri, Nov 10, 2017 at 08:45:06AM -0500, Mimi Zohar wrote: > It does not mean we don't have to support hashes from the start, we can, > however that could require a driver change where its hash is specified or > preferred, for

Re: Firmware signing -- Re: [PATCH 00/27] security, efi: Add kernel lockdown

On Mon, Nov 13, 2017 at 07:50:35PM +0100, Luis R. Rodriguez wrote: > On Fri, Nov 10, 2017 at 08:45:06AM -0500, Mimi Zohar wrote: > It does not mean we don't have to support hashes from the start, we can, > however that could require a driver change where its hash is specified or > preferred, for

Re: [RFC 1/7] x86/asm/64: Allocate and enable the SYSENTER stack

On 11/10/2017 08:05 PM, Andy Lutomirski wrote: > This will simplify some future code changes that will want some > temporary stack space in more places. It also lets us get rid of a > SWAPGS_UNSAFE_STACK user. > > This does not depend on CONFIG_IA32_EMULATION because we'll want the > stack space

Re: [RFC 1/7] x86/asm/64: Allocate and enable the SYSENTER stack

On 11/10/2017 08:05 PM, Andy Lutomirski wrote: > This will simplify some future code changes that will want some > temporary stack space in more places. It also lets us get rid of a > SWAPGS_UNSAFE_STACK user. > > This does not depend on CONFIG_IA32_EMULATION because we'll want the > stack space

Re: [PATCH] Documentation: sound: hd-audio: notes.rst

On Mon, 13 Nov 2017 18:41:23 +0100, Chris Gorman wrote: > > Fixed reference to file HD-Audio-Models.rst which has been moved to > hd-audio/models.rst > > Signed-off-by: Chris Gorman Applied, thanks. Takashi

Re: [PATCH] Documentation: sound: hd-audio: notes.rst

On Mon, 13 Nov 2017 18:41:23 +0100, Chris Gorman wrote: > > Fixed reference to file HD-Audio-Models.rst which has been moved to > hd-audio/models.rst > > Signed-off-by: Chris Gorman Applied, thanks. Takashi

Re: [RFC PATCH v2] fw_lockdown: new micro LSM module to prevent loading unsigned firmware

On Mon, Nov 13, 2017 at 06:43:34AM -0500, Mimi Zohar wrote: > If the kernel is locked down and IMA-appraisal is not enabled, prevent > loading of unsigned firmware. > > Signed-off-by: Mimi Zohar > --- > Changelog v2: > - Invert kernel_is_locked_down() test (Luis

Re: [RFC PATCH v2] fw_lockdown: new micro LSM module to prevent loading unsigned firmware

On Mon, Nov 13, 2017 at 06:43:34AM -0500, Mimi Zohar wrote: > If the kernel is locked down and IMA-appraisal is not enabled, prevent > loading of unsigned firmware. > > Signed-off-by: Mimi Zohar > --- > Changelog v2: > - Invert kernel_is_locked_down() test (Luis Rodriquez) > - Increase LSM name

Re: [PATCH 4.4 34/46] crypto: xts - Add ECB dependency

On Fri, Nov 10, 2017 at 08:40:53PM +, Ben Hutchings wrote: >On Thu, 2017-10-19 at 15:49 +0200, Greg Kroah-Hartman wrote: >> 4.4-stable review patch.  If anyone has any objections, please let me >> know. >> >> -- >> >> From: Milan Broz >> >> >> [ Upstream

Re: [PATCH 4.4 34/46] crypto: xts - Add ECB dependency

On Fri, Nov 10, 2017 at 08:40:53PM +, Ben Hutchings wrote: >On Thu, 2017-10-19 at 15:49 +0200, Greg Kroah-Hartman wrote: >> 4.4-stable review patch.  If anyone has any objections, please let me >> know. >> >> -- >> >> From: Milan Broz >> >> >> [ Upstream commit

Re: [PATCH 4.4 07/40] arm64: ensure __dump_instr() checks addr_limit

On Mon, 2017-11-06 at 10:44 +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Mark Rutland > > commit 7a7003b1da010d2b0d1dc8bf21c10f5c73b389f1 upstream. > > It's possible for a

Re: [PATCH 4.4 07/40] arm64: ensure __dump_instr() checks addr_limit

On Mon, 2017-11-06 at 10:44 +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Mark Rutland > > commit 7a7003b1da010d2b0d1dc8bf21c10f5c73b389f1 upstream. > > It's possible for a user to deliberately

Re: [PATCH 4.4 41/46] uapi: fix linux/rds.h userspace compilation errors

On Sun, Nov 12, 2017 at 06:50:43PM +, Ben Hutchings wrote: >On Thu, 2017-10-19 at 15:49 +0200, Greg Kroah-Hartman wrote: >> 4.4-stable review patch.  If anyone has any objections, please let me know. >> >> -- >> >> From: "Dmitry V. Levin" >> >> >> [ Upstream

Re: [PATCH 4.4 41/46] uapi: fix linux/rds.h userspace compilation errors

On Sun, Nov 12, 2017 at 06:50:43PM +, Ben Hutchings wrote: >On Thu, 2017-10-19 at 15:49 +0200, Greg Kroah-Hartman wrote: >> 4.4-stable review patch.  If anyone has any objections, please let me know. >> >> -- >> >> From: "Dmitry V. Levin" >> >> >> [ Upstream commit

Re: drivers/firmware/google/vpd.c: duplicate sysfs file

On Mon, Nov 13, 2017 at 10:18:35AM -0800, Randy Dunlap wrote: > On 11/13/2017 06:41 AM, Guenter Roeck wrote: > > > > > > On Sun, Nov 12, 2017 at 10:36 PM, Randy Dunlap > > wrote: > > > > sysfs: cannot create duplicate filename

Re: drivers/firmware/google/vpd.c: duplicate sysfs file

On Mon, Nov 13, 2017 at 10:18:35AM -0800, Randy Dunlap wrote: > On 11/13/2017 06:41 AM, Guenter Roeck wrote: > > > > > > On Sun, Nov 12, 2017 at 10:36 PM, Randy Dunlap > > wrote: > > > > sysfs: cannot create duplicate filename '/devices/platform/vpd' > > > >

[PATCH net-next] net: stmmac: fix LPI transitioning for dwmac4

The LPI transitioning logic in stmmac_main uses priv->tx_path_in_lpi_mode to enter/exit LPI. However, priv->tx_path_in_lpi_mode is assigned using the return value from host_irq_status(). So for dwmac4, priv->tx_path_in_lpi_mode was always false, to stmmac_tx_clean() would always try to put us in

[PATCH net-next] net: stmmac: fix LPI transitioning for dwmac4

The LPI transitioning logic in stmmac_main uses priv->tx_path_in_lpi_mode to enter/exit LPI. However, priv->tx_path_in_lpi_mode is assigned using the return value from host_irq_status(). So for dwmac4, priv->tx_path_in_lpi_mode was always false, to stmmac_tx_clean() would always try to put us in

Re: [PATCH ALT4 V3 1/2] audit: show fstype:pathname for entries with anonymous parents

On Mon, Nov 13, 2017 at 1:30 PM, Steve Grubb wrote: > On Thursday, November 9, 2017 3:52:46 PM EST Richard Guy Briggs wrote: >> > >> > It might be simplest to just apply a corrective patch over top of >> > >> > this one so that you don't have to muck about with git branches and

Re: [PATCH ALT4 V3 1/2] audit: show fstype:pathname for entries with anonymous parents

On Mon, Nov 13, 2017 at 1:30 PM, Steve Grubb wrote: > On Thursday, November 9, 2017 3:52:46 PM EST Richard Guy Briggs wrote: >> > >> > It might be simplest to just apply a corrective patch over top of >> > >> > this one so that you don't have to muck about with git branches and >> > >> > commit

[PATCH] schedule: use unlikely()

A small patch for schedule(), so that the code goes straght in the common case. Signed-off-by: Mikulas Patocka --- include/linux/blkdev.h |2 +- kernel/sched/core.c|2 +- 2 files changed, 2 insertions(+), 2 deletions(-) Index: linux-2.6/include/linux/blkdev.h

[PATCH] schedule: use unlikely()

A small patch for schedule(), so that the code goes straght in the common case. Signed-off-by: Mikulas Patocka --- include/linux/blkdev.h |2 +- kernel/sched/core.c|2 +- 2 files changed, 2 insertions(+), 2 deletions(-) Index: linux-2.6/include/linux/blkdev.h

[no subject]

-- -- Greetings From Elite Finance to you, Getting a legitimate loan have always been a huge problem to clients who are in financial needs. The issue of credit and collateral are something that clients are always worried about when seeking a loan from a legitimate lender. But Elite

[no subject]

-- -- Greetings From Elite Finance to you, Getting a legitimate loan have always been a huge problem to clients who are in financial needs. The issue of credit and collateral are something that clients are always worried about when seeking a loan from a legitimate lender. But Elite

Re: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line

> > It's the "CONFIG_DEBUG_INFO_SPLIT" thing that makes faddr2line unable > > to see the inlining information, > > > > Using OPTIMIZE_INLINING is fine. > > Good to know that! It works for me. Perhaps your binutils is too old? It was added at some point. Can you try upgrading? %

Re: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line

> > It's the "CONFIG_DEBUG_INFO_SPLIT" thing that makes faddr2line unable > > to see the inlining information, > > > > Using OPTIMIZE_INLINING is fine. > > Good to know that! It works for me. Perhaps your binutils is too old? It was added at some point. Can you try upgrading? %

Re: [PATCH v8 1/6] x86/tsc: remove tsc_disabled flag

> Reviewed-by: Dou Liyang Thank you! Pavel

Re: [PATCH v8 1/6] x86/tsc: remove tsc_disabled flag

> Reviewed-by: Dou Liyang Thank you! Pavel

Re: Firmware signing -- Re: [PATCH 00/27] security, efi: Add kernel lockdown

On Fri, Nov 10, 2017 at 08:45:06AM -0500, Mimi Zohar wrote: > On Fri, 2017-11-10 at 02:46 +0100, Luis R. Rodriguez wrote: > > On Thu, Nov 09, 2017 at 10:48:43AM +0900, AKASHI, Takahiro wrote: > > > On Wed, Nov 08, 2017 at 08:46:26PM +0100, Luis R. Rodriguez wrote: > > > > But perhaps I'm not

Re: Firmware signing -- Re: [PATCH 00/27] security, efi: Add kernel lockdown

On Fri, Nov 10, 2017 at 08:45:06AM -0500, Mimi Zohar wrote: > On Fri, 2017-11-10 at 02:46 +0100, Luis R. Rodriguez wrote: > > On Thu, Nov 09, 2017 at 10:48:43AM +0900, AKASHI, Takahiro wrote: > > > On Wed, Nov 08, 2017 at 08:46:26PM +0100, Luis R. Rodriguez wrote: > > > > But perhaps I'm not

Re: [PATCH] iio: adc: cpcap: fix incorrect validation

* Sebastian Reichel [171112 18:30]: > Hi, > > On Mon, Nov 13, 2017 at 12:01:20AM +0800, Pan Bian wrote: > > Function platform_get_irq_byname() returns a negative error code on > > failure, and a zero or positive number on success. However, in function > > cpcap_adc_probe(),

Re: [PATCH] iio: adc: cpcap: fix incorrect validation

* Sebastian Reichel [171112 18:30]: > Hi, > > On Mon, Nov 13, 2017 at 12:01:20AM +0800, Pan Bian wrote: > > Function platform_get_irq_byname() returns a negative error code on > > failure, and a zero or positive number on success. However, in function > > cpcap_adc_probe(), positive IRQ numbers

Re: Regression in Linux next-20171113 with fbdev timer conversion

* Bartlomiej Zolnierkiewicz <b.zolnier...@samsung.com> [171113 17:26]: > > On Monday, November 13, 2017 09:07:14 AM Tony Lindgren wrote: > > Hi, > > Hi Tony, > > > Looks like next-20171113 now has a NULL pointe dereference with commit > > 6c78935777d

Re: Regression in Linux next-20171113 with fbdev timer conversion

* Bartlomiej Zolnierkiewicz [171113 17:26]: > > On Monday, November 13, 2017 09:07:14 AM Tony Lindgren wrote: > > Hi, > > Hi Tony, > > > Looks like next-20171113 now has a NULL pointe dereference with commit > > 6c78935777d1 ("video: fbdev: Convert timer

Re: [PATCH] mm: show stats for non-default hugepage sizes in /proc/meminfo

On Mon, Nov 13, 2017 at 10:30:10AM -0800, Mike Kravetz wrote: > On 11/13/2017 10:17 AM, Dave Hansen wrote: > > On 11/13/2017 10:11 AM, Roman Gushchin wrote: > >> On Mon, Nov 13, 2017 at 09:06:32AM -0800, Dave Hansen wrote: > >>> On 11/13/2017 08:03 AM, Roman Gushchin wrote: > To solve this

Re: [PATCH] mm: show stats for non-default hugepage sizes in /proc/meminfo

On Mon, Nov 13, 2017 at 10:30:10AM -0800, Mike Kravetz wrote: > On 11/13/2017 10:17 AM, Dave Hansen wrote: > > On 11/13/2017 10:11 AM, Roman Gushchin wrote: > >> On Mon, Nov 13, 2017 at 09:06:32AM -0800, Dave Hansen wrote: > >>> On 11/13/2017 08:03 AM, Roman Gushchin wrote: > To solve this

Re: linux-next: manual merge of the devicetree tree with the drm tree

Hi Jyri, On 11/13/17 07:40, Jyri Sarha wrote: > On 11/13/17 07:58, Stephen Rothwell wrote: >> Hi all, >> >> On Mon, 30 Oct 2017 20:37:56 + Mark Brown wrote: >>> >>> Today's linux-next merge of the devicetree tree got a conflict in: >>> >>>

Re: linux-next: manual merge of the devicetree tree with the drm tree

Hi Jyri, On 11/13/17 07:40, Jyri Sarha wrote: > On 11/13/17 07:58, Stephen Rothwell wrote: >> Hi all, >> >> On Mon, 30 Oct 2017 20:37:56 + Mark Brown wrote: >>> >>> Today's linux-next merge of the devicetree tree got a conflict in: >>> >>> drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c >>>

Re: [PATCH 2/3] fpga: manager: don't use drvdata in common fpga code

On Mon, Nov 13, 2017 at 11:51:59AM -0600, Alan Tull wrote: > On Tue, Oct 31, 2017 at 9:22 PM, Alan Tull wrote: > > Any further comments on v5? I'm getting ready to send v6. If I do it > today, most of these patches will have no changes (again), the only > changes will be in

Re: [PATCH 2/3] fpga: manager: don't use drvdata in common fpga code

On Mon, Nov 13, 2017 at 11:51:59AM -0600, Alan Tull wrote: > On Tue, Oct 31, 2017 at 9:22 PM, Alan Tull wrote: > > Any further comments on v5? I'm getting ready to send v6. If I do it > today, most of these patches will have no changes (again), the only > changes will be in the patches that

Re: [PATCH 00/24] staging: ccree: more cleanup patches

These cleanups look nice. Thanks. I hope you do a mass remove of likely/unlikely in a patch soon. Whenever, I see one of those in a + line I always have to remind myself that you're planning to do it in a later patch. regards, dan carpenter

Re: [PATCH 00/24] staging: ccree: more cleanup patches

These cleanups look nice. Thanks. I hope you do a mass remove of likely/unlikely in a patch soon. Whenever, I see one of those in a + line I always have to remind myself that you're planning to do it in a later patch. regards, dan carpenter

Re: [PATCH 5/7] perf tests: Set evlist of test__task_exit() to !overwrite

Em Mon, Nov 13, 2017 at 01:38:07AM +, Wang Nan escreveu: > Changing ringbuffer to !overwrite in this task is harmless because > this test uses a very low frequency (1) and using a very simple > program (true). There should have only 3 events in the whole test. > Overwriting is impossible to

Re: [PATCH 5/7] perf tests: Set evlist of test__task_exit() to !overwrite

Em Mon, Nov 13, 2017 at 01:38:07AM +, Wang Nan escreveu: > Changing ringbuffer to !overwrite in this task is harmless because > this test uses a very low frequency (1) and using a very simple > program (true). There should have only 3 events in the whole test. > Overwriting is impossible to

Re: [PATCH 4/7] perf tests: Set evlist of test__basic_mmap() to !overwrite

Em Mon, Nov 13, 2017 at 01:38:06AM +, Wang Nan escreveu: > In this test, a large ring buffer is required so all events can feed into, > so overwrite or not is meaningless. > > Change to !overwrite so following commits can remove this argument. applied > Signed-off-by: Wang Nan

Re: [PATCH 4/7] perf tests: Set evlist of test__basic_mmap() to !overwrite

Em Mon, Nov 13, 2017 at 01:38:06AM +, Wang Nan escreveu: > In this test, a large ring buffer is required so all events can feed into, > so overwrite or not is meaningless. > > Change to !overwrite so following commits can remove this argument. applied > Signed-off-by: Wang Nan > --- >

Re: [PATCH 3/7] perf tests: Set evlist of test__sw_clock_freq() to !overwrite

Em Mon, Nov 13, 2017 at 01:38:05AM +, Wang Nan escreveu: > Unsetting overwrite when calling perf_evlist__mmap is harmless. This commit > passes false to it, makes following commits eliminate the overwrite argument > easier. applied > Signed-off-by: Wang Nan > --- >

Re: [PATCH 3/7] perf tests: Set evlist of test__sw_clock_freq() to !overwrite

Em Mon, Nov 13, 2017 at 01:38:05AM +, Wang Nan escreveu: > Unsetting overwrite when calling perf_evlist__mmap is harmless. This commit > passes false to it, makes following commits eliminate the overwrite argument > easier. applied > Signed-off-by: Wang Nan > --- >

Re: [PATCH 1/4] ALSA: cs46xx: Adjust 33 function calls together with a variable assignment

On Mon, Nov 13, 2017 at 07:22:30PM +0100, SF Markus Elfring wrote: > - > - if ( (cpcm->pcm_channel = cs46xx_dsp_create_pcm_channel (chip, > sample_rate, cpcm, > - > cpcm->hw_buf.addr, > -

Re: [PATCH 1/4] ALSA: cs46xx: Adjust 33 function calls together with a variable assignment

On Mon, Nov 13, 2017 at 07:22:30PM +0100, SF Markus Elfring wrote: > - > - if ( (cpcm->pcm_channel = cs46xx_dsp_create_pcm_channel (chip, > sample_rate, cpcm, > - > cpcm->hw_buf.addr, > -

Re: [PATCH 2/7] perf tests: Set evlist of test__backward_ring_buffer() to !overwrite

Em Mon, Nov 13, 2017 at 01:38:04AM +, Wang Nan escreveu: > Setting overwrite in perf_evlist__mmap() is meaningless because the > event in this evlist is already have 'overwrite' postfix and goes to > backward ring buffer automatically. Pass 'false' to perf_evlist__mmap() > to make it similar

Re: [PATCH 2/7] perf tests: Set evlist of test__backward_ring_buffer() to !overwrite

Em Mon, Nov 13, 2017 at 01:38:04AM +, Wang Nan escreveu: > Setting overwrite in perf_evlist__mmap() is meaningless because the > event in this evlist is already have 'overwrite' postfix and goes to > backward ring buffer automatically. Pass 'false' to perf_evlist__mmap() > to make it similar

Re: [PATCH] mm: show stats for non-default hugepage sizes in /proc/meminfo

On 11/13/2017 10:17 AM, Dave Hansen wrote: > On 11/13/2017 10:11 AM, Roman Gushchin wrote: >> On Mon, Nov 13, 2017 at 09:06:32AM -0800, Dave Hansen wrote: >>> On 11/13/2017 08:03 AM, Roman Gushchin wrote: To solve this problem, let's display stats for all hugepage sizes. To provide the

Re: [PATCH] mm: show stats for non-default hugepage sizes in /proc/meminfo

On 11/13/2017 10:17 AM, Dave Hansen wrote: > On 11/13/2017 10:11 AM, Roman Gushchin wrote: >> On Mon, Nov 13, 2017 at 09:06:32AM -0800, Dave Hansen wrote: >>> On 11/13/2017 08:03 AM, Roman Gushchin wrote: To solve this problem, let's display stats for all hugepage sizes. To provide the

Re: [PATCH ALT4 V3 1/2] audit: show fstype:pathname for entries with anonymous parents

On Thursday, November 9, 2017 3:52:46 PM EST Richard Guy Briggs wrote: > > >> > It might be simplest to just apply a corrective patch over top of > > >> > this one so that you don't have to muck about with git branches and > > >> > commit messages. > > >> > > >> A quick note on the "corrective

Re: [PATCH 1/3] perf help: Document missing options

Em Sun, Nov 12, 2017 at 10:10:45AM +0900, Sihyeon Jang escreveu: > Cc: Jiri Olsa > Cc: Namhyung Kim > Signed-off-by: Sihyeon Jang > --- > tools/perf/Documentation/perf-help.txt | 14 +- > 1 file changed, 13

Re: [PATCH ALT4 V3 1/2] audit: show fstype:pathname for entries with anonymous parents

On Thursday, November 9, 2017 3:52:46 PM EST Richard Guy Briggs wrote: > > >> > It might be simplest to just apply a corrective patch over top of > > >> > this one so that you don't have to muck about with git branches and > > >> > commit messages. > > >> > > >> A quick note on the "corrective

Re: [PATCH 1/3] perf help: Document missing options

Em Sun, Nov 12, 2017 at 10:10:45AM +0900, Sihyeon Jang escreveu: > Cc: Jiri Olsa > Cc: Namhyung Kim > Signed-off-by: Sihyeon Jang > --- > tools/perf/Documentation/perf-help.txt | 14 +- > 1 file changed, 13 insertions(+), 1 deletion(-) > > diff --git

Re: [PATCH 3/3] perf top: Remove a duplicate word

Em Sun, Nov 12, 2017 at 10:10:47AM +0900, Sihyeon Jang escreveu: > Cc: Jiri Olsa > Cc: Namhyung Kim > Signed-off-by: Sihyeon Jang Thanks, applied. - Arnaldo > --- > tools/perf/builtin-top.c | 2 +- > 1 file changed, 1

Re: [PATCH 3/3] perf top: Remove a duplicate word

Em Sun, Nov 12, 2017 at 10:10:47AM +0900, Sihyeon Jang escreveu: > Cc: Jiri Olsa > Cc: Namhyung Kim > Signed-off-by: Sihyeon Jang Thanks, applied. - Arnaldo > --- > tools/perf/builtin-top.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tools/perf/builtin-top.c

[PATCH 4/4] ALSA: cs46xx: Adjust 35 checks for null pointers

From: Markus Elfring Date: Mon, 13 Nov 2017 19:03:29 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written … Thus

[PATCH 4/4] ALSA: cs46xx: Adjust 35 checks for null pointers

From: Markus Elfring Date: Mon, 13 Nov 2017 19:03:29 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written … Thus fix the affected source code

[PATCH 3/4] ALSA: cs46xx: Improve a size determination in cs46xx_dsp_proc_register_scb_desc()

From: Markus Elfring Date: Mon, 13 Nov 2017 18:56:58 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 3/4] ALSA: cs46xx: Improve a size determination in cs46xx_dsp_proc_register_scb_desc()

From: Markus Elfring Date: Mon, 13 Nov 2017 18:56:58 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was

Re: [PATCH 2/3] perf top: Document missing options

Em Sun, Nov 12, 2017 at 10:10:46AM +0900, Sihyeon Jang escreveu: > Cc: Jiri Olsa > Cc: Namhyung Kim > Signed-off-by: Sihyeon Jang applied > --- > tools/perf/Documentation/perf-top.txt | 6 ++ > 1 file changed, 6 insertions(+)

Re: [PATCH 2/3] perf top: Document missing options

Em Sun, Nov 12, 2017 at 10:10:46AM +0900, Sihyeon Jang escreveu: > Cc: Jiri Olsa > Cc: Namhyung Kim > Signed-off-by: Sihyeon Jang applied > --- > tools/perf/Documentation/perf-top.txt | 6 ++ > 1 file changed, 6 insertions(+) > > diff --git a/tools/perf/Documentation/perf-top.txt >

[GIT PULL] dlm updates for 4.15

Hi Linus, Please pull dlm updates from tag: git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-4.15 This set focuses, as usual, on fixes to the comms layer. New testing of the dlm with ocfs2 uncovered a number of bugs in the TCP connection handling during recovery,

[GIT PULL] dlm updates for 4.15

Hi Linus, Please pull dlm updates from tag: git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-4.15 This set focuses, as usual, on fixes to the comms layer. New testing of the dlm with ocfs2 uncovered a number of bugs in the TCP connection handling during recovery,

[PATCH 2/4] ALSA: cs46xx: Use common error handling code in two functions

From: Markus Elfring Date: Mon, 13 Nov 2017 18:53:11 +0100 Add jump targets so that a bit of exception handling can be better reused at the end of these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring

[PATCH 2/4] ALSA: cs46xx: Use common error handling code in two functions

From: Markus Elfring Date: Mon, 13 Nov 2017 18:53:11 +0100 Add jump targets so that a bit of exception handling can be better reused at the end of these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- sound/pci/cs46xx/cs46xx.c | 64

Re: [PATCH v1 1/5] perf, tools: Document some missing perf.data headers

Em Mon, Nov 13, 2017 at 09:54:03AM +0100, Jiri Olsa escreveu: > On Thu, Nov 09, 2017 at 06:55:24AM -0800, Andi Kleen wrote: > > From: Andi Kleen > > > > Document STAT and CACHE header entries. > > > > Signed-off-by: Andi Kleen > > Acked-by: Jiri

Re: [PATCH v1 1/5] perf, tools: Document some missing perf.data headers

Em Mon, Nov 13, 2017 at 09:54:03AM +0100, Jiri Olsa escreveu: > On Thu, Nov 09, 2017 at 06:55:24AM -0800, Andi Kleen wrote: > > From: Andi Kleen > > > > Document STAT and CACHE header entries. > > > > Signed-off-by: Andi Kleen > > Acked-by: Jiri Olsa Applied. - Arnaldo

Re: [PATCH v1 3/5] perf, tools, script: Allow printing period for non freq mode groups

Em Mon, Nov 13, 2017 at 10:11:58AM +0100, Jiri Olsa escreveu: > On Thu, Nov 09, 2017 at 06:55:26AM -0800, Andi Kleen wrote: > > From: Andi Kleen > > > > When using leader sampling the values of the not sampled but counted > > events are shown by perf script in "period". > >

Re: [PATCH v1 3/5] perf, tools, script: Allow printing period for non freq mode groups

Em Mon, Nov 13, 2017 at 10:11:58AM +0100, Jiri Olsa escreveu: > On Thu, Nov 09, 2017 at 06:55:26AM -0800, Andi Kleen wrote: > > From: Andi Kleen > > > > When using leader sampling the values of the not sampled but counted > > events are shown by perf script in "period". > > > > Currently

[PATCH 1/4] ALSA: cs46xx: Adjust 33 function calls together with a variable assignment

From: Markus Elfring Date: Mon, 13 Nov 2017 18:50:19 +0100 The script "checkpatch.pl" pointed information out like the following. ERROR: do not use assignment in if condition Thus fix the affected source code places. Signed-off-by: Markus Elfring

[PATCH 1/4] ALSA: cs46xx: Adjust 33 function calls together with a variable assignment

From: Markus Elfring Date: Mon, 13 Nov 2017 18:50:19 +0100 The script "checkpatch.pl" pointed information out like the following. ERROR: do not use assignment in if condition Thus fix the affected source code places. Signed-off-by: Markus Elfring --- sound/pci/cs46xx/cs46xx.c | 31

Re: [PATCH v1 5/5] perf, tools, script: Allow computing metrics in perf script

Em Mon, Nov 13, 2017 at 10:30:11AM +0100, Jiri Olsa escreveu: > On Thu, Nov 09, 2017 at 06:55:28AM -0800, Andi Kleen wrote: > > SNIP > > > static void process_event(struct perf_script *script, > > struct perf_sample *sample, struct perf_evsel *evsel, > >

Re: [PATCH v1 5/5] perf, tools, script: Allow computing metrics in perf script

Em Mon, Nov 13, 2017 at 10:30:11AM +0100, Jiri Olsa escreveu: > On Thu, Nov 09, 2017 at 06:55:28AM -0800, Andi Kleen wrote: > > SNIP > > > static void process_event(struct perf_script *script, > > struct perf_sample *sample, struct perf_evsel *evsel, > >

[PATCH 0/4] ALSA: cs46xx: Adjustments for some function implementations

From: Markus Elfring Date: Mon, 13 Nov 2017 19:14:56 +0100 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Adjust 33 function calls together with a variable assignment Use common error handling code in two

Re: [PATCH] MIPS: Add iomem resource for kernel bss section.

On Thu, Oct 12, 2017 at 12:50:34PM -0700, David Daney wrote: > The kexec/kdump tools need to know where the .bss is so it can be > included in the core dump. This allows vmcore-dmesg to have access to > the dmesg buffers of the crashed kernel as well as allowing the > debugger to examine

[PATCH 0/4] ALSA: cs46xx: Adjustments for some function implementations

From: Markus Elfring Date: Mon, 13 Nov 2017 19:14:56 +0100 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Adjust 33 function calls together with a variable assignment Use common error handling code in two functions Improve a size

Re: [PATCH] MIPS: Add iomem resource for kernel bss section.

On Thu, Oct 12, 2017 at 12:50:34PM -0700, David Daney wrote: > The kexec/kdump tools need to know where the .bss is so it can be > included in the core dump. This allows vmcore-dmesg to have access to > the dmesg buffers of the crashed kernel as well as allowing the > debugger to examine

Re: [PATCH] usb: f_fs: Drop check on Reserved1 field on OS_DESC_EXT_COMPAT

On Mon, 13 Nov 2017 12:57:21 +0200, Felipe Balbi wrote: > Good point. Then how about we just force the value to 1 in f_fs.c and > remove the check? That seems reasonable. Something like this? -- >8 -- Subject: [PATCH] usb: f_fs: Force Reserved1=1 in OS_DESC_EXT_COMPAT The specification says

Re: [PATCH] usb: f_fs: Drop check on Reserved1 field on OS_DESC_EXT_COMPAT

On Mon, 13 Nov 2017 12:57:21 +0200, Felipe Balbi wrote: > Good point. Then how about we just force the value to 1 in f_fs.c and > remove the check? That seems reasonable. Something like this? -- >8 -- Subject: [PATCH] usb: f_fs: Force Reserved1=1 in OS_DESC_EXT_COMPAT The specification says

[ANNOUNCE] iproute2 4.14.1

Release of iproute2 for Linux 4.14 Update to iproute2 utility to support new features in Linux 4.14. This release features JSON output for many commands and greater support of offloading to hardware. As well as many fixes. Version 4.14.1 is because of late patch that showed up for building on

[ANNOUNCE] iproute2 4.14.1

Release of iproute2 for Linux 4.14 Update to iproute2 utility to support new features in Linux 4.14. This release features JSON output for many commands and greater support of offloading to hardware. As well as many fixes. Version 4.14.1 is because of late patch that showed up for building on

Re: drivers/firmware/google/vpd.c: duplicate sysfs file

On 11/13/2017 06:41 AM, Guenter Roeck wrote: > > > On Sun, Nov 12, 2017 at 10:36 PM, Randy Dunlap > wrote: > > sysfs: cannot create duplicate filename '/devices/platform/vpd' > > on the second load of this driver.  I.e., > >

Re: drivers/firmware/google/vpd.c: duplicate sysfs file

On 11/13/2017 06:41 AM, Guenter Roeck wrote: > > > On Sun, Nov 12, 2017 at 10:36 PM, Randy Dunlap > wrote: > > sysfs: cannot create duplicate filename '/devices/platform/vpd' > > on the second load of this driver.  I.e., > > modprobe vpd-sysfs >

Re: [PATCH] mm: show stats for non-default hugepage sizes in /proc/meminfo

On 11/13/2017 10:11 AM, Roman Gushchin wrote: > On Mon, Nov 13, 2017 at 09:06:32AM -0800, Dave Hansen wrote: >> On 11/13/2017 08:03 AM, Roman Gushchin wrote: >>> To solve this problem, let's display stats for all hugepage sizes. >>> To provide the backward compatibility let's save the existing

Re: [PATCH] mm: show stats for non-default hugepage sizes in /proc/meminfo

On 11/13/2017 10:11 AM, Roman Gushchin wrote: > On Mon, Nov 13, 2017 at 09:06:32AM -0800, Dave Hansen wrote: >> On 11/13/2017 08:03 AM, Roman Gushchin wrote: >>> To solve this problem, let's display stats for all hugepage sizes. >>> To provide the backward compatibility let's save the existing

<    3   4   5   6   7   8   9   10   11   12   >