public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "Александр Офицеров" <oficerovas@altlinux.org>
Cc: dutyrok@altlinux.org, kovalev@altlinux.org, linux-man@vger.kernel.org
Subject: Re: man page for syscall delete_module is outdated
Date: Mon, 19 Feb 2024 12:56:59 +0100	[thread overview]
Message-ID: <ZdNCCy_Yx4Ekx4Mj@debian> (raw)
In-Reply-To: <08125e65-52ed-a846-2b38-c7f63071c898@basealt.ru>

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

Hi,

On Mon, Feb 19, 2024 at 11:17:29AM +0300, Александр Офицеров wrote:
> Found out that man page for delete_module syscall is outdated.
> The behaviour described there doesn't match to code, specifically for
> unloading module if its have no refcnt. Parameter O_NONBLOCK described in
> man doesn't exist anymore in kernel versions 3.13+, which is quite old, only
> O_TRUNC parameter present for actual kernel version, O_NONBLOCK does
> nothing.
> I've also opened an issue on bugzilla:
> https://bugzilla.kernel.org/show_bug.cgi?id=218489

Would you mind suggesting a patch?  Also, would you mind showing your
findings in the kernel code?

See also:
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING>
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING.d/bugs>
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING.d/patches>
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING.d/mail>

Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-02-19 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  8:17 man page for syscall delete_module is outdated Александр Офицеров
2024-02-19 11:56 ` Alejandro Colomar [this message]
2024-02-19 16:11   ` Alexander Ofitserov
2024-03-04 16:10     ` Alejandro Colomar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZdNCCy_Yx4Ekx4Mj@debian \
    --to=alx@kernel.org \
    --cc=dutyrok@altlinux.org \
    --cc=kovalev@altlinux.org \
    --cc=linux-man@vger.kernel.org \
    --cc=oficerovas@altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox