[x86/mm/kasan] d17a1d97dc: WARNING:at_lib/stackdepot.c:#depot_save_stack

Hi Andrey, FYI, we noticed the following commit (built with gcc-7): commit: d17a1d97dc208d664c91cc387ffb752c7f85dc61 ("x86/mm/kasan: don't use vmemmap_populate() to initialize shadow") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity

[x86/mm/kasan] d17a1d97dc: WARNING:at_lib/stackdepot.c:#depot_save_stack

Hi Andrey, FYI, we noticed the following commit (built with gcc-7): commit: d17a1d97dc208d664c91cc387ffb752c7f85dc61 ("x86/mm/kasan: don't use vmemmap_populate() to initialize shadow") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity

Re: [PATCH v2] checkpatch: Add a warning for log messages that don't end in a new line

On Sun, 2017-11-26 at 23:44 +0100, Julia Lawall wrote: > My semantic patch and results are below. The semantic patch has some > features that may or may not be desired: > > 1. It goes beyond printk, pr_xxx, dev_xxx, and netdev_xxx, by finding > functions that are sometimes used with a format

Re: [PATCH v2] checkpatch: Add a warning for log messages that don't end in a new line

On Sun, 2017-11-26 at 23:44 +0100, Julia Lawall wrote: > My semantic patch and results are below. The semantic patch has some > features that may or may not be desired: > > 1. It goes beyond printk, pr_xxx, dev_xxx, and netdev_xxx, by finding > functions that are sometimes used with a format

f7dd250789 ("gcc-plugins: structleak: add option to init all vars used as byref args"): BUG: KASAN: use-after-scope in pcpu_setup_first_chunk

Hi Ard, FYI this commit triggers one new KASAN bug. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit f7dd2507893cc3425d3ffc2369559619960befb0 Author: Ard Biesheuvel AuthorDate: Sun Aug 6 12:06:27 2017 +0100 Commit: Kees Cook

f7dd250789 ("gcc-plugins: structleak: add option to init all vars used as byref args"): BUG: KASAN: use-after-scope in pcpu_setup_first_chunk

Hi Ard, FYI this commit triggers one new KASAN bug. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit f7dd2507893cc3425d3ffc2369559619960befb0 Author: Ard Biesheuvel AuthorDate: Sun Aug 6 12:06:27 2017 +0100 Commit: Kees Cook CommitDate: Mon Aug 7

Re: [PATCH 2/2] KVM: x86: Allow userspace to define what's the microcode version

2017-11-27 0:41 GMT+08:00 Filippo Sironi : > ... that the guest should see. > Guest operating systems may check the microcode version to decide whether > to disable certain features that are known to be buggy up to certain > microcode versions. Address the issue by making the

Re: [PATCH 2/2] KVM: x86: Allow userspace to define what's the microcode version

2017-11-27 0:41 GMT+08:00 Filippo Sironi : > ... that the guest should see. > Guest operating systems may check the microcode version to decide whether > to disable certain features that are known to be buggy up to certain > microcode versions. Address the issue by making the microcode version >

unregister_netdevice: waiting for lo to become free. Usage count = 1

Hello! In case anyone wondering (like I did) if this is still an issue, it's not. It was fixed in 4.12.

unregister_netdevice: waiting for lo to become free. Usage count = 1

Hello! In case anyone wondering (like I did) if this is still an issue, it's not. It was fixed in 4.12.

Re: [PATCHv3 1/1] locking/qspinlock/x86: Avoid test-and-set when PV_DEDICATED is set

Hi Eduardo, 2017-11-16 12:54 GMT+08:00 Eduardo Valentin : > Hey Radim, > > On Thu, Nov 09, 2017 at 03:17:33PM +0100, Radim Krčmář wrote: > > > >> >> This is what I'm doubting, because the patch is adding about two >> thousand cycles to every spinlock-taken path. >> Doesn't this

Re: [PATCHv3 1/1] locking/qspinlock/x86: Avoid test-and-set when PV_DEDICATED is set

Hi Eduardo, 2017-11-16 12:54 GMT+08:00 Eduardo Valentin : > Hey Radim, > > On Thu, Nov 09, 2017 at 03:17:33PM +0100, Radim Krčmář wrote: > > > >> >> This is what I'm doubting, because the patch is adding about two >> thousand cycles to every spinlock-taken path. >> Doesn't this patch yield better

Re: [PATCH v3 2/2] Protected O_CREAT open in sticky directories

