Re: [PATCH v4 0/9] docs: Convert VFS doc to RST

On Wed, May 29, 2019 at 04:30:52PM -0600, Jonathan Corbet wrote: > On Wed, 15 May 2019 10:29:04 +1000 > "Tobin C. Harding" wrote: > > > Here is an updated version of the VFS doc conversion. This series in no > > way represents a final point for the VFS documentation rather it is a > > small step

[lwn:docs-next 19/19] htmldocs: include/linux/generic-radix-tree.h:1: warning: 'Generic radix trees/sparse arrays' not found

tree: git://git.lwn.net/linux-2.6 docs-next head: b0d60bfbb60cef1efd699a65e29a94487f8c7b1f commit: b0d60bfbb60cef1efd699a65e29a94487f8c7b1f [19/19] kernel-doc: always name missing kerneldoc sections reproduce: make htmldocs If you fix the issue, kindly add following tag Reported-by: kbuild te

Re: [PATCH v6 00/12] Include linux PCI docs into Sphinx TOC tree

On Wed, May 29, 2019 at 04:35:10PM -0600, Jonathan Corbet wrote: > On Mon, 20 May 2019 06:10:15 + > Changbin Du wrote: > > > Bjorn and Jonathan, > > Could we consider to merge this serias now? Thanks. > > Somewhat belatedly, but I think we could. Bjorn, do you have a preference > for which

Re: [PATCH v6 00/12] Include linux PCI docs into Sphinx TOC tree

On Wed, May 29, 2019 at 04:35:10PM -0600, Jonathan Corbet wrote: > On Mon, 20 May 2019 06:10:15 + > Changbin Du wrote: > > > Bjorn and Jonathan, > > Could we consider to merge this serias now? Thanks. > > Somewhat belatedly, but I think we could. Bjorn, do you have a preference > for which

Re: [PATCH 4/5] docs: by default, build docs a lot faster with Sphinx >= 1.7

Em Wed, 29 May 2019 17:47:16 -0600 Jonathan Corbet escreveu: > On Wed, 29 May 2019 20:20:05 -0300 > Mauro Carvalho Chehab wrote: > > > > So this totally fails to work for me with any version of sphinx, and I'm > > > not enough of a Perl person to figure it out. Sometimes I'll see the > > > sph

Re: [PATCH 2/2] Docs: hwmon: pmbus: Add PXE1610 driver

On 5/29/19 3:35 PM, Vijay Khemka wrote: Added support for Infenion PXE1610 driver Signed-off-by: Vijay Khemka --- Documentation/hwmon/pxe1610 | 84 + 1 file changed, 84 insertions(+) create mode 100644 Documentation/hwmon/pxe1610 diff --git a/Documentat

Re: [PATCH 1/2] hwmon: pmbus: Add Infineon PXE1610 VR driver

On 5/29/19 3:35 PM, Vijay Khemka wrote: Added pmbus driver for the new device Infineon pxe1610 voltage regulator. It also supports similar family device PXE1110 and PXM1310. Signed-off-by: Vijay Khemka --- drivers/hwmon/pmbus/Kconfig | 9 +++ drivers/hwmon/pmbus/Makefile | 1 + drive

[PATCH v3 0/4] F2FS Checkpointing without GC, related fixes

The first patch adjusts the default allowable holes for checkpointing, and the next two patches fix underflow issues related to inc_valid_block_count and inc_valid_node_count. The final one adds a new feature for checkpointing where the user can specify an acceptable amount of space to lose access

[PATCH v3 1/4] f2fs: Lower threshold for disable_cp_again

The existing threshold for allowable holes at checkpoint=disable time is too high. The OVP space contains reserved segments, which are always in the form of free segments. These must be subtracted from the OVP value. The current threshold is meant to be the maximum value of holes of a single type

[PATCH v3 3/4] f2fs: Fix accounting for unusable blocks

Fixes possible underflows when dealing with unusable blocks. Signed-off-by: Daniel Rosenberg --- fs/f2fs/f2fs.h | 15 ++- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 9b3d9977cd1ef..a39cc4ffeb4b1 100644 --- a/fs/f2fs/f2fs.h +++

[PATCH v3 4/4] f2fs: Add option to limit required GC for checkpoint=disable

This extends the checkpoint option to allow checkpoint=disable:%u[%] This allows you to specify what how much of the disk you are willing to lose access to while mounting with checkpoint=disable. If the amount lost would be higher, the mount will return -EAGAIN. This can be given as a percent of to

[PATCH v3 2/4] f2fs: Fix root reserved on remount

On a remount, you can currently set root reserved if it was not previously set. This can cause an underflow if reserved has been set to a very high value, since then root reserved + current reserved could be greater than user_block_count. inc_valid_block_count later subtracts out these values from

Re: [PATCH 4/5] docs: by default, build docs a lot faster with Sphinx >= 1.7

On Wed, 29 May 2019 20:20:05 -0300 Mauro Carvalho Chehab wrote: > > So this totally fails to work for me with any version of sphinx, and I'm > > not enough of a Perl person to figure it out. Sometimes I'll see the > > sphinx-build output, i.e.: > > > > sphinx-build 1.8.4 > > > > and someti

Re: [PATCH 21/22] docs: net: sja1105.rst: fix table format

On Thu, 30 May 2019 at 02:24, Mauro Carvalho Chehab wrote: > > There's a table there with produces two warnings when built > with Sphinx: > > Documentation/networking/dsa/sja1105.rst:91: WARNING: Block quote ends > without a blank line; unexpected unindent. > Documentation/networking/dsa/

[PATCH 19/22] docs: security: core.rst: Fix several warnings

Multi-line literal markups only work when they're idented at the same level, with is not the case here: Documentation/security/keys/core.rst:1597: WARNING: Inline literal start-string without end-string. Documentation/security/keys/core.rst:1597: WARNING: Inline emphasis start-string witho

[PATCH 18/22] docs: security: trusted-encrypted.rst: fix code-block tag

The code-block tag is at the wrong place, causing those warnings: Documentation/security/keys/trusted-encrypted.rst:112: WARNING: Literal block expected; none found. Documentation/security/keys/trusted-encrypted.rst:121: WARNING: Unexpected indentation. Documentation/security/keys/tr

[PATCH 01/22] ABI: sysfs-devices-system-cpu: point to the right docs

The cpuidle doc was split on two, one at the admin guide and another one at the driver API guide. Instead of pointing to a non-existent file, point to both (admin guide being the first one). Signed-off-by: Mauro Carvalho Chehab --- Documentation/ABI/testing/sysfs-devices-system-cpu | 3 ++- 1 fi

[PATCH 10/22] docs: amd-memory-encryption.rst get rid of warnings

Get rid of those warnings: Documentation/virtual/kvm/amd-memory-encryption.rst:244: WARNING: Citation [white-paper] is not referenced. Documentation/virtual/kvm/amd-memory-encryption.rst:246: WARNING: Citation [amd-apm] is not referenced. Documentation/virtual/kvm/amd-memory-encrypti

[PATCH 04/22] docs: zh_CN: get rid of basic_profiling.txt

Changeset 5700d1974818 ("docs: Get rid of the "basic profiling" guide") removed an old basic-profiling.txt file that was not updated over the last 11 years and won't reflect the post-perf era. It makes no sense to keep its translation, so get rid of it too. Fixes: 5700d1974818 ("docs: Get rid of

[PATCH 11/22] gpu: amdgpu: fix broken amdgpu_dma_buf.c references

This file was renamed, but docs weren't updated accordingly. WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function PRIME Buffer Sharing ./drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c' failed with return code 1 WARNING: kernel-doc './scripts/kernel-doc -rst -enable-

[PATCH 08/22] docs: bpf: get rid of two warnings

Documentation/bpf/btf.rst:154: WARNING: Unexpected indentation. Documentation/bpf/btf.rst:163: WARNING: Unexpected indentation. Signed-off-by: Mauro Carvalho Chehab --- Documentation/bpf/btf.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/bpf/btf.rst b/Documentation/bpf/b

[PATCH 20/22] docs: net: dpio-driver.rst: fix two codeblock warnings

Documentation/networking/device_drivers/freescale/dpaa2/dpio-driver.rst:43: WARNING: Definition list ends without a blank line; unexpected unindent. Documentation/networking/device_drivers/freescale/dpaa2/dpio-driver.rst:63: WARNING: Unexpected indentation. looking for now-outdated files.

[PATCH 07/22] docs: mm: numaperf.rst: get rid of a build warning

When building it, it gets this warning: Documentation/admin-guide/mm/numaperf.rst:168: WARNING: Footnote [1] is not referenced. The problem is that this is not really a reference, as it is not mentioned within the documentation. Signed-off-by: Mauro Carvalho Chehab --- Documentation/a

[PATCH 02/22] isdn: mISDN: remove a bogus reference to a non-existing doc

The mISDN driver was added on those commits: 960366cf8dbb ("Add mISDN DSP") 1b2b03f8e514 ("Add mISDN core files") 04578dd330f1 ("Define AF_ISDN and PF_ISDN") e4ac9bc1f668 ("Add mISDN driver") None of them added a Documentation/isdn/mISDN.cert file. Also, whatever w

[PATCH 13/22] docs: zh_CN: avoid duplicate citation references

Documentation/process/management-style.rst:35: WARNING: duplicate label decisions, other instance in Documentation/translations/zh_CN/process/management-style.rst Documentation/process/programming-language.rst:37: WARNING: duplicate citation c-language, other instance in Documen

[PATCH 17/22] docs: soundwire: locking: fix tags for a code-block

There's an ascii artwork at Example 1 whose code-block is not properly idented, causing those warnings. Documentation/driver-api/soundwire/locking.rst:50: WARNING: Inconsistent literal block quoting. Documentation/driver-api/soundwire/locking.rst:51: WARNING: Line block ends without a bl

[PATCH 14/22] docs: vm: hmm.rst: fix some warnings

Documentation/vm/hmm.rst:292: WARNING: Unexpected indentation. Documentation/vm/hmm.rst:300: WARNING: Unexpected indentation. Signed-off-by: Mauro Carvalho Chehab --- Documentation/vm/hmm.rst | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/Documentation/vm/hm

[PATCH 16/22] docs: gpio: driver.rst: fix a bad tag

With ReST, [foo]_ means a reference to foo, causing this warning: Documentation/driver-api/gpio/driver.rst:419: WARNING: Unknown target name: "devm". Fix it by using a literal for the name. Signed-off-by: Mauro Carvalho Chehab --- Documentation/driver-api/gpio/driver.rst | 2 +- 1 file ch

[PATCH 03/22] dt: fix broken references to nand.txt

The Documentation/devicetree/bindings/mtd/nand.txt were both renamed and converted to YAML on a single patch, without updating references to it. That caused several cross-references to break. Fixes: 212e49693592 ("dt-bindings: mtd: Add YAML schemas for the generic NAND options") Signed-off-by: M

[PATCH 06/22] doc: it_IT: fix reference to magic-number.rst

There's a typo at the referred file. Signed-off-by: Mauro Carvalho Chehab --- Documentation/translations/it_IT/process/magic-number.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/translations/it_IT/process/magic-number.rst b/Documentation/translations/it_I

[PATCH 05/22] mfd: madera: Fix bad reference to pinctrl.txt file

From: Otto Sabart The pinctrl.txt file was converted into reStructuredText and moved into driver-api folder. This patch updates the broken reference. Fixes: 5a9b73832e9e ("pinctrl.txt: move it to the driver-api book") Signed-off-by: Otto Sabart Signed-off-by: Charles Keepax Signed-off-by: Maur

[PATCH 21/22] docs: net: sja1105.rst: fix table format

There's a table there with produces two warnings when built with Sphinx: Documentation/networking/dsa/sja1105.rst:91: WARNING: Block quote ends without a blank line; unexpected unindent. Documentation/networking/dsa/sja1105.rst:91: WARNING: Block quote ends without a blank line; unexpect

[PATCH 15/22] docs: it: license-rules.rst: get rid of warnings

There's a wrong identation on a code block, and it tries to use a reference that was not defined at the Italian translation. Documentation/translations/it_IT/process/license-rules.rst:329: WARNING: Literal block expected; none found. Documentation/translations/it_IT/process/license-rules.

Re: [PATCH 4/5] docs: by default, build docs a lot faster with Sphinx >= 1.7

Em Wed, 29 May 2019 17:02:02 -0600 Jonathan Corbet escreveu: > On Mon, 27 May 2019 08:07:40 -0300 > Mauro Carvalho Chehab wrote: > > > Since Sphinx version 1.7, it is possible to use "-jauto" in > > order to speedup documentation builds. On older versions, > > while -j was already supported, on

[PATCH 10/10] docs: requirements.txt: recommend Sphinx 1.7.9

As discussed at the linux-doc ML, while we'll still support version 1.3, it is time to recommend a more modern version. So, let's switch the minimal requirements to Sphinx 1.7.9, as it has the "-jauto" flag, with makes a lot faster when building documentation. Signed-off-by: Mauro Carvalho Chehab

