[PATCH 04/23] kconfig: set SYMBOL_AUTO to the symbol marked with defconfig_list

The 'defconfig_list' is a weird attribute. If the '.config' is missing, conf_read_simple() iterates over all visible defaults, then it uses the first one for which fopen() succeeds. config DEFCONFIG_LIST string depends on !UML option defconfig_list default

[PATCH 15/23] kconfig: add CC_IS_GCC and GCC_VERSION

This will be useful to specify the required compiler version, like this: config FOO bool "Use Foo" depends on GCC_VERSION >= 408000 help This feature requires GCC 4.8 or newer. Signed-off-by: Masahiro Yamada --- init/Kconfig | 9 + 1 file changed, 9

[PATCH 01/23] kbuild: remove kbuild cache

The kbuild cache was introduced to remember the result of shell commands, some of which are expensive to compute, such as $(call cc-option,...). However, this turned out not so clear as I had first expected. Actually, it is problematic. For example, "$(CC) -print-file-name" is cached. If the

[PATCH 01/23] kbuild: remove kbuild cache

The kbuild cache was introduced to remember the result of shell commands, some of which are expensive to compute, such as $(call cc-option,...). However, this turned out not so clear as I had first expected. Actually, it is problematic. For example, "$(CC) -print-file-name" is cached. If the

Re: [PATCH 0/2] efivars: reading variables can generate SMIs

On Fri, Feb 16, 2018 at 11:18:12AM +, Ard Biesheuvel wrote: > On 16 February 2018 at 11:08, Borislav Petkov wrote: > > On Fri, Feb 16, 2018 at 10:58:47AM +, Ard Biesheuvel wrote: > >> By your own reasoning above, that's a no-no as well. > > > > I'm sure we can come up with

Re: [PATCH 0/2] efivars: reading variables can generate SMIs

On Fri, Feb 16, 2018 at 11:18:12AM +, Ard Biesheuvel wrote: > On 16 February 2018 at 11:08, Borislav Petkov wrote: > > On Fri, Feb 16, 2018 at 10:58:47AM +, Ard Biesheuvel wrote: > >> By your own reasoning above, that's a no-no as well. > > > > I'm sure we can come up with some emulation

[PATCH 12/23] kconfig: replace $UNAME_RELEASE with function call

With 'shell-stdout' supported, we can make it self-contained in Kconfig. Signed-off-by: Masahiro Yamada --- Makefile | 3 +-- init/Kconfig | 4 ++-- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile index e9fc7c9..6491404

[PATCH 12/23] kconfig: replace $UNAME_RELEASE with function call

With 'shell-stdout' supported, we can make it self-contained in Kconfig. Signed-off-by: Masahiro Yamada --- Makefile | 3 +-- init/Kconfig | 4 ++-- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile index e9fc7c9..6491404 100644 --- a/Makefile +++

[PATCH 05/23] kconfig: move and rename sym_expand_string_value()

This helper expands symbols contained in a string. I am about to change it to expand environments instead of symbols. Also, I will add function expansion later. Rename it to expand_string_value(), and move it to util.c, which is a more suitable place. Signed-off-by: Masahiro Yamada

[PATCH 05/23] kconfig: move and rename sym_expand_string_value()

This helper expands symbols contained in a string. I am about to change it to expand environments instead of symbols. Also, I will add function expansion later. Rename it to expand_string_value(), and move it to util.c, which is a more suitable place. Signed-off-by: Masahiro Yamada ---

[PATCH 08/23] kconfig: add 'macro' keyword to support user-defined function

Now, we got a basic ability to test compiler capability in Kconfig. config CC_HAS_STACKPROTECTOR bool default $(shell $CC -Werror -fstack-protector -c -x c /dev/null -o /dev/null) This works, but it is ugly to repeat this long boilerplate. We want to describe like this: config

[PATCH 08/23] kconfig: add 'macro' keyword to support user-defined function

Now, we got a basic ability to test compiler capability in Kconfig. config CC_HAS_STACKPROTECTOR bool default $(shell $CC -Werror -fstack-protector -c -x c /dev/null -o /dev/null) This works, but it is ugly to repeat this long boilerplate. We want to describe like this: config

[PATCH 17/23] kconfig: add CC_IS_CLANG and CLANG_VERSION

This will be useful to describe the clang version dependency. Signed-off-by: Masahiro Yamada --- init/Kconfig | 8 scripts/clang-version.sh | 24 +++- 2 files changed, 19 insertions(+), 13 deletions(-) diff --git

[PATCH 17/23] kconfig: add CC_IS_CLANG and CLANG_VERSION

This will be useful to describe the clang version dependency. Signed-off-by: Masahiro Yamada --- init/Kconfig | 8 scripts/clang-version.sh | 24 +++- 2 files changed, 19 insertions(+), 13 deletions(-) diff --git a/init/Kconfig b/init/Kconfig index

[PATCH] x86/microcode: Check microcode revision before updating sibling threads

After updating microcode on one of the threads in the core, the thread sibling automatically gets the update since the microcode resources are shared. Check the ucode revision on the cpu before performing a ucode update. Signed-off-by: Ashok Raj Cc: X86 ML

[PATCH] x86/microcode: Check microcode revision before updating sibling threads

After updating microcode on one of the threads in the core, the thread sibling automatically gets the update since the microcode resources are shared. Check the ucode revision on the cpu before performing a ucode update. Signed-off-by: Ashok Raj Cc: X86 ML Cc: LKML ---

[PATCH 16/23] kbuild: add clang-version.sh

From: Sami Tolvanen Based on gcc-version.sh, clang-version.sh prints out the correct version of clang. Signed-off-by: Sami Tolvanen Tested-by: Nick Desaulniers Signed-off-by: Masahiro Yamada

[PATCH 16/23] kbuild: add clang-version.sh

From: Sami Tolvanen Based on gcc-version.sh, clang-version.sh prints out the correct version of clang. Signed-off-by: Sami Tolvanen Tested-by: Nick Desaulniers Signed-off-by: Masahiro Yamada --- scripts/clang-version.sh | 33 + 1 file changed, 33

[PATCH 19/23] kcov: imply GCC_PLUGINS and GCC_PLUGIN_SANCOV instead of select'ing them

As Documentation/kbuild/kconfig-language.txt notes, 'select' should be used with care - it forces a lower limit of another symbol, ignoring the dependency. In this case, KCOV can select GCC_PLUGINS even if 'depends on HAVE_GCC_PLUGINS' is unmet. 'imply' is modest enough to observe the

[PATCH 19/23] kcov: imply GCC_PLUGINS and GCC_PLUGIN_SANCOV instead of select'ing them

As Documentation/kbuild/kconfig-language.txt notes, 'select' should be used with care - it forces a lower limit of another symbol, ignoring the dependency. In this case, KCOV can select GCC_PLUGINS even if 'depends on HAVE_GCC_PLUGINS' is unmet. 'imply' is modest enough to observe the

[PATCH 13/23] kconfig: expand environments/functions in (main)menu, comment, prompt

Expand the prompt passed to menu_add_prompt(). This affects 'mainmenu', 'menu', 'prompt', 'comment'. Another good thing is, I am fixing the memory leak for the case without mainmenu. The 'mainmenu' should be independent of user configuration. So, its prompt can be expanded in the first parse

[PATCH 11/23] kconfig: add 'shell-stdout' function

This is the second built-in function, which retrieves the first line of stdout from the given shell command. Example code: config CC_IS_GCC bool default $(shell $CC --version | grep -q gcc) config GCC_VERSION int default $(shell-stdout

[PATCH 13/23] kconfig: expand environments/functions in (main)menu, comment, prompt

Expand the prompt passed to menu_add_prompt(). This affects 'mainmenu', 'menu', 'prompt', 'comment'. Another good thing is, I am fixing the memory leak for the case without mainmenu. The 'mainmenu' should be independent of user configuration. So, its prompt can be expanded in the first parse

[PATCH 11/23] kconfig: add 'shell-stdout' function

This is the second built-in function, which retrieves the first line of stdout from the given shell command. Example code: config CC_IS_GCC bool default $(shell $CC --version | grep -q gcc) config GCC_VERSION int default $(shell-stdout

[PATCH 02/23] kbuild: remove CONFIG_CROSS_COMPILE support

Kbuild provides a couple of ways to specify CROSS_COMPILE: [1] Command line [2] Environment [3] arch/*/Makefile (only some architectures) [4] CONFIG_CROSS_COMPILE [4] is problematic for the compiler capability tests in Kconfig. CONFIG_CROSS_COMPILE allows users to change the compiler prefix from

[PATCH 02/23] kbuild: remove CONFIG_CROSS_COMPILE support

Kbuild provides a couple of ways to specify CROSS_COMPILE: [1] Command line [2] Environment [3] arch/*/Makefile (only some architectures) [4] CONFIG_CROSS_COMPILE [4] is problematic for the compiler capability tests in Kconfig. CONFIG_CROSS_COMPILE allows users to change the compiler prefix from

[PATCH 14/23] kconfig: show compiler version text in the top comment

The kernel configuration phase is now tightly coupled with the compiler in use. It will be nice to show the compiler information in Kconfig. The compiler information will be displayed like this: $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- config scripts/kconfig/conf --oldaskconfig

[PATCH 14/23] kconfig: show compiler version text in the top comment

The kernel configuration phase is now tightly coupled with the compiler in use. It will be nice to show the compiler information in Kconfig. The compiler information will be displayed like this: $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- config scripts/kconfig/conf --oldaskconfig

[PATCH] ARM: dts: sun7i: Enable HDMI support on the Banana Pi

From: Stefan Monnier Enable the display pipeline and HDMI output Signed-off-by: Stefan Monnier --- arch/arm/boot/dts/sun7i-a20-bananapi.dts | 25 + 1 file changed, 25 insertions(+) diff --git

[PATCH] ARM: dts: sun7i: Enable HDMI support on the Banana Pi

From: Stefan Monnier Enable the display pipeline and HDMI output Signed-off-by: Stefan Monnier --- arch/arm/boot/dts/sun7i-a20-bananapi.dts | 25 + 1 file changed, 25 insertions(+) diff --git a/arch/arm/boot/dts/sun7i-a20-bananapi.dts

Re: [tip:x86/pti] x86/speculation: Use IBRS if available before calling into firmware

On 02/11/2018 11:19 AM, tip-bot for David Woodhouse wrote: \ > }) > diff --git a/arch/x86/include/asm/nospec-branch.h > b/arch/x86/include/asm/nospec-branch.h > index 300cc15..788c4da 100644 > --- a/arch/x86/include/asm/nospec-branch.h > +++ b/arch/x86/include/asm/nospec-branch.h

Re: [tip:x86/pti] x86/speculation: Use IBRS if available before calling into firmware

On 02/11/2018 11:19 AM, tip-bot for David Woodhouse wrote: \ > }) > diff --git a/arch/x86/include/asm/nospec-branch.h > b/arch/x86/include/asm/nospec-branch.h > index 300cc15..788c4da 100644 > --- a/arch/x86/include/asm/nospec-branch.h > +++ b/arch/x86/include/asm/nospec-branch.h

[PATCH 18/23] gcov: remove CONFIG_GCOV_FORMAT_AUTODETECT

CONFIG_GCOV_FORMAT_AUTODETECT compiles either gcc_3_4.c or gcc_4_7.c according to your GCC version. We can achieve the equivalent behavior by setting reasonable default in the 'choice' with the knowledge of the compiler version. Users are still allowed to change it if they need to do so.

[PATCH 18/23] gcov: remove CONFIG_GCOV_FORMAT_AUTODETECT

CONFIG_GCOV_FORMAT_AUTODETECT compiles either gcc_3_4.c or gcc_4_7.c according to your GCC version. We can achieve the equivalent behavior by setting reasonable default in the 'choice' with the knowledge of the compiler version. Users are still allowed to change it if they need to do so.

[PATCH 00/23] kconfig: move compiler capability tests to Kconfig

I brushed up the implementation in this version. In the previous RFC, CC_HAS_ was described by using 'option shell=', like this: config CC_HAS_STACKPROTECTOR bool option shell="$CC -Werror -fstack-protector -c -x c /dev/null" After I thought a bit more, the following syntax is

[PATCH 00/23] kconfig: move compiler capability tests to Kconfig

I brushed up the implementation in this version. In the previous RFC, CC_HAS_ was described by using 'option shell=', like this: config CC_HAS_STACKPROTECTOR bool option shell="$CC -Werror -fstack-protector -c -x c /dev/null" After I thought a bit more, the following syntax is

[PATCH 06/23] kconfig: reference environments directly and remove 'option env=' syntax

To get an environment value, Kconfig needs to define a symbol using "option env=" syntax. It is tedious to add a config entry for each environment given that we need more environments such as 'CC', 'AS', 'srctree' etc. to evaluate the compiler capability in Kconfig. Adding '$' to symbols is

[PATCH 21/23] gcc-plugins: move GCC version check for PowerPC to Kconfig

For PowerPC, GCC 5.2 is the requirement for GCC plugins. Move the version check to Kconfig, and remove the ugly checker. Signed-off-by: Masahiro Yamada --- arch/powerpc/Kconfig | 2 +- scripts/Makefile.gcc-plugins | 8 2 files changed, 1

[PATCH 06/23] kconfig: reference environments directly and remove 'option env=' syntax

To get an environment value, Kconfig needs to define a symbol using "option env=" syntax. It is tedious to add a config entry for each environment given that we need more environments such as 'CC', 'AS', 'srctree' etc. to evaluate the compiler capability in Kconfig. Adding '$' to symbols is

[PATCH 21/23] gcc-plugins: move GCC version check for PowerPC to Kconfig

For PowerPC, GCC 5.2 is the requirement for GCC plugins. Move the version check to Kconfig, and remove the ugly checker. Signed-off-by: Masahiro Yamada --- arch/powerpc/Kconfig | 2 +- scripts/Makefile.gcc-plugins | 8 2 files changed, 1 insertion(+), 9 deletions(-) diff

[PATCH] Staging: xgifb: fix lines should not end with open parenthesis in vb_setmode.c

