Re: [kernel-hardening] Re: [PATCH 0/2] sysctl: allow CLONE_NEWUSER to be disabled

2016-01-25 Thread Serge Hallyn
Quoting Kees Cook (keesc...@chromium.org): > On Fri, Jan 22, 2016 at 7:02 PM, Eric W. Biederman > > So I have concerns about both efficacy and usability with the proposed > > sysctl. > > Two distros already have this sysctl because it was so strongly > requested by their users. This needs to be up

Re: [PATCH 0/2] sysctl: allow CLONE_NEWUSER to be disabled

2016-01-25 Thread Eric W. Biederman
Kees Cook writes: > On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman > wrote: >> Kees Cook writes: >>> >>> Well, I don't know about less weird, but it would leave a unneeded >>> hole in the permission checks. >> >> To be clear the current patch has my: >> >> Nacked-by: "Eric W. Biederman" >

[RFT PATCH v7 7/9] watchdog: retu: Convert to use infrastructure triggered keepalives

2016-01-25 Thread Guenter Roeck
From: Guenter Roeck The watchdog infrastructure now supports handling watchdog keepalive if the watchdog is running while the watchdog device is closed. Convert the driver to use this infrastructure. Signed-off-by: Guenter Roeck --- v7: Set max_hw_timeout_ms Rebased to v4.5-rc1 v6: Rename W

[RFT PATCH v7 8/9] watchdog: at91sam9: Convert to use infrastructure triggered keepalives

2016-01-25 Thread Guenter Roeck
From: Guenter Roeck The watchdog infrastructure now supports handling watchdog keepalive if the watchdog is running while the watchdog device is closed. The infrastructure now also supports generating additional heartbeats if the maximum hardware timeout is smaller than or close to the configured

[RFT PATCH v7 6/9] watchdog: imx2: Convert to use infrastructure triggered keepalives

2016-01-25 Thread Guenter Roeck
From: Guenter Roeck The watchdog infrastructure now supports handling watchdog keepalive if the watchdog is running while the watchdog device is closed. Convert the driver to use this infrastructure. Signed-off-by: Guenter Roeck --- v7: Set max_hw_timeout_ms Rebased to v4.5-rc1 v6: Rename W

[PATCH v7 2/9] watchdog: Introduce WDOG_HW_RUNNING flag

2016-01-25 Thread Guenter Roeck
From: Guenter Roeck The WDOG_HW_RUNNING flag is expected to be set by watchdog drivers if the hardware watchdog is running. If the flag is set, the watchdog subsystem will ping the watchdog even if the watchdog device is closed. The watchdog driver stop function is now optional and may be omitte

[RFT PATCH v7 9/9] watchdog: dw_wdt: Convert to use watchdog infrastructure

2016-01-25 Thread Guenter Roeck
From: Guenter Roeck Convert driver to use watchdog infrastructure. This includes infrastructure support to handle watchdog keepalive if the watchdog is running while the watchdog device is closed. Signed-off-by: Guenter Roeck --- v7: Set max_hw_timeout_ms Rebased to v4.5-rc1 v6: Added patc

[PATCH v7 3/9] watchdog: Make set_timeout function optional

2016-01-25 Thread Guenter Roeck
From: Guenter Roeck For some watchdogs, the hardware timeout is fixed, and the watchdog driver depends on the watchdog core to handle the actual timeout. In this situation, the watchdog driver might only set the 'timeout' variable but do nothing else. This can as well be handled by the infrastruc

[PATCH v7 5/9] watchdog: Simplify update_worker

2016-01-25 Thread Guenter Roeck
From: Guenter Roeck Drop 'cancel' parameter; simply cancel worker unconditionally if not needed. Signed-off-by: Guenter Roeck --- v7: Rebased to v4.5-rc1 v6: Rebased to v4.4-rc2 v5: Introduced patch --- drivers/watchdog/watchdog_dev.c | 15 +++ 1 file changed, 7 insertions(+), 8 d

[PATCH v7 1/9] watchdog: Introduce hardware maximum timeout in watchdog core

2016-01-25 Thread Guenter Roeck
From: Guenter Roeck Introduce an optional hardware maximum timeout in the watchdog core. The hardware maximum timeout can be lower than the maximum timeout. Drivers can set the maximum hardware timeout value in the watchdog data structure. If the configured timeout exceeds the maximum hardware t

[PATCH v7 4/9] watchdog: Add support for minimum time between heartbeats

2016-01-25 Thread Guenter Roeck
From: Guenter Roeck Some watchdogs require a minimum time between heartbeats. Examples are the watchdogs in DA9062 and AT91SAM9x. Signed-off-by: Guenter Roeck --- v7: Rebased to v4.5-rc1 v6: Rebased to v4.4-rc2 v5: Rebased to v4.4-rc1 Fixed typo in documentation. v4: Added patch --- Docum

[PATCH v7 0/9] watchdog: Add support for keepalives triggered by infrastructure

2016-01-25 Thread Guenter Roeck
From: Guenter Roeck The watchdog infrastructure is currently purely passive, meaning it only passes information from user space to drivers and vice versa. Since watchdog hardware tends to have its own quirks, this can result in quite complex watchdog drivers. A number of scanarios are especially

Re: [kernel-hardening] Re: [PATCH 0/2] sysctl: allow CLONE_NEWUSER to be disabled

2016-01-25 Thread Daniel Micay
> This feature is already implemented by two distros, and likely wanted > by others. We cannot ignore that. Date point: Arch Linux won't be enabling CONFIG_USERNS until there's a way to disable unprivileged user namespaces. The kernel maintainers are unwilling to carry long-term out-of-tree patche

Re: [PATCH] kernel-doc: add support for asciidoc output

2016-01-25 Thread Jonathan Corbet
On Mon, 18 Jan 2016 10:41:17 +0200 Jani Nikula wrote: > Add new -asciidoc option to produce asciidoc output from kernel-doc. The > output is formatted internally, with no dependencies on external > tools. Any asciidoc formatting present in kernel-doc will naturally be > present in the resulting a

Re: [PATCH 0/2] sysctl: allow CLONE_NEWUSER to be disabled

2016-01-25 Thread Andy Lutomirski
On Mon, Jan 25, 2016 at 2:34 PM, Kees Cook wrote: > On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman > wrote: >> Kees Cook writes: >>> >>> Well, I don't know about less weird, but it would leave a unneeded >>> hole in the permission checks. >> >> To be clear the current patch has my: >> >> Na

[PATCH 4/4] Docs: add a sample asciidoc template

2016-01-25 Thread Jonathan Corbet
This is just a copy of tracepoints.tmpl (because it was short!) converted into asciidoc. Signed-off-by: Jonathan Corbet --- Documentation/DocBook/Makefile | 2 +- Documentation/DocBook/tpoint.adt | 64 2 files changed, 65 insertions(+), 1 deletion(-)

[PATCH 2/4] docproc: handle asciidoc templates

2016-01-25 Thread Jonathan Corbet
There's really nothing different that needs to be done except for invoking kernel-doc with the -asciidoc argument. Look at the input file name to recognize asciidoc templates, so no special command-line flags are needed. Signed-off-by: Jonathan Corbet --- scripts/docproc.c | 25

[RFC] A first shot at asciidoc-based formatted docs

2016-01-25 Thread Jonathan Corbet
So here is a proof-of-concept series showing how a fully asciidoc-based toolchain might work. Lots of hackery here, this isn't meant to be applied to anything at this point, but it's a good start. What this series has is: - Jani Nikula's patch adding asciidoc output to kernel-doc. Thanks for

[PATCH 1/4] kernel-doc: add support for asciidoc output

