Re: [PATCH 5/5] docs: sysctl/fs: re-order, prettify

kernel test robot
2022-07-16T19:45:39Z

Hi Stephen,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on 50fd82b3a9a9335df5d50c7ddcb81c81d358c4fc]

url: https://github.com/intel-lab-lkp/linux/commits/Stephen-Kitt/docs-sysctl-remove-references-to-inode-max/20220713-014344
base: 50fd82b3a9a9335df5d50c7ddcb81c81d358c4fc
reproduce: make htmldocs

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> Documentation/admin-guide/sysctl/fs.rst:260: WARNING: undefined label: core_pattern (if the link has no caption the label must precede a section header)

vim +260 Documentation/admin-guide/sysctl/fs.rst

249
250 = ========== ===============================================================
251 0 (default) Traditional behaviour. Any process which has changed
252 privilege levels or is execute only will not be dumped.
253 1 (debug) All processes dump core when possible. The core dump is
254 owned by the current user and no security is applied. This is
255 intended for system debugging situations only.
256 Ptrace is unchecked.
257 This is insecure as it allows regular users to examine the
258 memory contents of privileged processes.
259 2 (suidsafe) Any binary which normally would not be dumped is dumped
> 260 anyway, but only if the ``core_pattern`` kernel sysctl (see
261 :ref:`Documentation/admin-guide/sysctl/kernel.rst <core_pattern>`)
262 is set to
263 either a pipe handler or a fully qualified path. (For more
264 details on this limitation, see CVE-2006-2451.) This mode is
265 appropriate when administrators are attempting to debug
266 problems in a normal environment, and either have a core dump
267 pipe handler that knows to treat privileged core dumps with
268 care, or specific directory defined for catching core dumps.
269 If a core dump happens without a pipe handler or fully
270 qualified path, a message will be emitted to syslog warning
271 about the lack of a correct setting.
272 = ========== ===============================================================
273
274
275

--
0-DAY CI Kernel Test Service