On Fri, Nov 24, 2017 at 12:43:47PM +0100, Salvatore Mesoraca wrote: > 2017-11-24 11:53 GMT+01:00 David Laight : > > From: Alan Cox > >> Sent: 22 November 2017 16:52 > >> > >> On Wed, 22 Nov 2017 09:01:46 +0100 Salvatore Mesoraca > >> wrote: > >> >

Re: [PATCH v3 2/2] Protected O_CREAT open in sticky directories

On Fri, Nov 24, 2017 at 12:43:47PM +0100, Salvatore Mesoraca wrote: > 2017-11-24 11:53 GMT+01:00 David Laight : > > From: Alan Cox > >> Sent: 22 November 2017 16:52 > >> > >> On Wed, 22 Nov 2017 09:01:46 +0100 Salvatore Mesoraca > >> wrote: > >> > >> > Disallows O_CREAT open missing the O_EXCL

linux-next: manual merge of the ipmi tree with Linus' tree

Hi Corey, Today's linux-next merge of the ipmi tree got a conflict in: drivers/char/ipmi/ipmi_si_intf.c between commit: e99e88a9d2b0 ("treewide: setup_timer() -> timer_setup()") from Linus' tree and commit: 942e1563654c ("ipmi: Stop timers before cleaning up the module") from the ipmi

linux-next: manual merge of the ipmi tree with Linus' tree

Hi Corey, Today's linux-next merge of the ipmi tree got a conflict in: drivers/char/ipmi/ipmi_si_intf.c between commit: e99e88a9d2b0 ("treewide: setup_timer() -> timer_setup()") from Linus' tree and commit: 942e1563654c ("ipmi: Stop timers before cleaning up the module") from the ipmi

Linux 4.15-rc1

So it's been the usual two weeks of merge window, and rc1 is out. And that normal time length is about the only thing usual about this merge window. Because of the indiscriminate mass slaughter of turkeys in the US last week, lots of people - including me - were on vacation. That meant that I had

Linux 4.15-rc1

So it's been the usual two weeks of merge window, and rc1 is out. And that normal time length is about the only thing usual about this merge window. Because of the indiscriminate mass slaughter of turkeys in the US last week, lots of people - including me - were on vacation. That meant that I had

linux-next: manual merge of the watchdog tree with Linus' tree

Hi Wim, Today's linux-next merge of the watchdog tree got a conflict in: drivers/watchdog/mpc8xxx_wdt.c between commit: e99e88a9d2b0 ("treewide: setup_timer() -> timer_setup()") from Linus' tree and commit: fbdec655375c ("watchdog: mpc8xxx: use the core worker function") from the

linux-next: manual merge of the watchdog tree with Linus' tree

Hi Wim, Today's linux-next merge of the watchdog tree got a conflict in: drivers/watchdog/mpc8xxx_wdt.c between commit: e99e88a9d2b0 ("treewide: setup_timer() -> timer_setup()") from Linus' tree and commit: fbdec655375c ("watchdog: mpc8xxx: use the core worker function") from the

RE: [PATCH] arm: l2c: unlock ways when in non-secure mode

Hi Russell, > Subject: Re: [PATCH] arm: l2c: unlock ways when in non-secure mode > > On Sun, Nov 26, 2017 at 08:25:30PM +0800, Peng Fan wrote: > > To boot Linux in Non-secure mode with l2x0, the l2x0 controller is > > enabled in secure mode and ways locked to make it seems L2 cache > > disabled

RE: [PATCH] arm: l2c: unlock ways when in non-secure mode

Hi Russell, > Subject: Re: [PATCH] arm: l2c: unlock ways when in non-secure mode > > On Sun, Nov 26, 2017 at 08:25:30PM +0800, Peng Fan wrote: > > To boot Linux in Non-secure mode with l2x0, the l2x0 controller is > > enabled in secure mode and ways locked to make it seems L2 cache > > disabled

Re: [PATCH 0/5] Consolidate init_task handling

On Sun, Nov 26, 2017 at 3:44 PM, David Howells wrote: > Linus Torvalds wrote: > >> So I don't see anything wrong with it, but I think it's 4.16 material. > > Okay. Side note: I had already pulled it into my tree, but then got cold feet. And

Re: [PATCH 0/5] Consolidate init_task handling

On Sun, Nov 26, 2017 at 3:44 PM, David Howells wrote: > Linus Torvalds wrote: > >> So I don't see anything wrong with it, but I think it's 4.16 material. > > Okay. Side note: I had already pulled it into my tree, but then got cold feet. And it would be lovely to get a few acks from

Re: [PATCH 0/5] Consolidate init_task handling

Linus Torvalds wrote: > So I don't see anything wrong with it, but I think it's 4.16 material. Okay. Thanks, David