2016-01-25 Thread Jonathan Corbet
From: Jani Nikula Add new -asciidoc option to produce asciidoc output from kernel-doc. The output is formatted internally, with no dependencies on external tools. Any asciidoc formatting present in kernel-doc will naturally be present in the resulting asciidoc as well. Highlighting of functions(

[PATCH 3/4] Docs: Makefile tweaks for asciidoc templates

2016-01-25 Thread Jonathan Corbet
This is a hatchet job, but it's something to start with. Generalize some of the string manipulation to not assume that templates have a ".tmpl" suffix, and add rules to translate asciidoc templates to HTML. Nothing for any other output formats at this point. Signed-off-by: Jonathan Corbet ---

Re: [PATCH 0/2] sysctl: allow CLONE_NEWUSER to be disabled

2016-01-25 Thread Kees Cook
On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman wrote: > Kees Cook writes: >> >> Well, I don't know about less weird, but it would leave a unneeded >> hole in the permission checks. > > To be clear the current patch has my: > > Nacked-by: "Eric W. Biederman" > > The code is buggy, and poorly

Re: [RFC PATCH] codingstyle: improve elisp for a better experience

2016-01-25 Thread Geyslan G. Bem
2016-01-25 17:01 GMT-03:00 Jonathan Corbet : > On Thu, 21 Jan 2016 22:18:30 -0300 > "Geyslan G. Bem" wrote: > >> This patch does use of more emacs functionalities which deliver to the >> user indentation, commenting and white space highlighting. > > So perhaps it's just me, but that's an awful lot

Re: [PATCH V8 20/23] perf tools: making function set_max_cpu_num() non static

2016-01-25 Thread Arnaldo Carvalho de Melo
Em Mon, Jan 25, 2016 at 06:12:42PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Mon, Jan 25, 2016 at 01:46:22PM -0700, Mathieu Poirier escreveu: > > On 14 January 2016 at 14:46, Mathieu Poirier > > wrote: > > > For memory allocation purposes, code located in other places > > > then util/cpumap.

Re: [PATCH V8 20/23] perf tools: making function set_max_cpu_num() non static

2016-01-25 Thread Arnaldo Carvalho de Melo
Em Mon, Jan 25, 2016 at 01:46:22PM -0700, Mathieu Poirier escreveu: > On 14 January 2016 at 14:46, Mathieu Poirier > wrote: > > For memory allocation purposes, code located in other places > > then util/cpumap.c may want to know how many CPUs the system has. > > > > This patch is making function

Re: [PATCH V8 20/23] perf tools: making function set_max_cpu_num() non static

2016-01-25 Thread Mathieu Poirier
On 14 January 2016 at 14:46, Mathieu Poirier wrote: > For memory allocation purposes, code located in other places > then util/cpumap.c may want to know how many CPUs the system has. > > This patch is making function set_max_cpu_num() available to > other parts of the perf tool so that global vari

Re: [RFC PATCH] codingstyle: improve elisp for a better experience

2016-01-25 Thread Jonathan Corbet
On Thu, 21 Jan 2016 22:18:30 -0300 "Geyslan G. Bem" wrote: > This patch does use of more emacs functionalities which deliver to the > user indentation, commenting and white space highlighting. So perhaps it's just me, but that's an awful lot of elisp code for readers to wade through; many of tho

Re: [PATCH 0/2] sysctl: allow CLONE_NEWUSER to be disabled

2016-01-25 Thread Eric W. Biederman
Kees Cook writes: > > Well, I don't know about less weird, but it would leave a unneeded > hole in the permission checks. To be clear the current patch has my: Nacked-by: "Eric W. Biederman" The code is buggy, and poorly thought through. Your lack of interest in fixing the bugs in your patch

Re: [PATCH] SubmittingPatches: fix spelling of "git send-email"

2016-01-25 Thread Jonathan Corbet
On Tue, 15 Dec 2015 12:00:27 +0100 Jakub Wilk wrote: > -(e.g., when using "git send email") to associate the patch with > +(e.g., when using "git send-email") to associate the patch with Applied (finally) to the docs tree, thanks. jon -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH 0/2] sysctl: allow CLONE_NEWUSER to be disabled

