[PATCH] Documentation/process: Clarify disclosure rules

2019-09-25 Thread Thomas Gleixner
The role of the contact list provided by the disclosing party and how it affects the disclosure process and the ability to include experts into the development process is not really well explained. Neither is it entirely clear when the disclosing party will be informed about the fact that a develo

Re: [PATCH v2] docs: Use make invocation's -j argument for parallelism

2019-09-25 Thread Jani Nikula
On Tue, 24 Sep 2019, Kees Cook wrote: > On Tue, Sep 24, 2019 at 10:12:22AM +0300, Jani Nikula wrote: >> On Mon, 23 Sep 2019, Kees Cook wrote: >> > On Sun, Sep 22, 2019 at 02:03:31PM -0600, Jonathan Corbet wrote: >> >> On Thu, 19 Sep 2019 14:44:37 -0700 >> >> Kees Cook wrote: >> >> >> >> > While

[PATCH 1/2] docs: security: fix section hyperlink

2019-09-25 Thread bhenryj0117
From: Brendan Jackman The reStructuredText syntax is wrong here; not sure how it was intended but we can just use the section header as an implicit hyperlink target, with a single "outward" underscore. Signed-off-by: Brendan Jackman Cc: Jonathan Corbet --- Documentation/security/lsm.rst | 2 +

[PATCH 2/2] docs: security: update base LSM documentation file

2019-09-25 Thread bhenryj0117
From: Brendan Jackman I was bringing myself up to speed on LSMs and discovered that this base doc file is out of date. Unless I'm mistaken the "stacking" functionality is still in significant flux (and also I am of course a newbie here) so I haven't really _added_ any info, mainly this patch remo

[PATCH] docs: hwmon: Include 'inspur-ipsps1.rst' into docs

2019-09-25 Thread Adam Zerella
When generating documentation output Sphinx outputs a warning for not including the page 'inspur-ipsps1.rst' in 'index.rst'. Assuming this documentation is useful it should be included in the index. Signed-off-by: Adam Zerella --- Documentation/hwmon/index.rst | 1 + 1 file changed, 1 insertion

[PATCH] docs: kmemleak: DEBUG_KMEMLEAK_EARLY_LOG_SIZE changed names

2019-09-25 Thread Jeremy Cline
Commit c5665868183f ("mm: kmemleak: use the memory pool for early allocations") renamed CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE to CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE. Update the documentation reference to reflect that. Signed-off-by: Jeremy Cline --- Documentation/dev-tools/kmemleak.rst | 2 +- 1

Re: [PATCH] docs: kmemleak: DEBUG_KMEMLEAK_EARLY_LOG_SIZE changed names

2019-09-25 Thread Catalin Marinas
On Wed, Sep 25, 2019 at 02:31:14PM +, Jeremy Cline wrote: > Commit c5665868183f ("mm: kmemleak: use the memory pool for early > allocations") renamed CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE to > CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE. Update the documentation reference > to reflect that. > > Signed-

Re: [PATCH v3] printf: add support for printing symbolic error codes

2019-09-25 Thread Petr Mladek
First, I am sorry that I replay so late. I was traveling the previous two weeks and was not able to follow the discussion about this patch. I am fine with adding this feature. But I would like to do it a cleaner way, see below. On Tue 2019-09-17 08:59:59, Rasmus Villemoes wrote: > With my embedd

Re: [PATCH] Documentation/process: Clarify disclosure rules

2019-09-25 Thread Dave Hansen
On 9/25/19 1:29 AM, Thomas Gleixner wrote: > The role of the contact list provided by the disclosing party and how it > affects the disclosure process and the ability to include experts into > the development process is not really well explained. > > Neither is it entirely clear when the disclosin

[PATCH] docs: fix memory.low description in cgroup-v2.rst

2019-09-25 Thread Jon Haslam
The current cgroup-v2.rst file contains an incorrect description of when memory is reclaimed from a cgroup that is using the 'memory.low' mechanism. This fix simply corrects the text to reflect the actual implementation. Fixes: 7854207fe954 ("mm/docs: describe memory.low refinements") Signed-off-b

Re: [PATCH] docs: fix memory.low description in cgroup-v2.rst

2019-09-25 Thread Roman Gushchin
On Wed, Sep 25, 2019 at 12:56:04PM -0700, Jon Haslam wrote: > The current cgroup-v2.rst file contains an incorrect description of when > memory is reclaimed from a cgroup that is using the 'memory.low' > mechanism. This fix simply corrects the text to reflect the actual > implementation. > > Fixes

Re: [PATCH 2/2] docs: security: update base LSM documentation file

2019-09-25 Thread Kees Cook
On Wed, Sep 25, 2019 at 05:17:45PM +0700, bhenryj0...@gmail.com wrote: > From: Brendan Jackman > > I was bringing myself up to speed on LSMs and discovered that this > base doc file is out of date. Unless I'm mistaken the "stacking" > functionality is still in significant flux (and also I am of c

[RFC PATCH] x86/doc/boot_protocol: Correct the description of "reloc"

2019-09-25 Thread Cao jin
The fields marked with (reloc) actually are not dedicated for writing, but communicating info for relocatable kernel with boot loaders. For example: Field name: pref_address Type: read (reloc) Offset/size:0x258/8 Protocol: 2.

Re: [RFC PATCH] x86/doc/boot_protocol: Correct the description of "reloc"

2019-09-25 Thread Ingo Molnar
* Cao jin wrote: > The fields marked with (reloc) actually are not dedicated for writing, > but communicating info for relocatable kernel with boot loaders. For > example: > > > Field name: pref_address > Type: read (reloc) > Offset/size

Re: [RFC PATCH] x86/doc/boot_protocol: Correct the description of "reloc"

2019-09-25 Thread hpa
On September 25, 2019 11:01:39 PM PDT, Ingo Molnar wrote: >* Cao jin wrote: > >> The fields marked with (reloc) actually are not dedicated for >writing, >> but communicating info for relocatable kernel with boot loaders. For >> example: >> >> >> Field name: