From: Alejandro Colomar <alx@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-man@vger.kernel.org, linux-xfs@vger.kernel.org,
mtk.manpages@gmail.com
Subject: Re: quotactl(2) (was: [PATCH v2] man/man2: introduce man page for file_getattr/file_setattr syscalls)
Date: Tue, 15 Sep 2026 22:46:19 +0200 [thread overview]
Message-ID: <aqmtYCLEnLh-j6Yp@devuan> (raw)
In-Reply-To: <20260915181047.GI6283@frogsfrogsfrogs>
[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]
Hey Darrick,
> Date: 2026-09-15 11:10:47-0700
> From: "Darrick J. Wong" <djwong@kernel.org>
>
> On Fri, Sep 11, 2026 at 12:38:23AM +0200, Alejandro Colomar wrote:
> > [CC trimmed]
> >
> > Hi Darrick,
> >
> > > > Date: 2026-09-10 09:44:28-0700
> > > > From: "Darrick J. Wong" <djwong@kernel.org>
> > > >
> > > > quotactl (and xattrs) have a similar weird history of originating in XFS
> > > > and later getting yanked into the vfs. Every time I have to go look up
> > > > the quota syscalls I just get a headache. :/
> >
> > I have recently worked on having quotactl(2) split into more organized
> > manual pages. This has been part of the man-pages-6.19 release.
> > Have you had a look at these manual pages after that change? Did the
> > headache experience improve (or worsen) after this change?
> >
> > Michael's man7.org already includes the latest version:
> > <https://www.man7.org/linux/man-pages/man2/quotactl.2.html>
> >
> > I'd welcome feedback, and any improvements or suggestions to improve
> > the pages.
>
> Oh hey, that /is/ a lot better!
Thanks!! Michael didn't like these splitting changes at first (I don't
know if I've convinced him yet), but it's good to see users that like
the change. :-)
> The only addition I can think of is that QUOTAOFF generally isn't
> supported anymore.
Oh, thanks! I can add a note that it's deprecated. If you want to add
a more specific note saying it fails for new kernels, I'd need some
information for preparing a patch:
- Is it reporting an error?
- If so, which error?
- Which kernel version dropped support?
- You said 'generally'. In which cases is it still supported?
- Any other ideas about it?
> Thanks for breaking up that big messy manpage. :)
Thank you for liking it! :)
Have a lovely night!
Alex
>
> --D
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-15 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 10:41 [PATCH v2] man/man2: introduce man page for file_getattr/file_setattr syscalls Andrey Albershteyn
2026-09-10 13:20 ` Alejandro Colomar
2026-09-10 16:12 ` Darrick J. Wong
2026-09-10 16:31 ` Alejandro Colomar
2026-09-10 16:44 ` Darrick J. Wong
2026-09-10 16:50 ` Alejandro Colomar
2026-09-10 22:38 ` quotactl(2) (was: [PATCH v2] man/man2: introduce man page for file_getattr/file_setattr syscalls) Alejandro Colomar
2026-09-15 18:10 ` Darrick J. Wong
2026-09-15 20:46 ` Alejandro Colomar [this message]
2026-09-11 11:17 ` [PATCH v2] man/man2: introduce man page for file_getattr/file_setattr syscalls Andrey Albershteyn
2026-09-11 11:56 ` 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=aqmtYCLEnLh-j6Yp@devuan \
--to=alx@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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