Re: [PATCH 0/5] Consolidate init_task handling

Linus Torvalds wrote: > So I don't see anything wrong with it, but I think it's 4.16 material. Okay. Thanks, David

[PATCH] tpm: return a TPM_RC_COMMAND_CODE response if a command isn't implemented

According to the TPM Library Specification, a TPM device must do a command header validation before processing and return a TPM_RC_COMMAND_CODE code if the command is not implemented. So user-space will expect to handle that response as an error. But if the in-kernel resource manager is used

[PATCH] tpm: return a TPM_RC_COMMAND_CODE response if a command isn't implemented

According to the TPM Library Specification, a TPM device must do a command header validation before processing and return a TPM_RC_COMMAND_CODE code if the command is not implemented. So user-space will expect to handle that response as an error. But if the in-kernel resource manager is used

[patch V2 0/5] x86/kaiser: Boot time disabling and debug support

This patch series applies on top of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/mm It contains the following updates: - Don't set NX/PAGE_GLOBAL unconditionally - Get rid of the compile time PAGE_GLOBAL disabling - Add debug support for WX mappings in the

[patch V2 0/5] x86/kaiser: Boot time disabling and debug support

This patch series applies on top of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/mm It contains the following updates: - Don't set NX/PAGE_GLOBAL unconditionally - Get rid of the compile time PAGE_GLOBAL disabling - Add debug support for WX mappings in the

[patch V2 2/5] x86/kaiser: Simplify disabling of global pages

The current way of disabling global pages at compile time prevents boot time disabling of kaiser and creates unnecessary indirections. Global pages can be supressed by __supported_pte_mask as well. The shadow mappings set PAGE_GLOBAL for the minimal kernel mappings which are required for

[patch V2 5/5] x86/kaiser: Add boottime disable switch

KAISER comes with overhead. The most expensive part is the CR3 switching in the entry code. Add a command line parameter which allows to disable KAISER at boot time. Most code pathes simply check a variable, but the entry code uses a static branch. The other code pathes cannot use a static

[patch V2 2/5] x86/kaiser: Simplify disabling of global pages

The current way of disabling global pages at compile time prevents boot time disabling of kaiser and creates unnecessary indirections. Global pages can be supressed by __supported_pte_mask as well. The shadow mappings set PAGE_GLOBAL for the minimal kernel mappings which are required for

[patch V2 5/5] x86/kaiser: Add boottime disable switch

KAISER comes with overhead. The most expensive part is the CR3 switching in the entry code. Add a command line parameter which allows to disable KAISER at boot time. Most code pathes simply check a variable, but the entry code uses a static branch. The other code pathes cannot use a static

[patch V2 3/5] x86/dump_pagetables: Check KAISER shadow page table for WX pages

ptdump_walk_pgd_level_checkwx() checks the kernel page table for WX pages, but does not check the KAISER shadow page table. Restructure the code so that dmesg output is selected by an explicit argument and not implicit via checking the pgd argument for !NULL. Add the check for the shadow page

[patch V2 3/5] x86/dump_pagetables: Check KAISER shadow page table for WX pages

ptdump_walk_pgd_level_checkwx() checks the kernel page table for WX pages, but does not check the KAISER shadow page table. Restructure the code so that dmesg output is selected by an explicit argument and not implicit via checking the pgd argument for !NULL. Add the check for the shadow page

[patch V2 4/5] x86/mm/debug_pagetables: Allow dumping current pagetables

Add two debugfs files which allow to dump the pagetable of the current task. current_page_tables_knl dumps the regular page table. This is the page table which is normally shared between kernel and user space. If KAISER is enabled this is the kernel space mapping. If KAISER is enabled the second

[patch V2 4/5] x86/mm/debug_pagetables: Allow dumping current pagetables

Add two debugfs files which allow to dump the pagetable of the current task. current_page_tables_knl dumps the regular page table. This is the page table which is normally shared between kernel and user space. If KAISER is enabled this is the kernel space mapping. If KAISER is enabled the second

[patch V2 1/5] x86/kaiser: Respect disabled CPU features

PAGE_NX and PAGE_GLOBAL might be not supported or disabled on the command line, but KAISER sets them unconditionally. Add proper protection against that. Signed-off-by: Thomas Gleixner --- arch/x86/include/asm/pgtable_64.h |3 ++- arch/x86/mm/kaiser.c |

[patch V2 1/5] x86/kaiser: Respect disabled CPU features

PAGE_NX and PAGE_GLOBAL might be not supported or disabled on the command line, but KAISER sets them unconditionally. Add proper protection against that. Signed-off-by: Thomas Gleixner --- arch/x86/include/asm/pgtable_64.h |3 ++- arch/x86/mm/kaiser.c | 12 +++- 2

