From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 1/5] syscalls/quotactl01: Add Q_GETNEXTQUOTA test
Date: Thu, 21 Nov 2019 11:30:03 +0100 [thread overview]
Message-ID: <20191121103003.GC23702@dell5510> (raw)
In-Reply-To: <1893160007.13287158.1574326875945.JavaMail.zimbra@redhat.com>
Hi Jan, Li,
> ----- Original Message -----
> > @Jan, @Cyril: Do we want to generally avoid loading <linux/types.h> if not
> > really needed?
> Yes, we generally try to avoid including kernel headers. Our style-guide says
> "Don't use +linux/+ headers if at all possible". uapi on older distros
> was more prone to cause LTP build errors.
Thank you for pointing out docs, I completely forgot on this page.
BTW it needs some update (examples use old API, linux_syscall_numbers.h).
Also not sure if everything else still applies (4. Call APIs that don't require
freeing up resources on failure first, 2. Sort headers).
> > Also ,If we use uint64_t, they still failed on 2.6.32-754.el6.x86_64 with undefined . Or, we should use TST_ABI to define uint64_t them
Jan, are you aware of this problem?
Xu, I'm not sure if you're talking about uint64_t problematic in <linux/types.h>
(as you mention kernel) or problem in glibc <sys/types.h> / <stdint.h> / <inttypes.h>?
We have lots of code which is using some of these 3 libc headers, does it fail
on 2.6.32?
Does anybody compile for 2.6.32?
I know we want to keep support for 2.6.x (we had some discussion in the past).
Than it'd be good to have travis build for kernel 2.6.x.
Back to patchset. I suggest to merge it as it is and I'll prepare patches, which
use <sys/types.h> in our tests.
Kind regards,
Petr
next prev parent reply other threads:[~2019-11-21 10:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 9:13 [LTP] [PATCH v4 0/5] optimize quotactl test code Yang Xu
2019-11-20 9:13 ` [LTP] [PATCH v4 1/5] syscalls/quotactl01: Add Q_GETNEXTQUOTA test Yang Xu
2019-11-20 15:12 ` Petr Vorel
2019-11-20 15:16 ` Petr Vorel
2019-11-21 3:37 ` Yang Xu
2019-11-21 5:10 ` Petr Vorel
2019-11-21 7:07 ` Yang Xu
2019-11-21 8:21 ` Petr Vorel
2019-11-21 9:01 ` Yang Xu
2019-11-21 2:29 ` Yang Xu
2019-11-21 5:45 ` Petr Vorel
2019-11-21 7:45 ` Yang Xu
2019-11-21 8:32 ` Petr Vorel
2019-11-21 8:38 ` Yang Xu
2019-11-21 9:01 ` Jan Stancek
2019-11-21 10:30 ` Petr Vorel [this message]
2019-11-21 11:08 ` Jan Stancek
2019-11-21 15:19 ` Petr Vorel
2019-11-20 9:13 ` [LTP] [PATCH v4 2/5] syscalls/quotactl02: Add Q_XGETQSTATV test and group quota tests Yang Xu
2019-11-20 9:13 ` [LTP] [PATCH v4 3/5] syscalls/quotactl04: add project quota test for non-xfs filesystem Yang Xu
2019-11-20 9:13 ` [LTP] [PATCH v4 4/5] syscalls/quotactl05: add project quota test on xfs filesystem Yang Xu
2019-11-20 9:13 ` [LTP] [PATCH v4 5/5] syscalls/quotactl06: Add new error testcase Yang Xu
2019-11-21 17:01 ` [LTP] [PATCH v4 0/5] optimize quotactl test code Petr Vorel
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=20191121103003.GC23702@dell5510 \
--to=pvorel@suse.cz \
--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