public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: xuyang <xuyang2018.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] ltp-cap.m4: add libcap version detection && fix compiler error
Date: Wed, 15 May 2019 17:01:24 +0800	[thread overview]
Message-ID: <5CDBD564.8010300@cn.fujitsu.com> (raw)
In-Reply-To: <20190514120119.GA26452@dell5510>

on 2019/05/14 20:01, Petr Vorel wrote:
> Hi Yang,
>
>> Hi Peter
>>    I sent a mail to you last Friday mentioned this problem.
> Noticed, before I find a time you send a patch, so I replied to it (it's always
> better to send a question in public).
>
OK. I  got it.

>> At the beginning, I
>>    think it makes no sense because libcap-1 is too old.  But I notices that ltp-quota.m4
>>    has quota_v1 and quota_v2. I changes my mind.
>>    Since we have drop libnuma v1, I agree with you that we also drop libcap v1(too old).
>>    Also, I think we should drop quota_v1 because it is too old (since Linux 2.4.22, Q_GETINFO has
>>    been supported in kernel).
> Good point. But I'm not sure if it's the same, as QFMT_VFS_OLD is part of kernel
> source tree (part of kernel space code) so it makes sense to test it, whereas
> libcap v1 and libnuma v1 are just old versions of user space library.
> Or am I wrong?
Hi Petr

    I have seen kernel source about quota and try it. I think you are right.  But current quota_v1
and quota_v2 detection has problem. In kernel source, I disable CONFIG_QFMT_V2 and enable CONFIG_QFMT_V1
,then I found ltp still detects quotav2 instead of quotav1,  and run ./quotactl01, the following error occurs:

./quotactl01
tst_device.c:84: INFO: Found free device '/dev/loop0'
tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
mke2fs 1.44.4 (18-Aug-2018)
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
quotactl01.c:195: FAIL: quotactl failed to turn on quota for user: ESRCH
quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for user: ESRCH
quotactl01.c:195: FAIL: quotactl failed to get disk quota limit for user: ESRCH
quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for user: ESRCH
quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for user: ESRCH
quotactl01.c:195: FAIL: quotactl failed to get quota format for user: ESRCH
quotactl01.c:206: PASS: quotactl succeeded to update quota usages for user
quotactl01.c:206: PASS: quotactl succeeded to turn off quota for user
quotactl01.c:195: FAIL: quotactl failed to turn on quota for group: ESRCH
quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH
quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH
quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for group: ESRCH
quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for group: ESRCH
quotactl01.c:195: FAIL: quotactl failed to get quota format for group: ESRCH
quotactl01.c:206: PASS: quotactl succeeded to update quota usages for group
quotactl01.c:206: PASS: quotactl succeeded to turn off quota for group

Summary:
passed   4
failed   12
skipped  0
warnings 0

Kind Regards,
Yang Xu

>> Kind Regards,
>> Yang Xu
> Kind regards,
> Petr
>
>
>




  reply	other threads:[~2019-05-15  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13  7:26 [LTP] [PATCH] ltp-cap.m4: add libcap version detection && fix compiler error Yang Xu
2019-05-13 13:14 ` Petr Vorel
2019-05-14  5:24   ` xuyang
2019-05-14 12:01     ` Petr Vorel
2019-05-15  9:01       ` xuyang [this message]
2019-05-15 14:37         ` Petr Vorel
2019-05-16  6:44           ` xuyang
2019-05-16  6:52           ` [LTP] [PATCH v2] security: add missing PR_CAPBSET_READ/PR_CAPBSET_DROP check Yang Xu
2019-06-20 11:49             ` Petr Vorel
2019-06-21  2:01               ` Yang Xu

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=5CDBD564.8010300@cn.fujitsu.com \
    --to=xuyang2018.jy@cn.fujitsu.com \
    --cc=ltp@lists.linux.it \
    /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