Re: FW: [RFC PATCH] tpm: don't return -EINVAL if TPM command validation fails

On 11/26/2017 03:18 PM, Jarkko Sakkinen wrote: > On Wed, Nov 22, 2017 at 09:16:25AM -0800, flihp wrote: >> The intent of this "mostly transparent" stuff is to convey that the RM >> should be as transparent as possible while acknowledging that there are >> some cases where it's not / can't be. I

Re: FW: [RFC PATCH] tpm: don't return -EINVAL if TPM command validation fails

On 11/26/2017 03:18 PM, Jarkko Sakkinen wrote: > On Wed, Nov 22, 2017 at 09:16:25AM -0800, flihp wrote: >> The intent of this "mostly transparent" stuff is to convey that the RM >> should be as transparent as possible while acknowledging that there are >> some cases where it's not / can't be. I

Re: [PATCH] staging: rtl8188eu: Fix private WEXT IOCTL calls

/linux/commits/ishraq-i-ashraf-gmail-com/staging-rtl8188eu-Fix-private-WEXT-IOCTL-calls/20171126-052554 config: x86_64-randconfig-u0-11270543 (attached as .config) compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010 reproduce: # save the attached .config to linux build tree make ARCH

Re: [PATCH] staging: rtl8188eu: Fix private WEXT IOCTL calls

/linux/commits/ishraq-i-ashraf-gmail-com/staging-rtl8188eu-Fix-private-WEXT-IOCTL-calls/20171126-052554 config: x86_64-randconfig-u0-11270543 (attached as .config) compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010 reproduce: # save the attached .config to linux build tree make ARCH

Re: [RFC PATCH] tpm: don't return -EINVAL if TPM command validation fails

On 11/26/2017 03:12 PM, Jarkko Sakkinen wrote: > On Wed, Nov 22, 2017 at 10:26:24AM +0100, Javier Martinez Canillas wrote: >> On 11/21/2017 09:29 PM, Roberts, William C wrote: >> >> [snip] >> > > Do you agree with Jason's suggestion to send a synthesized TPM command > in the that the

Re: [RFC PATCH] tpm: don't return -EINVAL if TPM command validation fails

On 11/26/2017 03:12 PM, Jarkko Sakkinen wrote: > On Wed, Nov 22, 2017 at 10:26:24AM +0100, Javier Martinez Canillas wrote: >> On 11/21/2017 09:29 PM, Roberts, William C wrote: >> >> [snip] >> > > Do you agree with Jason's suggestion to send a synthesized TPM command > in the that the

Re: [PATCH v2 1/2] ALSA: pcm: add SNDRV_PCM_FORMAT_{S, U}20

Hi, On 26.11.2017 10:27, Takashi Sakamoto wrote: > Hi, > (..) > Before applying this patch: > 166 /* FIXME: the following three formats are not defined properly > yet */ > 167 [SNDRV_PCM_FORMAT_MPEG] = { > 168 .le = -1, .signd = -1, > 169 }, > 170

Re: [PATCH v2 1/2] ALSA: pcm: add SNDRV_PCM_FORMAT_{S, U}20

Hi, On 26.11.2017 10:27, Takashi Sakamoto wrote: > Hi, > (..) > Before applying this patch: > 166 /* FIXME: the following three formats are not defined properly > yet */ > 167 [SNDRV_PCM_FORMAT_MPEG] = { > 168 .le = -1, .signd = -1, > 169 }, > 170

[PATCH v3 2/2] ASoC: fsl_ssi: add 20-bit sample format for AC'97 and use it for capture

When testing AC'97 capture on UDOO board (currently the only user of fsl_ssi driver in the AC'97 mode) it become obvious that there is a massive distortion above certain, small input signal. This problem has been traced to silicon errata ERR003778: "In AC97, 16-bit mode, received data is shifted

[PATCH v3 2/2] ASoC: fsl_ssi: add 20-bit sample format for AC'97 and use it for capture

When testing AC'97 capture on UDOO board (currently the only user of fsl_ssi driver in the AC'97 mode) it become obvious that there is a massive distortion above certain, small input signal. This problem has been traced to silicon errata ERR003778: "In AC97, 16-bit mode, received data is shifted

[PATCH v3 1/2] ALSA: pcm: add SNDRV_PCM_FORMAT_{S,U}20

This format is similar to existing SNDRV_PCM_FORMAT_{S,U}20_3 that keep 20-bit PCM samples in 3 bytes, however i.MX6 platform SSI FIFO does not allow 3-byte accesses (including DMA) so a 4-byte (more conventional) format is needed for it. Signed-off-by: Maciej S. Szmigiero

