public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@ubuntu.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [Ubuntu PATCH] fix VFS nr_files accounting
Date: Tue, 04 Jul 2006 11:06:56 -0400	[thread overview]
Message-ID: <1152025616.23756.93.camel@grayson> (raw)
In-Reply-To: <20060703235031.0fe17c18.akpm@osdl.org>

On Mon, 2006-07-03 at 23:50 -0700, Andrew Morton wrote:
> On Mon, 03 Jul 2006 13:46:57 -0700
> Randy Dunlap <randy.dunlap@oracle.com> wrote:
> 
> > 
> > lkml discussion: http://thread.gmane.org/gmane.linux.kernel/385438/focus=385478
> > 
> > Already in -mm?
> > 
> > From: Dipankar Sarma <dipankar@in.ibm.com>
> > 
> > Ubuntu patch location:
> > http://www.kernel.org/git/?p=linux/kernel/git/bcollins/ubuntu-dapper.git;a=commitdiff;h=5ce2ed3a63172c6ce0b97069e449960c2d538623
> > 
> 
> hm.  This is actually a reversion of
> 529bf6be5c04f2e869d07bfdb122e9fd98ade714, so it presumably reintroduces the
> problem discussed in that lkml thread.
> 
> Ben, what's the story here?

This was pulled in to try to fix some problems we were seeing on
sparc64. However, this backported patch broke other architectures (I
think x86_64 wouldn't even boot), so was reverted.

I can't remember any more details than that.

-- 
Ubuntu     - http://www.ubuntu.com/
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
SwissDisk  - http://www.swissdisk.com/


      reply	other threads:[~2006-07-04 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 20:46 [Ubuntu PATCH] fix VFS nr_files accounting Randy Dunlap
2006-07-04  6:50 ` Andrew Morton
2006-07-04 15:06   ` Ben Collins [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=1152025616.23756.93.camel@grayson \
    --to=bcollins@ubuntu.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=viro@zeniv.linux.org.uk \
    /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