From: Bruno Meneguele <bmeneg@redhat.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH] ima-evm-utils: Enable large-file support
Date: Wed, 21 Aug 2019 09:35:23 -0300 [thread overview]
Message-ID: <20190821123523.GA9599@rhlt> (raw)
In-Reply-To: <20190820194236.tgyhdlw5kgygcnsu@altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]
On Tue, Aug 20, 2019 at 10:42:36PM +0300, Vitaly Chikunov wrote:
> Bruno,
>
> On Tue, Aug 20, 2019 at 12:19:39PM -0300, Bruno Meneguele wrote:
> > On Mon, Aug 19, 2019 at 11:25:07PM +0300, Vitaly Chikunov wrote:
> > > Some architectures require special measures to access large files (LFS).
> > > Add `AC_SYS_LARGEFILE' to `configure.ac' to handle this.
> > >
> > > It seems that ABI is not changed with this.
> > >
> > > Signed-off-by: Vitaly Chikunov <vt@altlinux.org>
> > > ---
> > > configure.ac | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/configure.ac b/configure.ac
> > > index 3f21ba4..02bd6f8 100644
> > > --- a/configure.ac
> > > +++ b/configure.ac
> > > @@ -8,6 +8,7 @@ AC_CONFIG_MACRO_DIR([m4])
> > >
> > > AC_CANONICAL_HOST
> > > AC_USE_SYSTEM_EXTENSIONS
> > > +AC_SYS_LARGEFILE
> > >
> >
> > Should we also add AC_FUNC_FSEEKO?
> >
> > I can't see any use of fseek or ftell in the code, but if we are
> > enabling AC_SYS_LARGEFILE by default we also should check for
> > AC_FUNC_FSEEKO in order to allow the use of fseeko/ftello whenever
> > needed.
>
> I thought about AC_FUNC_FSEEKO, but we don't use fseeko/ftello, so it
> didn't look useful.
>
> Thanks,
>
That's fine by me :)
Just was wondering if we should consider now that for possible use in
future. But indeed, that'll be useful only if we would use
fseeko/ftello.
Thanks.
Reviewed-by: Bruno Meneguele <bmeneg@redhat.com>
>
> >
> > > # Checks for programs.
> > > AC_PROG_CC
> > > --
> > > 2.11.0
> > >
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-08-21 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 20:25 [PATCH] ima-evm-utils: Enable large-file support Vitaly Chikunov
2019-08-20 15:19 ` Bruno Meneguele
2019-08-20 19:42 ` Vitaly Chikunov
2019-08-21 12:35 ` Bruno Meneguele [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=20190821123523.GA9599@rhlt \
--to=bmeneg@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).