All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Peter Staubach <staubach@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org,
	nfs@lists.sourceforge.net
Subject: Re: What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree...
Date: Fri, 5 Oct 2007 19:54:37 +0200	[thread overview]
Message-ID: <20071005195437.2795f15a@poseidon.drzeus.cx> (raw)
In-Reply-To: <1191605779.6715.86.camel@heimdal.trondhjem.org>

On Fri, 05 Oct 2007 13:36:19 -0400
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:

> 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.
> 

Right, I didn't suggest that this had to be done in the kernel. My
point was that first you mark something as deprecated, make a lot of
noise when someone uses it so that problems can be identified, and some
time later you remove it. You don't just remove it and let production
systems deal with the fallout.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

-------------------------------------------------------------------------
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: Pierre Ossman <drzeus-list@drzeus.cx>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
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, 5 Oct 2007 19:54:37 +0200	[thread overview]
Message-ID: <20071005195437.2795f15a@poseidon.drzeus.cx> (raw)
In-Reply-To: <1191605779.6715.86.camel@heimdal.trondhjem.org>

On Fri, 05 Oct 2007 13:36:19 -0400
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:

> 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.
> 

Right, I didn't suggest that this had to be done in the kernel. My
point was that first you mark something as deprecated, make a lot of
noise when someone uses it so that problems can be identified, and some
time later you remove it. You don't just remove it and let production
systems deal with the fallout.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

  reply	other threads:[~2007-10-05 17:54 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 [this message]
2007-10-05 17:54                   ` 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
2007-10-05 18:00         ` [NFS] " 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=20071005195437.2795f15a@poseidon.drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=akpm@linux-foundation.org \
    --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.