From: Dave Jones <davej@redhat.com>
To: Mark Lord <kernel@teksavvy.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: mount.nfs: cannot allocate memory
Date: Tue, 12 Jun 2012 19:16:01 -0400 [thread overview]
Message-ID: <20120612231601.GA30715@redhat.com> (raw)
In-Reply-To: <4FD7C7C6.9030204@teksavvy.com>
On Tue, Jun 12, 2012 at 06:50:46PM -0400, Mark Lord wrote:
> Looks like an old bug, perhaps:
> https://bugzilla.redhat.com/show_bug.cgi?id=593035
> https://bugzilla.redhat.com/show_bug.cgi?id=728003
>
> I wonder what the underlying cause is?
> And I also wonder if the NFS code should be more clever
> about handing order-4 allocation failures.
>From memory, I don't think we've seen new reports of this since we switched to (now dead)
CONFIG_NFS_USE_NEW_IDMAPPER=y.
Dave
next prev parent reply other threads:[~2012-06-12 23:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 22:44 mount.nfs: cannot allocate memory Mark Lord
2012-06-12 22:50 ` Mark Lord
2012-06-12 22:58 ` Mark Lord
2012-06-12 23:08 ` Mark Lord
2012-06-12 23:28 ` Myklebust, Trond
2012-06-12 23:46 ` Mark Lord
2012-06-12 23:16 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-03 9:27 Paweł Sikora
2013-01-03 14:42 ` Steve Dickson
2013-01-04 5:16 ` Paweł Sikora
2013-01-04 6:03 ` fanchaoting
2013-01-04 15:20 ` Paweł Sikora
2013-01-05 10:08 ` Paweł Sikora
2013-01-07 14:47 ` Steve Dickson
2013-01-09 17:44 ` Paweł Sikora
2013-01-16 19:03 ` Paweł Sikora
2013-01-16 19:39 ` J. Bruce Fields
2013-01-16 20:07 ` Paweł Sikora
2013-01-16 20:15 ` J. Bruce Fields
2013-01-16 21:18 ` Paweł Sikora
2013-01-17 13:49 ` J. Bruce Fields
2013-01-17 14:59 ` Paweł Sikora
2013-01-16 20:14 ` Myklebust, Trond
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=20120612231601.GA30715@redhat.com \
--to=davej@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=kernel@teksavvy.com \
--cc=linux-kernel@vger.kernel.org \
/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.