[PATCH 03/10] scripts/sphinx-pre-install: get rid of RHEL7 explicity check

RHEL8 was already launched. This test won't get it, and will do the wrong thing. Ok, we could fix it, but now we check Sphinx version to ensure that it matches the minimal (1.3), so there's no need for an explicit check there. Signed-off-by: Mauro Carvalho Chehab --- scripts/sphinx-pre-install |

[PATCH 07/10] scripts/documentation-file-ref-check: improve tools ref handling

There's a false positive on perf/util: tools/perf/util/s390-cpumsf.c: Documentation/perf.data-file-format.txt The file is there at tools/perf/Documentation/, but the logic with detects relative documentation references inside tools is not capable of detecting it. So, improve it. Signed-

[PATCH 08/10] scripts/documentation-file-ref-check: teach about .txt -> .yaml renames

At DT, files are being renamed to jason. Teach the script how to handle such renames when used in fix mode. Signed-off-by: Mauro Carvalho Chehab --- scripts/documentation-file-ref-check | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/scripts/documentation

[PATCH 00/10] Improvements to the documentation build system

Hi Jon, This series contain some improvements for the building system. I sent already several of the patches here. They're rebased on the top of your docs-next tree: patch 1: gets rid of a warning since version 1.8 (I guess it starts appearing with 1.8.6); patches 2 to 4: improve the pre-instal

[PATCH 01/10] docs: cdomain.py: get rid of a warning since version 1.8

There's a new warning about a deprecation function. Add a logic at cdomain.py to avoid that. Signed-off-by: Mauro Carvalho Chehab --- Documentation/sphinx/cdomain.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Documentation/sphinx/cdomain.py b/Documentation/sphinx/cdo

[PATCH 02/10] scripts/sphinx-pre-install: make activate hint smarter

It is possible that multiple Sphinx virtualenvs are installed on a given kernel tree. Change the logic to get the latest version of those, as this is probably what the user wants. Signed-off-by: Mauro Carvalho Chehab --- scripts/sphinx-pre-install | 22 ++ 1 file changed, 14

[PATCH 09/10] docs: by default, build docs a lot faster with Sphinx >= 1.7

Since Sphinx version 1.7, it is possible to use "-jauto" in order to speedup documentation builds. On older versions, while -j was already supported, one would need to set the number of threads manually. So, if SPHINXOPTS is not provided, add -jauto, in order to speed up the build. That makes it *

[PATCH 06/10] scripts/documentation-file-ref-check: exclude false-positives

There are at least two cases where a documentation file was gone for good, but the text still mentions it: 1) drivers/vhost/vhost.c: the reference for Documentation/virtual/lguest/lguest.c is just to give credits to the original work that vhost replaced; 2) Documentation/scsi/scsi_mid_low_a

[PATCH 05/10] scripts/documentation-file-ref-check: better handle translations

Only seek for translation renames inside the translation directory. Signed-off-by: Mauro Carvalho Chehab --- scripts/documentation-file-ref-check | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/scripts/documentation-file-ref-check b/scripts/documentation-file-ref-

[PATCH 04/10] scripts/sphinx-pre-install: always check if version is compatible with build

Call the script every time a make docs target is selected, on a simplified check mode. With this change, the script will set two vars: $min_version - obtained from `needs_sphinx` var inside conf.py (currently, '1.3') $rec_version - obtained from sphinx/requirements.txt. With thos

Re: [PATCH] Allow to exclude specific file types in LoadPin

On Wed, May 29, 2019 at 03:43:50PM -0700, Ke Wu wrote: > Linux kernel already provide MODULE_SIG and KEXEC_VERIFY_SIG to > make sure loaded kernel module and kernel image are trusted. This > patch adds a kernel command line option "loadpin.exclude" which > allows to exclude specific file types from

Re: [PATCH 4/5] docs: by default, build docs a lot faster with Sphinx >= 1.7

On Mon, 27 May 2019 08:07:40 -0300 Mauro Carvalho Chehab wrote: > Since Sphinx version 1.7, it is possible to use "-jauto" in > order to speedup documentation builds. On older versions, > while -j was already supported, one would need to set the > number of threads manually. > > So, if SPHINXOPT

[PATCH] Allow to exclude specific file types in LoadPin

Linux kernel already provide MODULE_SIG and KEXEC_VERIFY_SIG to make sure loaded kernel module and kernel image are trusted. This patch adds a kernel command line option "loadpin.exclude" which allows to exclude specific file types from LoadPin. This is useful when people want to use different mech

Re: [PATCH] scripts/sphinx-pre-install: make activate hint smarter

On Thu, 23 May 2019 08:14:02 -0300 Mauro Carvalho Chehab wrote: > It is possible that multiple Sphinx virtualenvs are installed > on a given kernel tree. Change the logic to get the latest > version of those, as this is probably what the user wants. > > Signed-off-by: Mauro Carvalho Chehab App

[PATCH 1/2] hwmon: pmbus: Add Infineon PXE1610 VR driver

Added pmbus driver for the new device Infineon pxe1610 voltage regulator. It also supports similar family device PXE1110 and PXM1310. Signed-off-by: Vijay Khemka --- drivers/hwmon/pmbus/Kconfig | 9 +++ drivers/hwmon/pmbus/Makefile | 1 + drivers/hwmon/pmbus/pxe1610.c | 119 ++

[PATCH 2/2] Docs: hwmon: pmbus: Add PXE1610 driver

Added support for Infenion PXE1610 driver Signed-off-by: Vijay Khemka --- Documentation/hwmon/pxe1610 | 84 + 1 file changed, 84 insertions(+) create mode 100644 Documentation/hwmon/pxe1610 diff --git a/Documentation/hwmon/pxe1610 b/Documentation/hwmon/pxe16

Re: [PATCH v6 00/12] Include linux PCI docs into Sphinx TOC tree

On Mon, 20 May 2019 06:10:15 + Changbin Du wrote: > Bjorn and Jonathan, > Could we consider to merge this serias now? Thanks. Somewhat belatedly, but I think we could. Bjorn, do you have a preference for which tree this goes through? I don't remember if we'd come to an agreement on that or

Re: [PATCH v4 0/9] docs: Convert VFS doc to RST

On Wed, 15 May 2019 10:29:04 +1000 "Tobin C. Harding" wrote: > Here is an updated version of the VFS doc conversion. This series in no > way represents a final point for the VFS documentation rather it is a > small step towards getting VFS docs updated. This series does not > update the content

[PATCH] docs cgroups: add another example size for hugetlb

Add another example to clarify that HugePages smaller than 1MB will be displayed using "KB", with an uppercased K (eg. 20KB), and not the normal SI prefix kilo (small k). Because of a misunderstanding/copy-paste error inside runc (see https://github.com/opencontainers/runc/pull/2065), it tried acc

Re: [PATCH] [linux-next] docs: tracing: Fix typos in histogram.rst

On Tue, 21 May 2019 08:55:25 -0400 Steven Rostedt wrote: > On Tue, 21 May 2019 21:30:00 +0900 > Masanari Iida wrote: > > > This patch fixes some spelling typos in histogram.rst > > Acked-by: Steven Rostedt (VMware) > > Jon, > > Care to take this in your tree? Done, thanks. jon

Re: [PATCH] docs: cdomain.py: get rid of a warning since version 1.8

On Thu, 23 May 2019 07:43:43 -0300 Mauro Carvalho Chehab wrote: > There's a new warning about a deprecation function. Add a > logic at cdomain.py to avoid that. > > Signed-off-by: Mauro Carvalho Chehab Applied, thanks. jon

Re: [GIT PULL] Fixes for sphinx 2.0 docs build failures

The pull request you sent on Wed, 29 May 2019 09:54:08 -0600: > git://git.lwn.net/linux.git tags/docs-5.2-fixes2 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/bec7550cca106c3ccc061e3e625516af63054fe4 Thank you! -- Deet-doot-dot, I am a bot. https://korg.wiki.kernel

Re: [PATCH v3 1/1] sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices

Dave Chiluk writes: > It has been observed, that highly-threaded, non-cpu-bound applications > running under cpu.cfs_quota_us constraints can hit a high percentage of > periods throttled while simultaneously not consuming the allocated > amount of quota. This use case is typical of user-interact

Re: [PATCH v3 1/1] sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices

Dave Chiluk writes: > It has been observed, that highly-threaded, non-cpu-bound applications > running under cpu.cfs_quota_us constraints can hit a high percentage of > periods throttled while simultaneously not consuming the allocated > amount of quota. This use case is typical of user-interact

Re: [PATCH v3 1/1] sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices

On Wed, May 29, 2019 at 02:08:46PM -0500 Dave Chiluk wrote: > It has been observed, that highly-threaded, non-cpu-bound applications > running under cpu.cfs_quota_us constraints can hit a high percentage of > periods throttled while simultaneously not consuming the allocated > amount of quota. Thi

[PATCH v3 0/1] sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices

Changelog v3 - Reworked documentation to better describe behavior of slice expiration per feedback from Peter Oskolkov Changelog v2 - Fixed some checkpatch errors in the commit message.

[PATCH v3 1/1] sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices

It has been observed, that highly-threaded, non-cpu-bound applications running under cpu.cfs_quota_us constraints can hit a high percentage of periods throttled while simultaneously not consuming the allocated amount of quota. This use case is typical of user-interactive non-cpu bound applications

[GIT PULL] Fixes for sphinx 2.0 docs build failures

The following changes since commit a65fd4f0def56f59822b2c49522d36319bc8da8b: Documentation: kdump: fix minor typo (2019-05-21 09:31:28 -0600) are available in the Git repository at: git://git.lwn.net/linux.git tags/docs-5.2-fixes2 for you to fetch changes up to 551bd3368a7b3cfef01edaade8970

Re: [PATCH v2 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, 29 May 2019 at 17:33, Mark Rutland wrote: > > On Wed, May 29, 2019 at 04:15:01PM +0200, Marco Elver wrote: > > This adds a new header to asm-generic to allow optionally instrumenting > > architecture-specific asm implementations of bitops. > > > > This change includes the required change f

Re: [PATCH v2 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, May 29, 2019 at 04:15:01PM +0200, Marco Elver wrote: > This adds a new header to asm-generic to allow optionally instrumenting > architecture-specific asm implementations of bitops. > > This change includes the required change for x86 as reference and > changes the kernel API doc to point

Re: [PATCH v2 1/3] lib/test_kasan: Add bitops tests

On Wed, May 29, 2019 at 04:14:59PM +0200, Marco Elver wrote: > This adds bitops tests to the test_kasan module. In a follow-up patch, > support for bitops instrumentation will be added. > > Signed-off-by: Marco Elver > --- > Changes in v2: > * Use BITS_PER_LONG. > * Use heap allocated memory for

Re: [PATCH] ftrace: add simple oneshot function tracer

On Wed, 29 May 2019 11:31:23 +0200 Thomas Preisner wrote: > The "oneshot" tracer records every address (ip, parent_ip) exactly once. > As a result, "oneshot" can be used to efficiently create kernel function > coverage/usage reports such as in undertaker-tailor[0]. > > In order to provide this f

Re: [PATCH 2/3] x86: Move CPU feature test out of uaccess region

On May 29, 2019 7:15:00 AM PDT, Marco Elver wrote: >This patch is a pre-requisite for enabling KASAN bitops >instrumentation: >moves boot_cpu_has feature test out of the uaccess region, as >boot_cpu_has uses test_bit. With instrumentation, the KASAN check would >otherwise be flagged by objtool. >

[PATCH v2 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

This adds a new header to asm-generic to allow optionally instrumenting architecture-specific asm implementations of bitops. This change includes the required change for x86 as reference and changes the kernel API doc to point to bitops-instrumented.h instead. Rationale: the functions in x86's bit

[PATCH v2 1/3] lib/test_kasan: Add bitops tests

This adds bitops tests to the test_kasan module. In a follow-up patch, support for bitops instrumentation will be added. Signed-off-by: Marco Elver --- Changes in v2: * Use BITS_PER_LONG. * Use heap allocated memory for test, as newer compilers (correctly) warn on OOB stack access. --- lib/tes

[PATCH 2/3] x86: Move CPU feature test out of uaccess region

This patch is a pre-requisite for enabling KASAN bitops instrumentation: moves boot_cpu_has feature test out of the uaccess region, as boot_cpu_has uses test_bit. With instrumentation, the KASAN check would otherwise be flagged by objtool. This approach is preferred over adding the explicit kasan_

[PATCH v2 0/3] Bitops instrumentation for KASAN

The previous version of this patch series and discussion can be found here: https://lkml.org/lkml/2019/5/28/769 The most significant change is the change of the instrumented access size to cover the entire word of a bit. Marco Elver (3): lib/test_kasan: Add bitops tests x86: Move CPU feature

Re: [PATCH 6/8] docs/gpu: fix a documentation build break in i915.rst

On Wed, 29 May 2019 08:54:16 +0200 Daniel Vetter wrote: > > Documentation/gpu/i915.rst is not included in the TOC tree, but newer > > versions of sphinx parse it anyway. That leads to this hard build failure: > > > > It is included I think: Documentation/gpu/index.rst -> drivers.rst -> > i91

[PATCH v2 3/3] ima: show rules with IMA_INMASK correctly

Show the '^' character when a policy rule has flag IMA_INMASK. Fixes: 80eae209d63ac ("IMA: allow reading back the current IMA policy") Signed-off-by: Roberto Sassu Cc: sta...@vger.kernel.org --- security/integrity/ima/ima_policy.c | 21 - 1 file changed, 12 insertions(+), 9 d

[PATCH v2 2/3] ima: don't ignore INTEGRITY_UNKNOWN EVM status

Currently, ima_appraise_measurement() ignores the EVM status when evm_verifyxattr() returns INTEGRITY_UNKNOWN. If a file has a valid security.ima xattr with type IMA_XATTR_DIGEST or IMA_XATTR_DIGEST_NG, ima_appraise_measurement() returns INTEGRITY_PASS regardless of the EVM status. The problem is t

[PATCH v2 1/3] evm: check hash algorithm passed to init_desc()

This patch prevents memory access beyond the evm_tfm array by checking the validity of the index (hash algorithm) passed to init_desc(). The hash algorithm can be arbitrarily set if the security.ima xattr type is not EVM_XATTR_HMAC. Fixes: 5feeb61183dde ("evm: Allow non-SHA1 digital signatures") S

[PATCH v2 0/3] ima/evm fixes for v5.2

Changelog v1: - remove patch 2/4 (evm: reset status in evm_inode_post_setattr()); file attributes cannot be set if the signature is portable and immutable - patch 3/4: add __ro_after_init to ima_appraise_req_evm variable declaration - patch 3/4: remove ima_appraise_req_evm kernel option and in

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, May 29, 2019 at 12:57:15PM +0200, Dmitry Vyukov wrote: > On Wed, May 29, 2019 at 12:30 PM Peter Zijlstra wrote: > > > > On Wed, May 29, 2019 at 12:16:31PM +0200, Marco Elver wrote: > > > On Wed, 29 May 2019 at 12:01, Peter Zijlstra wrote: > > > > > > > > On Wed, May 29, 2019 at 11:20:17AM

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, May 29, 2019 at 01:29:51PM +0200, Dmitry Vyukov wrote: > Thanks. I've filed https://bugzilla.kernel.org/show_bug.cgi?id=203751 > for checking alignment with all the points and references, so that > it's not lost. Thanks!

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, May 29, 2019 at 11:20:56AM +, David Laight wrote: > From: Dmitry Vyukov > > Sent: 29 May 2019 11:57 > > Interesting. Does an address passed to bitops also should be aligned, > > or alignment is supposed to be handled by bitops themselves? > > The bitops are defined on 'long []' and it

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, May 29, 2019 at 1:23 PM Andrey Ryabinin wrote: > On 5/29/19 1:57 PM, Dmitry Vyukov wrote: > > On Wed, May 29, 2019 at 12:30 PM Peter Zijlstra > > wrote: > >> > >> On Wed, May 29, 2019 at 12:16:31PM +0200, Marco Elver wrote: > >>> On Wed, 29 May 2019 at 12:01, Peter Zijlstra wrote: > >>>

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On 5/29/19 1:57 PM, Dmitry Vyukov wrote: > On Wed, May 29, 2019 at 12:30 PM Peter Zijlstra wrote: >> >> On Wed, May 29, 2019 at 12:16:31PM +0200, Marco Elver wrote: >>> On Wed, 29 May 2019 at 12:01, Peter Zijlstra wrote: On Wed, May 29, 2019 at 11:20:17AM +0200, Marco Elver wrote: >>

RE: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

From: Dmitry Vyukov > Sent: 29 May 2019 11:57 > On Wed, May 29, 2019 at 12:30 PM Peter Zijlstra wrote: > > > > On Wed, May 29, 2019 at 12:16:31PM +0200, Marco Elver wrote: > > > On Wed, 29 May 2019 at 12:01, Peter Zijlstra wrote: > > > > > > > > On Wed, May 29, 2019 at 11:20:17AM +0200, Marco Elv

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, May 29, 2019 at 12:30 PM Peter Zijlstra wrote: > > On Wed, May 29, 2019 at 12:16:31PM +0200, Marco Elver wrote: > > On Wed, 29 May 2019 at 12:01, Peter Zijlstra wrote: > > > > > > On Wed, May 29, 2019 at 11:20:17AM +0200, Marco Elver wrote: > > > > For the default, we decided to err on th

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, May 29, 2019 at 12:16:31PM +0200, Marco Elver wrote: > On Wed, 29 May 2019 at 12:01, Peter Zijlstra wrote: > > > > On Wed, May 29, 2019 at 11:20:17AM +0200, Marco Elver wrote: > > > For the default, we decided to err on the conservative side for now, > > > since it seems that e.g. x86 oper

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, 29 May 2019 at 12:01, Peter Zijlstra wrote: > > On Wed, May 29, 2019 at 11:20:17AM +0200, Marco Elver wrote: > > For the default, we decided to err on the conservative side for now, > > since it seems that e.g. x86 operates only on the byte the bit is on. > > This is not correct, see for i

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, May 29, 2019 at 11:20:17AM +0200, Marco Elver wrote: > For the default, we decided to err on the conservative side for now, > since it seems that e.g. x86 operates only on the byte the bit is on. This is not correct, see for instance set_bit(): static __always_inline void set_bit(long nr,

Re: [PATCH 2/3] tools/objtool: add kasan_check_* to uaccess whitelist

On Wed, May 29, 2019 at 11:46:10AM +0200, Marco Elver wrote: > On Wed, 29 May 2019 at 10:55, Dmitry Vyukov wrote: > > > > On Tue, May 28, 2019 at 7:19 PM Peter Zijlstra wrote: > > > > > > On Tue, May 28, 2019 at 06:32:57PM +0200, Marco Elver wrote: > > > > This is a pre-requisite for enabling bit

Re: [PATCH 2/3] tools/objtool: add kasan_check_* to uaccess whitelist

On Wed, 29 May 2019 at 10:55, Dmitry Vyukov wrote: > > On Tue, May 28, 2019 at 7:19 PM Peter Zijlstra wrote: > > > > On Tue, May 28, 2019 at 06:32:57PM +0200, Marco Elver wrote: > > > This is a pre-requisite for enabling bitops instrumentation. Some bitops > > > may safely be used with instrument

[PATCH] ftrace: add simple oneshot function tracer

The "oneshot" tracer records every address (ip, parent_ip) exactly once. As a result, "oneshot" can be used to efficiently create kernel function coverage/usage reports such as in undertaker-tailor[0]. In order to provide this functionality, "oneshot" uses a configurable hashset for blacklisting a

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Wed, 29 May 2019 at 10:53, Dmitry Vyukov wrote: > > On Tue, May 28, 2019 at 6:50 PM Mark Rutland wrote: > > > > On Tue, May 28, 2019 at 06:32:58PM +0200, Marco Elver wrote: > > > This adds a new header to asm-generic to allow optionally instrumenting > > > architecture-specific asm implementat

Великденски бонуси

Здравейте, съвременното доплащане на храна под формата на ваучери за храна, които могат да бъдат използвани в най-голямата мрежа от заведения за хранене в страната, е инструмент, който ефективно повишава ефективността на персонала. Изборът на нашите ваучери за храна като форма на социална придо

Re: [PATCH 2/3] tools/objtool: add kasan_check_* to uaccess whitelist

On Tue, May 28, 2019 at 7:19 PM Peter Zijlstra wrote: > > On Tue, May 28, 2019 at 06:32:57PM +0200, Marco Elver wrote: > > This is a pre-requisite for enabling bitops instrumentation. Some bitops > > may safely be used with instrumentation in uaccess regions. > > > > For example, on x86, `test_bit

Re: [PATCH 3/3] asm-generic, x86: Add bitops instrumentation for KASAN

On Tue, May 28, 2019 at 6:50 PM Mark Rutland wrote: > > On Tue, May 28, 2019 at 06:32:58PM +0200, Marco Elver wrote: > > This adds a new header to asm-generic to allow optionally instrumenting > > architecture-specific asm implementations of bitops. > > > > This change includes the required change

[PATCH 21/21] EDAC, Documentation: Describe CPER module definition and DIMM ranks

Update on CPER DIMM naming convention and DIMM ranks. Signed-off-by: Robert Richter --- Documentation/admin-guide/ras.rst | 31 +++ 1 file changed, 19 insertions(+), 12 deletions(-) diff --git a/Documentation/admin-guide/ras.rst b/Documentation/admin-guide/ras.rst i