Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: libc-help@sourceware.org
Cc: Jan Kara <jack@suse.cz>,
	linux-man@vger.kernel.org,  Petr Gajdos <pgajdos@suse.cz>
Subject: Why is caddr_t used in quotactl(2)?
Date: Mon, 18 May 2026 17:17:49 +0200	[thread overview]
Message-ID: <agssqAsUt9aYBsHX@devuan> (raw)
In-Reply-To: <b2kszapero3mb6q3763rrgjjfltkvt7aapm6s7oakpbpepfypk@mwybch7ayyqd>

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

[looping libc-help@]

Hi all,

On 2026-05-18T17:05:59+0200, Jan Kara wrote:
> Hi Alejandro!
> 
> On Mon 18-05-26 14:51:45, Alejandro Colomar wrote:
> > Also, I wonder why caddr_t was used at all, instead of void*.  It seems
> > to unnecessarily require a cast, which could have been avoided with
> > void*.  In quotactl_fd(), since we need to use syscall(2), which is
> > variadic, I'll document the correct pointer types, instead of caddr_t*.
> 
> For this I don't have a good answer. It was like that for ages... I guess
> you can ask glibc guys - the kernel uses void * but glibc uses caddr_t.

Does anyone know why glibc uses caddr_t in quotactl(2)?  It seems to me
that void* would be obviously better, by not needing a cast.

-  Why was it added in the first place, given the kernel uses void*
   internally?

-  Can we change it now to be void*?


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es>

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

      parent reply	other threads:[~2026-05-18 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-16 17:12 [PATCH v1] man/man2/quotactl.2: tfix Alejandro Colomar
2026-05-18 10:20 ` Jan Kara
2026-05-18 10:27   ` Alejandro Colomar
2026-05-18 12:51   ` Alejandro Colomar
2026-05-18 15:05     ` Jan Kara
2026-05-18 15:12       ` Alejandro Colomar
2026-05-18 15:17       ` Alejandro Colomar [this message]

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=agssqAsUt9aYBsHX@devuan \
    --to=alx@kernel.org \
    --cc=jack@suse.cz \
    --cc=libc-help@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=pgajdos@suse.cz \
    /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