[PATCH v3 1/2] ALSA: pcm: add SNDRV_PCM_FORMAT_{S,U}20

This format is similar to existing SNDRV_PCM_FORMAT_{S,U}20_3 that keep 20-bit PCM samples in 3 bytes, however i.MX6 platform SSI FIFO does not allow 3-byte accesses (including DMA) so a 4-byte (more conventional) format is needed for it. Signed-off-by: Maciej S. Szmigiero --- Changes from v1:

Re: [PATCH 0/5] Consolidate init_task handling

On Sat, Nov 25, 2017 at 2:47 PM, David Howells wrote: > I've updated my git branch with changed descriptions, but the content is the > same. Ok, so I think this is definitely the right thing to do, but decided that it's also something that should cook in linux-next for a

Re: [PATCH 0/5] Consolidate init_task handling

On Sat, Nov 25, 2017 at 2:47 PM, David Howells wrote: > I've updated my git branch with changed descriptions, but the content is the > same. Ok, so I think this is definitely the right thing to do, but decided that it's also something that should cook in linux-next for a while just to make sure

linux-next: manual merge of the net tree with Linus' tree

Hi all, Today's linux-next merge of the net tree got a conflict in: net/rxrpc/call_object.c between commit: e99e88a9d2b0 ("treewide: setup_timer() -> timer_setup()") from Linus' tree and commit: 9faaff593404 ("rxrpc: Provide a different lockdep key for call->user_mutex for kernel

linux-next: manual merge of the net tree with Linus' tree

Hi all, Today's linux-next merge of the net tree got a conflict in: net/rxrpc/call_object.c between commit: e99e88a9d2b0 ("treewide: setup_timer() -> timer_setup()") from Linus' tree and commit: 9faaff593404 ("rxrpc: Provide a different lockdep key for call->user_mutex for kernel

Re: [PATCH 25/43] x86/mm/kaiser: Unmap kernel from userspace page tables (core patch), noexec=off

On Sun, 26 Nov 2017, Borislav Petkov wrote: > On Fri, Nov 24, 2017 at 06:23:53PM +0100, Ingo Molnar wrote: > > + * Take a PGD location (pgdp) and a pgd value that needs > > + * to be set there. Populates the shadow and returns > > + * the resulting PGD that must be set in the kernel copy > > + *

Re: [PATCH 25/43] x86/mm/kaiser: Unmap kernel from userspace page tables (core patch), noexec=off

On Sun, 26 Nov 2017, Borislav Petkov wrote: > On Fri, Nov 24, 2017 at 06:23:53PM +0100, Ingo Molnar wrote: > > + * Take a PGD location (pgdp) and a pgd value that needs > > + * to be set there. Populates the shadow and returns > > + * the resulting PGD that must be set in the kernel copy > > + *

Re: [PATCH v2] checkpatch: Add a warning for log messages that don't end in a new line

On Sun, 2017-11-26 at 10:38 -0700, Logan Gunthorpe wrote: > > On 25/11/17 11:01 PM, Joe Perches wrote: > > It doesn't really work. > > That's rather hyperbolic and I don't appreciate the tone. What I wrote is neither hyperbolic nor tonal. I'm rather familiar with checkpatch. High false

Re: [PATCH v2] checkpatch: Add a warning for log messages that don't end in a new line

On Sun, 2017-11-26 at 10:38 -0700, Logan Gunthorpe wrote: > > On 25/11/17 11:01 PM, Joe Perches wrote: > > It doesn't really work. > > That's rather hyperbolic and I don't appreciate the tone. What I wrote is neither hyperbolic nor tonal. I'm rather familiar with checkpatch. High false

Re: [PATCH 25/43] x86/mm/kaiser: Unmap kernel from userspace page tables (core patch), noexec=off

On Fri, Nov 24, 2017 at 06:23:53PM +0100, Ingo Molnar wrote: > + * Take a PGD location (pgdp) and a pgd value that needs > + * to be set there. Populates the shadow and returns > + * the resulting PGD that must be set in the kernel copy > + * of the page tables. > + */ > +static inline pgd_t

Re: [PATCH 25/43] x86/mm/kaiser: Unmap kernel from userspace page tables (core patch), noexec=off

On Fri, Nov 24, 2017 at 06:23:53PM +0100, Ingo Molnar wrote: > + * Take a PGD location (pgdp) and a pgd value that needs > + * to be set there. Populates the shadow and returns > + * the resulting PGD that must be set in the kernel copy > + * of the page tables. > + */ > +static inline pgd_t

Re: [PATCH 1/2] dt-bindings: clocksource: Add Spreadtrum SC9860 timer

On Fri, Nov 24, 2017 at 01:37:47PM +0800, Baolin Wang wrote: > This patch adds documentation of device tree bindings for the timers > found on Spreadtrum SC9860 platform. > > Signed-off-by: Baolin Wang > --- > .../bindings/timer/spreadtrum,sprd-timer.txt | 20

Re: [PATCH 1/2] dt-bindings: clocksource: Add Spreadtrum SC9860 timer

On Fri, Nov 24, 2017 at 01:37:47PM +0800, Baolin Wang wrote: > This patch adds documentation of device tree bindings for the timers > found on Spreadtrum SC9860 platform. > > Signed-off-by: Baolin Wang > --- > .../bindings/timer/spreadtrum,sprd-timer.txt | 20 > >

Re: [PATCH v2 06/11] dt-bindings: Document the Rockchip MIPI RX D-PHY bindings

On Fri, Nov 24, 2017 at 10:37:01AM +0800, Jacob Chen wrote: > Add DT bindings documentation for Rockchip MIPI D-PHY RX > > Signed-off-by: Jacob Chen > --- > .../bindings/media/rockchip-mipi-dphy.txt | 77 > ++ > 1 file changed, 77

Re: [PATCH v2 06/11] dt-bindings: Document the Rockchip MIPI RX D-PHY bindings

On Fri, Nov 24, 2017 at 10:37:01AM +0800, Jacob Chen wrote: > Add DT bindings documentation for Rockchip MIPI D-PHY RX > > Signed-off-by: Jacob Chen > --- > .../bindings/media/rockchip-mipi-dphy.txt | 77 > ++ > 1 file changed, 77 insertions(+) > create mode

[RFC 3/3] LSM: Add an example sample dynamic LSM

This adds an example LSM that utilizes the features added by the dynamically loadable LSMs patch. Once the module is unloaded, the command is once again allowed. It prevents the user from running: date --set="October 21 2015 16:29:00 PDT The behaviour can be verified by looking at:

[RFC 2/3] LSM: Add statistics about the invocation of dynamic hooks

This patch builds on the dynamic hooks patch. With dynamic hooks, /sys/kernel/security/lsm doesn't really make a lot of sense, because the administrator is more likely interested in the per-hook modules. There is now a /sys/kernel/security/dynamic_hooks/${HOOK_NAME} which has the currently

[RFC 3/3] LSM: Add an example sample dynamic LSM

This adds an example LSM that utilizes the features added by the dynamically loadable LSMs patch. Once the module is unloaded, the command is once again allowed. It prevents the user from running: date --set="October 21 2015 16:29:00 PDT The behaviour can be verified by looking at:

[RFC 2/3] LSM: Add statistics about the invocation of dynamic hooks

This patch builds on the dynamic hooks patch. With dynamic hooks, /sys/kernel/security/lsm doesn't really make a lot of sense, because the administrator is more likely interested in the per-hook modules. There is now a /sys/kernel/security/dynamic_hooks/${HOOK_NAME} which has the currently

[RFC 0/3] Safe, dynamically (un)loadable LSMs

This patchset introduces safe dynamic LSM support. It does this via SRCU-protected security hooks. It also EXPORT_SYMBOL_GPLs the symbols required to perform runtime loading, and unloading. The patchset is meant to introduce as little overhead as possible when not used. Additionally, the

[RFC 1/3] security: Add safe, dynamic (runtime-loadable) hook support

This patch adds dynamic security hooks. These hooks are designed to allow for safe runtime loading, and unloading. Each dynamic_security_hook is protected by an SRCU, allowing for arbitrary computation inside of the callback. Concurrency-control, loading, and unloading is done on a

[RFC 0/3] Safe, dynamically (un)loadable LSMs

This patchset introduces safe dynamic LSM support. It does this via SRCU-protected security hooks. It also EXPORT_SYMBOL_GPLs the symbols required to perform runtime loading, and unloading. The patchset is meant to introduce as little overhead as possible when not used. Additionally, the

[RFC 1/3] security: Add safe, dynamic (runtime-loadable) hook support

This patch adds dynamic security hooks. These hooks are designed to allow for safe runtime loading, and unloading. Each dynamic_security_hook is protected by an SRCU, allowing for arbitrary computation inside of the callback. Concurrency-control, loading, and unloading is done on a

Re: [PATCH v2 05/11] dt-bindings: Document the Rockchip ISP1 bindings

On Fri, Nov 24, 2017 at 10:37:00AM +0800, Jacob Chen wrote: > From: Jacob Chen > > Add DT bindings documentation for Rockchip ISP1 > > Signed-off-by: Jacob Chen > --- > .../devicetree/bindings/media/rockchip-isp1.txt| 61 >

Re: [PATCH v2 05/11] dt-bindings: Document the Rockchip ISP1 bindings

On Fri, Nov 24, 2017 at 10:37:00AM +0800, Jacob Chen wrote: > From: Jacob Chen > > Add DT bindings documentation for Rockchip ISP1 > > Signed-off-by: Jacob Chen > --- > .../devicetree/bindings/media/rockchip-isp1.txt| 61 > ++ > 1 file changed, 61 insertions(+) >

Re: [PATCH 1/3] dt-bindings: hwrng: Add Samsung Exynos 5250+ True RNG bindings

On Thu, Nov 23, 2017 at 04:09:12PM +0100, Łukasz Stelmach wrote: > Add binding documentation for the True Random Number Generator > found on Samsung Exynos 5250+ SoCs. > > Signed-off-by: Łukasz Stelmach > --- > .../devicetree/bindings/rng/samsung,exynos5250-trng.txt | 17

Re: [PATCH 1/3] dt-bindings: hwrng: Add Samsung Exynos 5250+ True RNG bindings

On Thu, Nov 23, 2017 at 04:09:12PM +0100, Łukasz Stelmach wrote: > Add binding documentation for the True Random Number Generator > found on Samsung Exynos 5250+ SoCs. > > Signed-off-by: Łukasz Stelmach > --- > .../devicetree/bindings/rng/samsung,exynos5250-trng.txt | 17 > + >

[PATCH] video: matroxfb: Delete an error message for a failed memory allocation in matroxfb_crtc2_probe()

From: Markus Elfring Date: Sun, 26 Nov 2017 22:13:55 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] video: matroxfb: Delete an error message for a failed memory allocation in matroxfb_crtc2_probe()

From: Markus Elfring Date: Sun, 26 Nov 2017 22:13:55 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/video/fbdev/matrox/matroxfb_crtc2.c | 5 ++--- 1 file

Re: regression: 4.13 cannot follow symlinks on some ext3 fs

On Sun, Nov 26, 2017 at 10:40:26AM -0500, Theodore Ts'o wrote: > On Sun, Nov 26, 2017 at 09:32:02AM +1100, Dave Chinner wrote: > > > > They don't have any whacky symlinks around, but the modern ext4 code > > does try to eat these filesystems every so often. Extended operation > > at ENOSPC will

Re: regression: 4.13 cannot follow symlinks on some ext3 fs

On Sun, Nov 26, 2017 at 10:40:26AM -0500, Theodore Ts'o wrote: > On Sun, Nov 26, 2017 at 09:32:02AM +1100, Dave Chinner wrote: > > > > They don't have any whacky symlinks around, but the modern ext4 code > > does try to eat these filesystems every so often. Extended operation > > at ENOSPC will

Re: [PATCH RFC 1/2] sched: Minimize the idle cpu selection race window.

On Fri, 2017-11-24 at 19:46 +0100, Mike Galbraith wrote: > > My view is you're barking up the wrong tree: you're making the idle > data SIS is using more accurate, but I question the benefit.  That it > makes an imperfect placement decision occasionally due to raciness is > nearly meaningless

Re: [PATCH RFC 1/2] sched: Minimize the idle cpu selection race window.

On Fri, 2017-11-24 at 19:46 +0100, Mike Galbraith wrote: > > My view is you're barking up the wrong tree: you're making the idle > data SIS is using more accurate, but I question the benefit.  That it > makes an imperfect placement decision occasionally due to raciness is > nearly meaningless

Re: [PATCH 25/43] x86/mm/kaiser: Unmap kernel from userspace page tables (core patch)

On Fri, Nov 24, 2017 at 06:23:53PM +0100, Ingo Molnar wrote: > diff --git a/arch/x86/entry/calling.h b/arch/x86/entry/calling.h > index e1650da01323..d087c3aa0514 100644 > --- a/arch/x86/entry/calling.h > +++ b/arch/x86/entry/calling.h > @@ -2,6 +2,7 @@ > #include > #include > #include >

Re: [PATCH 25/43] x86/mm/kaiser: Unmap kernel from userspace page tables (core patch)

On Fri, Nov 24, 2017 at 06:23:53PM +0100, Ingo Molnar wrote: > diff --git a/arch/x86/entry/calling.h b/arch/x86/entry/calling.h > index e1650da01323..d087c3aa0514 100644 > --- a/arch/x86/entry/calling.h > +++ b/arch/x86/entry/calling.h > @@ -2,6 +2,7 @@ > #include > #include > #include >

Re: [PATCH] staging: rtl8188eu: Fix private WEXT IOCTL calls

/linux/commits/ishraq-i-ashraf-gmail-com/staging-rtl8188eu-Fix-private-WEXT-IOCTL-calls/20171126-052554 config: x86_64-randconfig-n0-11270329 (attached as .config) compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025 reproduce: # save the attached .config to linux build tree make ARCH

Re: [PATCH] staging: rtl8188eu: Fix private WEXT IOCTL calls

/linux/commits/ishraq-i-ashraf-gmail-com/staging-rtl8188eu-Fix-private-WEXT-IOCTL-calls/20171126-052554 config: x86_64-randconfig-n0-11270329 (attached as .config) compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025 reproduce: # save the attached .config to linux build tree make ARCH

[PATCH 2/2] video: fbdev-MMP: Improve a size determination in path_init()

From: Markus Elfring Date: Sun, 26 Nov 2017 21:21:33 +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 2/2] video: fbdev-MMP: Improve a size determination in path_init()

