From: chrubis@suse.cz
To: Helge Deller <deller@gmx.de>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] fcntl16.c patch
Date: Thu, 7 Nov 2013 12:19:01 +0100 [thread overview]
Message-ID: <20131107111901.GA28246@rei> (raw)
In-Reply-To: <527A964D.6030004@gmx.de>
Hi!
> >> The fcntl16 testcase is being compiled twice, once normal, and the other
> >> time with the _FILE_OFFSET_BITS=64 define set.
> >>
> >> When compiled with 64bit file functions (as fcntl16_64) all
> >> file functions will automatically use their 64bit variants, e.g.
> >> "struct flock64" instead of "struct flock".
> >>
> >> So, when in the code e.g.
> >> fcntl(fd, F_SETLK, thislock)
> >> is called, this will automatically be translated into
> >> fcntl64(fd, F_SETLK64, thislock)
> >> and "thislock" needs to be of type "struct flock64".
> >>
> >> So, we need to make sure that thislock is of the correct type,
> >> with the start and len fields being of type "off_t" which then
> >> will be translated into "loff_t" during compilation when
> >> _FILE_OFFSET_BITS=64 is set.
> >>
> >> This fixes the fcntl16_64 testcase on hppa64-linux-gnu with
> >> 32bit userspace running on 64bit kernel.
> >>
> >> Signed-off-by: Helge Deller <deller@gmx.de>
> >
> > What about using struct flock as defined in bits/fcntl.h instead?
>
> Sure, that's possible.
> Patch is attached.
>
> I would be happy if you would apply one of those.
Applied, thanks.
And it would be easier for me if you had send git formatted patch with
headline and description (output from git format-patch).
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2013-11-07 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 21:05 [LTP] [PATCH] fcntl16.c patch Helge Deller
2013-11-06 12:32 ` chrubis
[not found] ` <527A964D.6030004@gmx.de>
2013-11-07 11:19 ` chrubis [this message]
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=20131107111901.GA28246@rei \
--to=chrubis@suse.cz \
--cc=deller@gmx.de \
--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