From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Peter Staubach <staubach@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
nfsv4@linux-nfs.org, nfs@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [NFS] What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree...
Date: Fri, 05 Oct 2007 13:36:19 -0400 [thread overview]
Message-ID: <1191605779.6715.86.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20071005082513.4b5a058c@poseidon.drzeus.cx>
On Fri, 2007-10-05 at 08:25 +0200, Pierre Ossman wrote:
> Print a warning or something so that they can be found. Don't go
> breaking systems left and right. People have better things to do than
> to fix the build systems for ever program they use.
The kernel knows bugger all about what glibc function your program is
calling. The problem here is precisely that newer versions of glibc will
transform legacy 32-bit stat() calls into 64-bit stat64() calls, then
will complain when the result overflows.
If you want to figure out which apps are broken, then you will have to
either do so in glibc or use a preloaded shared library to intercept the
32-bit stat() calls and print out a warning.
Trond
next prev parent reply other threads:[~2007-10-05 17:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 23:41 Trond Myklebust
2007-10-03 23:52 ` Jeff Garzik
2007-10-04 6:52 ` Pierre Ossman
2007-10-04 14:00 ` [NFS] " Trond Myklebust
2007-10-04 16:43 ` Pierre Ossman
2007-10-04 18:42 ` Andrew Morton
2007-10-04 19:16 ` Trond Myklebust
2007-10-04 19:41 ` Peter Staubach
2007-10-05 6:25 ` Pierre Ossman
2007-10-05 17:36 ` Trond Myklebust [this message]
2007-10-05 17:54 ` Pierre Ossman
2007-10-04 19:59 ` Andrew Morton
2007-10-05 0:58 ` Trond Myklebust
2007-10-05 17:30 ` Valdis.Kletnieks
2007-10-05 17:52 ` Trond Myklebust
2007-10-05 18:00 ` Jeff Layton
2007-10-08 8:36 ` Greg Banks
2007-10-05 18:12 ` Jeff Layton
2007-10-07 22:56 ` David Chinner
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=1191605779.6715.86.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@linux-foundation.org \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
--cc=staubach@redhat.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
all inboxes | Powered by JetHome®