From: Markus Elfring Date: Sun, 26 Nov 2017 21:21:33 +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

[PATCH 1/2] video: fbdev-MMP: Delete an error message for a failed memory allocation in two functions

From: Markus Elfring Date: Sun, 26 Nov 2017 21:16:30 +0100 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/2] video: fbdev-MMP: Delete an error message for a failed memory allocation in two functions

From: Markus Elfring Date: Sun, 26 Nov 2017 21:16:30 +0100 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/video/fbdev/mmp/fb/mmpfb.c| 5 ++---

[PATCH 0/2] video/fbdev/mmp: Adjustments for two function implementations

From: Markus Elfring Date: Sun, 26 Nov 2017 21:38:42 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation in two functions Improve a size determination

[PATCH 0/2] video/fbdev/mmp: Adjustments for two function implementations

From: Markus Elfring Date: Sun, 26 Nov 2017 21:38:42 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation in two functions Improve a size determination in path_init()

Re: [PATCH] ASoC: fsl_ssi: Override bit clock rate based on slot number

Hi Nicolin, > On Sat, Nov 25, 2017 at 11:29:48PM +0100, Lukasz Majewski wrote: > > > Nicolin, do you know what happened with this patch? I couldn't find > > it in current linux/master. > > > > Has it been applied to any asoc tree for being upstreamed? > > A similar patch with an updated

Re: [PATCH] ASoC: fsl_ssi: Override bit clock rate based on slot number

Hi Nicolin, > On Sat, Nov 25, 2017 at 11:29:48PM +0100, Lukasz Majewski wrote: > > > Nicolin, do you know what happened with this patch? I couldn't find > > it in current linux/master. > > > > Has it been applied to any asoc tree for being upstreamed? > > A similar patch with an updated

Re: [PATCH v8 2/2] ARM: dts: TS-4600: add basic device tree

Hi Sebastien, On Thu, Nov 23, 2017 at 7:04 PM, Sebastien Bourdelin wrote: > + reg_vddio_sd0: regulator-vddio-sd0 { > + compatible = "regulator-fixed"; > + regulator-name = "vddio-sd0"; > +

Re: [PATCH v8 2/2] ARM: dts: TS-4600: add basic device tree

Hi Sebastien, On Thu, Nov 23, 2017 at 7:04 PM, Sebastien Bourdelin wrote: > + reg_vddio_sd0: regulator-vddio-sd0 { > + compatible = "regulator-fixed"; > + regulator-name = "vddio-sd0"; > + regulator-min-microvolt = <330>; > +

Re: [PATCH 4/5] dt-bindings: PCI: cadence: Add DT bindings for Cadence PCIe endpoint controller

On Thu, Nov 23, 2017 at 04:01:49PM +0100, Cyrille Pitchen wrote: > This patch documents the DT bindings for the Cadence PCIe controller > when configured in endpoint mode. > > Signed-off-by: Cyrille Pitchen > --- >

Re: [PATCH 4/5] dt-bindings: PCI: cadence: Add DT bindings for Cadence PCIe endpoint controller

On Thu, Nov 23, 2017 at 04:01:49PM +0100, Cyrille Pitchen wrote: > This patch documents the DT bindings for the Cadence PCIe controller > when configured in endpoint mode. > > Signed-off-by: Cyrille Pitchen > --- > .../devicetree/bindings/pci/cdns,cdns-pcie-ep.txt| 20 >

<    1   2   3   4   5   6   7   >