linux-kernel - Re: mount.nfs: cannot allocate memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120612231601.GA30715@redhat.com>
Date:	Tue, 12 Jun 2012 19:16:01 -0400
From:	Dave Jones <davej@...hat.com>
To:	Mark Lord <kernel@...savvy.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	"J. Bruce Fields" <bfields@...ldses.org>,
	Trond Myklebust <Trond.Myklebust@...app.com>
Subject: Re: mount.nfs: cannot allocate memory

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/