From: Jeff Layton <jlayton@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: Peter Staubach <staubach@redhat.com>,
Andrew@sc8-sf-spam2.sourceforge.net, nfsv4@linux-nfs.org,
linux-kernel@vger.kernel.org,
Trond Myklebust <trond.myklebust@fys.uio.no>,
nfs@lists.sourceforge.net, Pierre Ossman <drzeus-list@drzeus.cx>,
Morton <akpm@linux-foundation.org>
Subject: Re: What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree...
Date: Fri, 5 Oct 2007 14:00:37 -0400 [thread overview]
Message-ID: <20071005140037.1309a8d3.jlayton@redhat.com> (raw)
In-Reply-To: <30494.1191605410@turing-police.cc.vt.edu>
On Fri, 05 Oct 2007 13:30:10 -0400
Valdis.Kletnieks@vt.edu wrote:
>
> How does Joe Sysadmin tell if he has an affected legacy app or not?
>
> (The obvious "try it and see what breaks" is a non-starter for many places,
> because you too easily end up in a loop of "enable it, find 4-5 show stoppers,
> turn it off, fix them, lather rinse repease". Been there, done that, got
> the tshirt - a project I got dragged into involves a large storage array that
> appears to insist on exporting 64-bit stuff, and a large farm of clients that
> are very 64-bit unclean....)
>
In addition to Trond's suggestion, you might be able to use "nm" or
something like it and see if there are references to non-LFS (f)stat
calls in your binaries. For instance, if you see references to stat()
(and not stat64()), then the app is probably not built with 64-bit file
offsets.
This is probably not as reliable as Trond's method, but it might be
less invasive and reasonable for a first pass when looking for these
sorts of apps...
--
Jeff Layton <jlayton@redhat.com>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Layton <jlayton@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Peter Staubach <staubach@redhat.com>,
nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org,
nfs@lists.sourceforge.net, Pierre Ossman <drzeus-list@drzeus.cx>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [NFS] What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree...
Date: Fri, 5 Oct 2007 14:00:37 -0400 [thread overview]
Message-ID: <20071005140037.1309a8d3.jlayton@redhat.com> (raw)
In-Reply-To: <30494.1191605410@turing-police.cc.vt.edu>
On Fri, 05 Oct 2007 13:30:10 -0400
Valdis.Kletnieks@vt.edu wrote:
>
> How does Joe Sysadmin tell if he has an affected legacy app or not?
>
> (The obvious "try it and see what breaks" is a non-starter for many places,
> because you too easily end up in a loop of "enable it, find 4-5 show stoppers,
> turn it off, fix them, lather rinse repease". Been there, done that, got
> the tshirt - a project I got dragged into involves a large storage array that
> appears to insist on exporting 64-bit stuff, and a large farm of clients that
> are very 64-bit unclean....)
>
In addition to Trond's suggestion, you might be able to use "nm" or
something like it and see if there are references to non-LFS (f)stat
calls in your binaries. For instance, if you see references to stat()
(and not stat64()), then the app is probably not built with 64-bit file
offsets.
This is probably not as reliable as Trond's method, but it might be
less invasive and reasonable for a first pass when looking for these
sorts of apps...
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2007-10-05 18:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 23:41 What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree Trond Myklebust
2007-10-03 23:41 ` Trond Myklebust
2007-10-03 23:52 ` Jeff Garzik
2007-10-04 6:52 ` Pierre Ossman
2007-10-04 6:52 ` Pierre Ossman
2007-10-04 14:00 ` [NFS] " Trond Myklebust
2007-10-04 14:00 ` Trond Myklebust
2007-10-04 16:43 ` Pierre Ossman
2007-10-04 18:42 ` Andrew Morton
2007-10-04 18:42 ` [NFS] " Andrew Morton
2007-10-04 19:16 ` Trond Myklebust
2007-10-04 19:16 ` Trond Myklebust
2007-10-04 19:41 ` Peter Staubach
2007-10-04 19:41 ` [NFS] " Peter Staubach
2007-10-05 6:25 ` Pierre Ossman
2007-10-05 6:25 ` [NFS] " Pierre Ossman
2007-10-05 12:24 ` Jeff Layton
2007-10-05 17:36 ` [NFS] " Trond Myklebust
2007-10-05 17:54 ` Pierre Ossman
2007-10-05 17:54 ` [NFS] " Pierre Ossman
2007-10-04 19:59 ` Andrew Morton
2007-10-04 19:59 ` Andrew Morton
2007-10-05 0:58 ` Trond Myklebust
2007-10-05 0:58 ` Trond Myklebust
2007-10-05 17:30 ` Valdis.Kletnieks
2007-10-05 17:30 ` [NFS] " Valdis.Kletnieks
2007-10-05 17:52 ` Trond Myklebust
2007-10-05 17:52 ` Trond Myklebust
2007-10-05 18:00 ` Jeff Layton [this message]
2007-10-05 18:00 ` Jeff Layton
2007-10-08 8:36 ` Greg Banks
2007-10-05 18:12 ` Jeff Layton
2007-10-05 18:12 ` Jeff Layton
2007-10-07 22:56 ` David Chinner
2007-10-04 20:16 ` Chuck Lever
2007-10-05 17:31 ` Trond Myklebust
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=20071005140037.1309a8d3.jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=Andrew@sc8-sf-spam2.sourceforge.net \
--cc=Valdis.Kletnieks@vt.edu \
--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 \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.