From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
Jan Kara <jack@suse.cz>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
Eugene Syromyatnikov <evgsyr@gmail.com>
Subject: Re: [PATCH] quotactl.2: Remove kernel version for Q_XQUOTARM ioctl
Date: Fri, 5 Nov 2021 03:05:44 +0000 [thread overview]
Message-ID: <61849F99.80502@fujitsu.com> (raw)
In-Reply-To: <e3dbb664-6745-e7d2-e414-268cea320df3@gmail.com>
on 2021/11/5 4:10, Alejandro Colomar (man-pages) wrote:
> Hi Jan and Yang,
>
> On 11/4/21 11:53, Jan Kara wrote:
>> On Thu 04-11-21 00:58:02, xuyang2018.jy@fujitsu.com wrote:
>>>>>>>> This patch[1] is designed to fix bug for Q_XQUOTARM ioctl not for
>>>>>>>> introduced.
>>>>>>>> So remove it.
>>>>>>>>
>>>>>>>> [1]https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da93f9b7c
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Signed-off-by: Yang Xu<xuyang2018.jy@fujitsu.com>
>>>>>>>> ---
>>>>>>>> man2/quotactl.2 | 3 +--
>>>>>>>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>>>>>>>
>>>>>>>> diff --git a/man2/quotactl.2 b/man2/quotactl.2
>>>>>>>> index d22d8c584..46f77a8b1 100644
>>>>>>>> --- a/man2/quotactl.2
>>>>>>>> +++ b/man2/quotactl.2
>>>>>>>> @@ -651,8 +651,7 @@ The
>>>>>>>> .I id
>>>>>>>> argument is ignored.
>>>>>>>> .TP
>>>>>>>> -.B Q_XQUOTARM " (since Linux 3.16)"
>>>>>>>> -.\" 9da93f9b7cdf8ab28da6b364cdc1fafc8670b4dc
>
> I applied the patch.
Thanks.
>>>>
>>>> Okay. Since you added that line (man-pages commit ae848b1d80), I'm fine
>>>> removing it. Was it a mistake? The commit message of that commit is a
>>>> bit unrelated to Q_XQUOTARM, isn't it?
>>> Yes.
>>
>> Well, that commit fixed Q_XQUOTARM quotactl. Previously it was supported
>> but it was buggy and not actually doing the desired functionality in some
>> cases. So the description kind of make sense but it is not quite
>> accurate -
>> maybe we should just move the note to NOTES section?
>
> I think we better add a BUGS section. Don't you?
> Unless you think it isn't important enough. How likely is it that
> Q_XQUOTARM was used in kernels before 3.16 and a BUGS section will help
> fix the bug? And how likely is it that someone will use it in the future
> for kernels before 3.16? How important/dangerous was the bug?
@Jan
I doubt this ioctl whether be used by any application.
ps:I also increase ltp quotactl coverage to cover quotactl_fd syscall. I
would appreciate it if you could review my ltp quotactl/quotactl_fd patchset
https://patchwork.ozlabs.org/project/ltp/list/?series=269166
>
> Maybe add something simpler such as "(buggy until Linux 3.16)" so that
> no one uses it in older kernels but doesn't use as much space as a new
> BUGS section?
@Alejandro
If this ioctl doesn't be used by many application(IMO,it is rare to be
used ), using "(buggy until Linux 3.16)" is better.
Best Regards
Yang Xu
>
>>
>>>> Maybe a better fix would be to replace the kernel version and the
>>>> commit
>>>> hash when it was really added?
>>> Yes, but I can't find this commit hash and it seems been supported since
>>> long time ago.
>>
>> Yeah, AFAIK Q_XQUOTARM is there in principle since XFS was introduced in
>> the linux kernel so around 2001. No point of mentioning that in the
>> manpage
>> IMO.
>>
>> Honza
>>
>
> Thanks,
>
> Alex
>
>
next prev parent reply other threads:[~2021-11-05 3:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 1:46 [PATCH] quotactl.2: Remove kernel version for Q_XQUOTARM ioctl Yang Xu
2021-11-01 3:38 ` xuyang2018.jy
2021-11-03 9:19 ` xuyang2018.jy
2021-11-03 9:29 ` xuyang2018.jy
2021-11-03 14:29 ` Alejandro Colomar (man-pages)
2021-11-04 0:58 ` xuyang2018.jy
2021-11-04 10:43 ` Eugene Syromyatnikov
2021-11-04 11:02 ` Eugene Syromyatnikov
2021-11-04 10:53 ` Jan Kara
2021-11-04 20:10 ` Alejandro Colomar (man-pages)
2021-11-05 3:05 ` xuyang2018.jy [this message]
2021-11-05 11:34 ` Jan Kara
2021-11-08 2:37 ` xuyang2018.jy
2021-11-05 11:20 ` Jan Kara
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=61849F99.80502@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=alx.manpages@gmail.com \
--cc=evgsyr@gmail.com \
--cc=jack@suse.cz \
--cc=linux-man@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