2016-01-25 Thread Kees Cook
On Mon, Jan 25, 2016 at 10:53 AM, Andy Lutomirski wrote: > On Mon, Jan 25, 2016 at 10:51 AM, Kees Cook wrote: >> On Sun, Jan 24, 2016 at 2:22 PM, Andy Lutomirski wrote: >>> On Fri, Jan 22, 2016 at 7:02 PM, Eric W. Biederman >>> wrote: Kees Cook writes: > There continues to be une

Re: [PATCH 0/2] sysctl: allow CLONE_NEWUSER to be disabled

2016-01-25 Thread Andy Lutomirski
On Mon, Jan 25, 2016 at 10:51 AM, Kees Cook wrote: > On Sun, Jan 24, 2016 at 2:22 PM, Andy Lutomirski wrote: >> On Fri, Jan 22, 2016 at 7:02 PM, Eric W. Biederman >> wrote: >>> Kees Cook writes: >>> There continues to be unexpected side-effects and security exposures via CLONE_NEWUSER

Re: [kernel-hardening] Re: [PATCH 2/2] sysctl: allow CLONE_NEWUSER to be disabled

2016-01-25 Thread Kees Cook
On Sun, Jan 24, 2016 at 2:20 PM, Andy Lutomirski wrote: > On Sun, Jan 24, 2016 at 12:59 PM, Kees Cook wrote: >> On Fri, Jan 22, 2016 at 4:59 PM, Ben Hutchings wrote: >>> On Fri, 2016-01-22 at 15:00 -0800, Kees Cook wrote: On Fri, Jan 22, 2016 at 2:55 PM, Robert Święcki wrote: > 2016-0

Re: [PATCH 0/2] sysctl: allow CLONE_NEWUSER to be disabled

2016-01-25 Thread Kees Cook
On Sun, Jan 24, 2016 at 2:22 PM, Andy Lutomirski wrote: > On Fri, Jan 22, 2016 at 7:02 PM, Eric W. Biederman > wrote: >> Kees Cook writes: >> >>> There continues to be unexpected side-effects and security exposures >>> via CLONE_NEWUSER. For many end-users running distro kernels with >>> CONFIG_

Re: [PATCH v15 1/6] fpga: add bindings document for fpga area and fpga bus

2016-01-25 Thread Rob Herring
On Wed, Jan 20, 2016 at 01:24:22PM -0600, at...@opensource.altera.com wrote: > From: Alan Tull > > New bindings document for FPGA Area for reprogramming > FPGA's under Device Tree control > > Signed-off-by: Alan Tull > --- > v9: initial version added to this patchset > v10: s/fpga/FPGA/g >

Re: [PATCH v15 5/6] fpga: fpga-area and fpga-bus: device tree control for FPGA

2016-01-25 Thread Rob Herring
On Fri, Jan 22, 2016 at 6:07 PM, Moritz Fischer wrote: > On Fri, Jan 22, 2016 at 5:37 PM, atull wrote: >> On Fri, 22 Jan 2016, Moritz Fischer wrote: >> >>> Alan, >>> >>> On Wed, Jan 20, 2016 at 8:24 PM, wrote: >>> >>> > +static int fpga_area_probe(struct platform_device *pdev) >>> > +{ >>> > +

Re: [PATCHv8 2/4] ARM: dts: Add Altera L2 Cache and OCRAM EDAC entries

2016-01-25 Thread Thor Thayer
On 01/22/2016 08:35 PM, Rob Herring wrote: On Thu, Jan 21, 2016 at 11:34:26AM -0600, ttha...@opensource.altera.com wrote: From: Thor Thayer Adding the device tree entries and bindings needed to support the Altera L2 cache and On-Chip RAM EDAC. This patch relies upon an earlier patch to decla