From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] fchownat/fchownat01.c: cleanup
Date: Tue, 10 Dec 2013 14:46:22 +0100 [thread overview]
Message-ID: <20131210134622.GA25591@rei> (raw)
In-Reply-To: <129748009.2529202.1386682206895.JavaMail.root@redhat.com>
Hi!
> > > -uid_t uid;
> > > -gid_t gid;
> > > -
> > > -int myfchownat(int dirfd, const char *filename, uid_t owner, gid_t group,
> > > - int flags)
> > > -{
> > > - return ltp_syscall(__NR_fchownat, dirfd, filename, owner, group, flags);
> > > -}
> >
> > Hmm, glibc 2.4 (first one with fchownat() support) has been released in
> > 2006. I wonder if seven years is long enough and if we can get rid of
> > the wrapper now... Moreover I'm not sure what is the status of
> > alternative libc implementations.
> >
> > There still may be enterprise distributions that still have older glibc
> > than that. Anybody out there?
>
> To my knowledge the oldest RHEL LTP is run against is RHEL5.3,
> which has glibc 2.5.
It seems to be glibc 2.4 for SLES10 SP3, which is just barely enough.
So I would just keep the wrapper for a few more years. Or even better we
should create a configure check for the fchownat() syscall and define
the wrapper only when it's not available.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-12-10 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 5:25 [LTP] [PATCH] fchownat/fchownat01.c: cleanup zenglg.jy
2013-12-10 13:17 ` chrubis
[not found] ` <129748009.2529202.1386682206895.JavaMail.root@redhat.com>
2013-12-10 13:46 ` chrubis [this message]
[not found] ` <1393326701.1952.59.camel@G08JYZSD130126>
2014-02-25 15:11 ` [LTP] [PATCH v2 1/2] " chrubis
[not found] ` <1393326785.1952.61.camel@G08JYZSD130126>
2014-02-25 15:45 ` [LTP] [PATCH v2 2/2] fchownat/fchownat02.c: add a new test chrubis
[not found] ` <1393407258.2066.5.camel@G08JYZSD130126>
2014-02-26 12:41 ` [LTP] [PATCH v3 1/3] include/safe_macros.h: fix mistakes chrubis
[not found] ` <1393407370.2066.7.camel@G08JYZSD130126>
2014-02-26 12:41 ` [LTP] [PATCH v3 3/3] fchownat/fchownat02.c: add a new test chrubis
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=20131210134622.GA25591@rei \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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