This patch fixes up line should not end with open parenthesis found by checkpatch.pl script. Signed-off-by: Yash Omer --- drivers/staging/xgifb/vb_setmode.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/xgifb/vb_setmode.c

[PATCH] Staging: xgifb: fix lines should not end with open parenthesis in vb_setmode.c

This patch fixes up line should not end with open parenthesis found by checkpatch.pl script. Signed-off-by: Yash Omer --- drivers/staging/xgifb/vb_setmode.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/xgifb/vb_setmode.c

[PATCH 22/23] gcc-plugins: test GCC plugin support in Kconfig

Run scripts/gcc-plugin.sh from Kconfig. Users can enable GCC_PLUGINS only when it is supported. I dropped 'depends on GCC_VERSION >= 40800'. I guess gcc-plugin.sh will not pass with GCC 4.7 or older. Signed-off-by: Masahiro Yamada --- arch/Kconfig

[PATCH 22/23] gcc-plugins: test GCC plugin support in Kconfig

Run scripts/gcc-plugin.sh from Kconfig. Users can enable GCC_PLUGINS only when it is supported. I dropped 'depends on GCC_VERSION >= 40800'. I guess gcc-plugin.sh will not pass with GCC 4.7 or older. Signed-off-by: Masahiro Yamada --- arch/Kconfig | 6 +++-

Re: [PATCH 2/6] ARM: davinci: update the nand driver names

On Fri, 16 Feb 2018 19:33:07 +0100 Boris Brezillon wrote: > On Fri, 16 Feb 2018 17:47:08 +0100 > Bartosz Golaszewski wrote: > > > From: Bartosz Golaszewski > > > > Since commit d8e22fb4ccac ("ARM: da850: add the nand

[PATCH 10/23] stack-protector: test compiler capability in Kconfig and drop AUTO mode

Add CC_HAS_STACKPROTECTOR(_STRONG) to test if the compiler supports -fstack-protector(-strong) option. X86 has additional shell scripts in case the compiler supports the option, but generates broken code. I added CC_HAS_SANE_STACKPROTECTOR to test this. I had to add -m32 to

Re: [PATCH 2/6] ARM: davinci: update the nand driver names

On Fri, 16 Feb 2018 19:33:07 +0100 Boris Brezillon wrote: > On Fri, 16 Feb 2018 17:47:08 +0100 > Bartosz Golaszewski wrote: > > > From: Bartosz Golaszewski > > > > Since commit d8e22fb4ccac ("ARM: da850: add the nand dev_id to the clock > > lookup table") we can no longer correctly lookup

[PATCH 10/23] stack-protector: test compiler capability in Kconfig and drop AUTO mode

Add CC_HAS_STACKPROTECTOR(_STRONG) to test if the compiler supports -fstack-protector(-strong) option. X86 has additional shell scripts in case the compiler supports the option, but generates broken code. I added CC_HAS_SANE_STACKPROTECTOR to test this. I had to add -m32 to

[PATCH 23/23] gcc-plugins: enable GCC_PLUGINS for COMPILE_TEST

The plugin availability is checked in Kconfig, so all{yes,mod}config will not be bothered. Remove 'depends on !COMPILE_TEST'. Signed-off-by: Masahiro Yamada --- arch/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/Kconfig b/arch/Kconfig index

[PATCH 23/23] gcc-plugins: enable GCC_PLUGINS for COMPILE_TEST

The plugin availability is checked in Kconfig, so all{yes,mod}config will not be bothered. Remove 'depends on !COMPILE_TEST'. Signed-off-by: Masahiro Yamada --- arch/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/Kconfig b/arch/Kconfig index d567bd1..5b5610b 100644 ---

[PATCH 20/23] gcc-plugins: always build plugins with C++

If the target compiler is GCC 4.8 or newer, plugins are compiled with HOSTCXX. Otherwise, gcc-plugin.sh will select HOSTCC or HOSTCXX. To simpily things, let's decide GCC 4.8 is the requirement for GCC pulgins. With this, plugins are always built with HOSTCXX. This is a feature of advanced

[PATCH 03/23] kconfig: add xstrdup() helper

We already have xmalloc(), xcalloc(), and xrealloc((). Add xstrdup() as well to save tedious error handling. Signed-off-by: Masahiro Yamada --- scripts/kconfig/confdata.c | 2 +- scripts/kconfig/kxgettext.c | 2 +- scripts/kconfig/lkc.h | 1 +

[PATCH 20/23] gcc-plugins: always build plugins with C++

If the target compiler is GCC 4.8 or newer, plugins are compiled with HOSTCXX. Otherwise, gcc-plugin.sh will select HOSTCC or HOSTCXX. To simpily things, let's decide GCC 4.8 is the requirement for GCC pulgins. With this, plugins are always built with HOSTCXX. This is a feature of advanced

[PATCH 03/23] kconfig: add xstrdup() helper

We already have xmalloc(), xcalloc(), and xrealloc((). Add xstrdup() as well to save tedious error handling. Signed-off-by: Masahiro Yamada --- scripts/kconfig/confdata.c | 2 +- scripts/kconfig/kxgettext.c | 2 +- scripts/kconfig/lkc.h | 1 + scripts/kconfig/symbol.c| 4 ++--

[PATCH 07/23] kconfig: add function support and implement 'shell' function

This commit adds a new concept 'function' to Kconfig. A function call resembles a variable reference with arguments, and looks like this: $(function arg1, arg2, arg3, ...) (Actually, this syntax was inspired by Makefile.) Real examples will look like this: $(shell true) $(cc-option

[PATCH 07/23] kconfig: add function support and implement 'shell' function

This commit adds a new concept 'function' to Kconfig. A function call resembles a variable reference with arguments, and looks like this: $(function arg1, arg2, arg3, ...) (Actually, this syntax was inspired by Makefile.) Real examples will look like this: $(shell true) $(cc-option

Re: arm64/v4.16-rc1: KASAN: use-after-free Read in finish_task_switch

On Fri, Feb 16, 2018 at 05:17:57PM +, Mathieu Desnoyers wrote: > - On Feb 16, 2018, at 11:53 AM, Mark Rutland mark.rutl...@arm.com wrote: > > I suspect we have a bogus mmdrop or mmput elsewhere, and do_exit() and > > finish_task_switch() aren't to blame. > > Currently reviewing:

Re: arm64/v4.16-rc1: KASAN: use-after-free Read in finish_task_switch

On Fri, Feb 16, 2018 at 05:17:57PM +, Mathieu Desnoyers wrote: > - On Feb 16, 2018, at 11:53 AM, Mark Rutland mark.rutl...@arm.com wrote: > > I suspect we have a bogus mmdrop or mmput elsewhere, and do_exit() and > > finish_task_switch() aren't to blame. > > Currently reviewing:

Re: [PATCH 04/12] usb: common: Small class for USB role switches

On 02/16/2018 02:47 AM, Hans de Goede wrote: > From: Heikki Krogerus > > diff --git a/drivers/usb/common/roles.c b/drivers/usb/common/roles.c > new file mode 100644 > index ..923e3721d183 > --- /dev/null > +++ b/drivers/usb/common/roles.c > @@ -0,0

Re: [PATCH 04/12] usb: common: Small class for USB role switches

On 02/16/2018 02:47 AM, Hans de Goede wrote: > From: Heikki Krogerus > > diff --git a/drivers/usb/common/roles.c b/drivers/usb/common/roles.c > new file mode 100644 > index ..923e3721d183 > --- /dev/null > +++ b/drivers/usb/common/roles.c > @@ -0,0 +1,305 @@ > +//

Re: [PATCH 2/6] ARM: davinci: update the nand driver names

On Fri, 16 Feb 2018 17:47:08 +0100 Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > Since commit d8e22fb4ccac ("ARM: da850: add the nand dev_id to the clock > lookup table") we can no longer correctly lookup the nand clock when > booting in

Re: [PATCH 2/6] ARM: davinci: update the nand driver names

On Fri, 16 Feb 2018 17:47:08 +0100 Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > Since commit d8e22fb4ccac ("ARM: da850: add the nand dev_id to the clock > lookup table") we can no longer correctly lookup the nand clock when > booting in legacy mode. Said commit added a dev_id to

Re: [PATCH 1/6] nand: davinci: rename the platform driver

Hi Bartosz Prefix should be "mtd: nand: davinci:" On Fri, 16 Feb 2018 17:47:07 +0100 Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > Commit d8e22fb4ccac ("ARM: da850: add the nand dev_id to the clock > lookup table") broke the nand support

Re: [PATCH 1/6] nand: davinci: rename the platform driver

Hi Bartosz Prefix should be "mtd: nand: davinci:" On Fri, 16 Feb 2018 17:47:07 +0100 Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > Commit d8e22fb4ccac ("ARM: da850: add the nand dev_id to the clock > lookup table") broke the nand support in board file mode for > da850-based

Re: [PATCH v21 1/5] xbitmap: Introduce xbitmap

On Fri, Feb 16, 2018 at 07:44:50PM +0200, Andy Shevchenko wrote: > On Tue, Jan 9, 2018 at 1:10 PM, Wei Wang wrote: > > From: Matthew Wilcox > > > > The eXtensible Bitmap is a sparse bitmap representation which is > > efficient for set bits which tend

Re: [PATCH v21 1/5] xbitmap: Introduce xbitmap

On Fri, Feb 16, 2018 at 07:44:50PM +0200, Andy Shevchenko wrote: > On Tue, Jan 9, 2018 at 1:10 PM, Wei Wang wrote: > > From: Matthew Wilcox > > > > The eXtensible Bitmap is a sparse bitmap representation which is > > efficient for set bits which tend to cluster. It supports up to > > 'unsigned

Re: [RFC PATCH] usb: hcd: complete URBs in threaded-IRQ context instead of tasklet

On Fri, 16 Feb 2018, Sebastian Andrzej Siewior wrote: > I've been going over Frederic's softirq patches and it seems that there > were two problems. One was network related, the other was Mauro's USB > dvb-[stc] device which was not able to stream properly over time. > > Here is an attempt to

Re: [PATCH ghak8 ALT4 V4 0/3] audit: show more information for entries with anonymous parents

On Fri, Feb 16, 2018 at 3:23 AM, Richard Guy Briggs wrote: > On 2018-02-15 17:15, Paul Moore wrote: >> On Mon, Feb 12, 2018 at 12:02 AM, Richard Guy Briggs wrote: >> > More than one filesystem was causing hundreds to thousands of null PATH >> > records to be

Re: [RFC PATCH] usb: hcd: complete URBs in threaded-IRQ context instead of tasklet

On Fri, 16 Feb 2018, Sebastian Andrzej Siewior wrote: > I've been going over Frederic's softirq patches and it seems that there > were two problems. One was network related, the other was Mauro's USB > dvb-[stc] device which was not able to stream properly over time. > > Here is an attempt to

Re: [PATCH ghak8 ALT4 V4 0/3] audit: show more information for entries with anonymous parents

On Fri, Feb 16, 2018 at 3:23 AM, Richard Guy Briggs wrote: > On 2018-02-15 17:15, Paul Moore wrote: >> On Mon, Feb 12, 2018 at 12:02 AM, Richard Guy Briggs wrote: >> > More than one filesystem was causing hundreds to thousands of null PATH >> > records to be associated with the *init_module

Re: plan9 semantics on Linux - mount namespaces

Enrico Weigelt writes: > On 13.02.2018 22:12, Enrico Weigelt wrote: > > CC @contain...@lists.linux-foundation.org > >> Hi folks, >> >> >> I'm currently trying to implement plan9 semantics on Linux and >> yet sorting out how to do the mount namespace handling. >> >> On plan9, any

Re: plan9 semantics on Linux - mount namespaces

Enrico Weigelt writes: > On 13.02.2018 22:12, Enrico Weigelt wrote: > > CC @contain...@lists.linux-foundation.org > >> Hi folks, >> >> >> I'm currently trying to implement plan9 semantics on Linux and >> yet sorting out how to do the mount namespace handling. >> >> On plan9, any unprivileged

Re: [v4.14-rt][report] arm: just another rcu_note_context_switch

On 02/16/2018 05:30 AM, Sebastian Andrzej Siewior wrote: On 2018-02-14 16:12:42 [-0600], Grygorii Strashko wrote: Hi All, Hi, I can see below warning during boot on few TI boards am437x-idk, am335x-evm, am335x-ice All of them are non-SMP I somehow missed the !SMP kernel… What about

Re: [v4.14-rt][report] arm: just another rcu_note_context_switch

On 02/16/2018 05:30 AM, Sebastian Andrzej Siewior wrote: On 2018-02-14 16:12:42 [-0600], Grygorii Strashko wrote: Hi All, Hi, I can see below warning during boot on few TI boards am437x-idk, am335x-evm, am335x-ice All of them are non-SMP I somehow missed the !SMP kernel… What about

Re: [PATCH 2/3] x86/mm: introduce __PAGE_KERNEL_GLOBAL

Dave Hansen wrote: > On 02/16/2018 09:47 AM, Nadav Amit wrote: >>> But, this also means that we now get *no* opportunity to use >>> global pages with PTI, even for data which is shared such as the >>> cpu_entry_area and entry/exit text. >> >> Doesn’t this patch

Re: [PATCH 2/3] x86/mm: introduce __PAGE_KERNEL_GLOBAL

Dave Hansen wrote: > On 02/16/2018 09:47 AM, Nadav Amit wrote: >>> But, this also means that we now get *no* opportunity to use >>> global pages with PTI, even for data which is shared such as the >>> cpu_entry_area and entry/exit text. >> >> Doesn’t this patch change the kernel behavior when

Re: [PATCH v3 2/2] net: ethernet: nixge: Add support for National Instruments XGE netdev

On Fri, Feb 16, 2018 at 09:00:33AM -0800, Moritz Fischer wrote: > +#define NIXGE_MDIO_CLAUSE45 BIT(12) > +#define NIXGE_MDIO_CLAUSE22 0 > +#define NIXGE_MDIO_OP(n) (((n) & 0x3) << 10) > +#define NIXGE_MDIO_OP_ADDRESS0 > +#define NIXGE_MDIO_OP_WRITE BIT(0) > +#define

Re: [PATCH v3 2/2] net: ethernet: nixge: Add support for National Instruments XGE netdev

On Fri, Feb 16, 2018 at 09:00:33AM -0800, Moritz Fischer wrote: > +#define NIXGE_MDIO_CLAUSE45 BIT(12) > +#define NIXGE_MDIO_CLAUSE22 0 > +#define NIXGE_MDIO_OP(n) (((n) & 0x3) << 10) > +#define NIXGE_MDIO_OP_ADDRESS0 > +#define NIXGE_MDIO_OP_WRITE BIT(0) > +#define

Re: [PATCH 1/4] perf record: Provide detailed information on s390 CPU

Em Fri, Feb 16, 2018 at 01:55:43PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Tue, Feb 13, 2018 at 04:14:16PM +0100, Thomas Richter escreveu: > > > 4938.13 ubuntu:16.04-x-s390 : FAIL s390x-linux-gnu-gcc > (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609 > > > Humm, this

Re: [PATCH 1/4] perf record: Provide detailed information on s390 CPU

Em Fri, Feb 16, 2018 at 01:55:43PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Tue, Feb 13, 2018 at 04:14:16PM +0100, Thomas Richter escreveu: > > > 4938.13 ubuntu:16.04-x-s390 : FAIL s390x-linux-gnu-gcc > (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609 > > > Humm, this

Re: [PATCH 4.4 095/108] Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" version

On Fri, Feb 16, 2018 at 07:48:50AM +0100, Greg Kroah-Hartman wrote: > On Thu, Feb 15, 2018 at 06:31:48PM -0800, Brian Norris wrote: > > On Thu, Feb 15, 2018 at 04:17:32PM +0100, Greg Kroah-Hartman wrote: > > > 4.4-stable review patch. If anyone has any objections, please let me > > > know. > >

Re: [PATCH 4.4 095/108] Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" version

On Fri, Feb 16, 2018 at 07:48:50AM +0100, Greg Kroah-Hartman wrote: > On Thu, Feb 15, 2018 at 06:31:48PM -0800, Brian Norris wrote: > > On Thu, Feb 15, 2018 at 04:17:32PM +0100, Greg Kroah-Hartman wrote: > > > 4.4-stable review patch. If anyone has any objections, please let me > > > know. > >

[PATCH v2 3/3] percpu: allow select gfp to be passed to underlying allocators

The prior patch added support for passing gfp flags through to the underlying allocators. This patch allows users to pass along gfp flags (currently only __GFP_NORETRY and __GFP_NOWARN) to the underlying allocators. This should allow users to decide if they are ok with failing allocations

[PATCH v2 3/3] percpu: allow select gfp to be passed to underlying allocators

The prior patch added support for passing gfp flags through to the underlying allocators. This patch allows users to pass along gfp flags (currently only __GFP_NORETRY and __GFP_NOWARN) to the underlying allocators. This should allow users to decide if they are ok with failing allocations

[PATCH v2 2/3] percpu: add __GFP_NORETRY semantics to the percpu balancing path

Percpu memory using the vmalloc area based chunk allocator lazily populates chunks by first requesting the full virtual address space required for the chunk and subsequently adding pages as allocations come through. To ensure atomic allocations can succeed, a workqueue item is used to maintain a

[PATCH v2 2/3] percpu: add __GFP_NORETRY semantics to the percpu balancing path

Percpu memory using the vmalloc area based chunk allocator lazily populates chunks by first requesting the full virtual address space required for the chunk and subsequently adding pages as allocations come through. To ensure atomic allocations can succeed, a workqueue item is used to maintain a

Re: [PATCH 1/1] perf: Add CPU hotplug support for events

On 02/16/2018 12:21 AM, Peter Zijlstra wrote: On Thu, Feb 15, 2018 at 03:01:41PM -0800, Raghavendra Rao Ananta wrote: Perf framework doesn't allow prevserving CPU events across CPU hotplugs. The events are scheduled out as and when the CPU walks offline. Moreover, the framework also doesn't

Re: [PATCH 1/1] perf: Add CPU hotplug support for events

On 02/16/2018 12:21 AM, Peter Zijlstra wrote: On Thu, Feb 15, 2018 at 03:01:41PM -0800, Raghavendra Rao Ananta wrote: Perf framework doesn't allow prevserving CPU events across CPU hotplugs. The events are scheduled out as and when the CPU walks offline. Moreover, the framework also doesn't

Re: [PATCH 2/3] x86/mm: introduce __PAGE_KERNEL_GLOBAL

On 02/16/2018 09:47 AM, Nadav Amit wrote: >> But, this also means that we now get *no* opportunity to use >> global pages with PTI, even for data which is shared such as the >> cpu_entry_area and entry/exit text. > > Doesn’t this patch change the kernel behavior when the “nopti” > parameter is

Re: [PATCH 2/3] x86/mm: introduce __PAGE_KERNEL_GLOBAL

On 02/16/2018 09:47 AM, Nadav Amit wrote: >> But, this also means that we now get *no* opportunity to use >> global pages with PTI, even for data which is shared such as the >> cpu_entry_area and entry/exit text. > > Doesn’t this patch change the kernel behavior when the “nopti” > parameter is

Re: [PATCH] extable: Make init_kernel_text() global

On Fri, 16 Feb 2018 11:57:44 -0600 Josh Poimboeuf wrote: > On Fri, Feb 16, 2018 at 11:55:54AM -0500, Jason Baron wrote: > > > +/* Disable any jump label entries in __init code */ > > > +void __init jump_label_invalidate_init(void) > > > +{ > > > + struct jump_entry

Re: [PATCH] extable: Make init_kernel_text() global

On Fri, 16 Feb 2018 11:57:44 -0600 Josh Poimboeuf wrote: > On Fri, Feb 16, 2018 at 11:55:54AM -0500, Jason Baron wrote: > > > +/* Disable any jump label entries in __init code */ > > > +void __init jump_label_invalidate_init(void) > > > +{ > > > + struct jump_entry *iter_start =

Re: [PATCH 4/4] fs/dcache: Avoid the try_lock loops in dentry_kill()

On Fri, Feb 16, 2018 at 7:09 AM, John Ogness wrote: > dentry_kill() holds dentry->d_lock and needs to acquire both > dentry->d_inode->i_lock and dentry->d_parent->d_lock. This cannot be > done with spin_lock() operations because it's the reverse of the > regular lock

Re: [PATCH 4/4] fs/dcache: Avoid the try_lock loops in dentry_kill()

On Fri, Feb 16, 2018 at 7:09 AM, John Ogness wrote: > dentry_kill() holds dentry->d_lock and needs to acquire both > dentry->d_inode->i_lock and dentry->d_parent->d_lock. This cannot be > done with spin_lock() operations because it's the reverse of the > regular lock order. To avoid ABBA

Re: [PATCH 1/2] kernel/sofirq: consolidate common code in __tasklet_schedule() + _hi_

On Fri, 16 Feb 2018 18:55:09 +0100 Sebastian Andrzej Siewior wrote: > > Should we add something like: > > > > WARN_ON_ONCE(!in_atomic()); > > > > ? > > Doubt it. this_cpu_ptr() screams already with CONFIG_DEBUG_PREEMPT. If that's the case then, yeah I agree. I

Re: [PATCH 1/2] kernel/sofirq: consolidate common code in __tasklet_schedule() + _hi_

On Fri, 16 Feb 2018 18:55:09 +0100 Sebastian Andrzej Siewior wrote: > > Should we add something like: > > > > WARN_ON_ONCE(!in_atomic()); > > > > ? > > Doubt it. this_cpu_ptr() screams already with CONFIG_DEBUG_PREEMPT. If that's the case then, yeah I agree. I couldn't remember if

Re: [PATCH] Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" version

Hi, On Fri, Feb 16, 2018 at 01:10:20PM +0100, Hans de Goede wrote: > On 16-02-18 12:45, Marcel Holtmann wrote: > > Hi Hans, > > > > > > > > > Commit 7d06d5895c15 ("Revert "Bluetooth: btusb: fix > > > > > > > QCA...suspend/resume"") > > > > > > > removed the setting of the BTUSB_RESET_RESUME

Re: [PATCH] Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" version

Hi, On Fri, Feb 16, 2018 at 01:10:20PM +0100, Hans de Goede wrote: > On 16-02-18 12:45, Marcel Holtmann wrote: > > Hi Hans, > > > > > > > > > Commit 7d06d5895c15 ("Revert "Bluetooth: btusb: fix > > > > > > > QCA...suspend/resume"") > > > > > > > removed the setting of the BTUSB_RESET_RESUME

[PATCH] extable: Make init_kernel_text() global

On Fri, Feb 16, 2018 at 11:55:54AM -0500, Jason Baron wrote: > > +/* Disable any jump label entries in __init code */ > > +void __init jump_label_invalidate_init(void) > > +{ > > + struct jump_entry *iter_start = __start___jump_table; > > + struct jump_entry *iter_stop = __stop___jump_table; >

[PATCH] extable: Make init_kernel_text() global

On Fri, Feb 16, 2018 at 11:55:54AM -0500, Jason Baron wrote: > > +/* Disable any jump label entries in __init code */ > > +void __init jump_label_invalidate_init(void) > > +{ > > + struct jump_entry *iter_start = __start___jump_table; > > + struct jump_entry *iter_stop = __stop___jump_table; >

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