linux-kernel - Re: nfs oom on 3.15

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 5 May 2014 07:08:12 -0400
From:	Jeff Layton <jlayton@...chiereds.net>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Marc Dietrich <marvin24@....de>, linux-kernel@...r.kernel.org,
	linux-nfs@...r.kernel.org,
	Trond Myklebust <trond.myklebust@...marydata.com>,
	Mel Gorman <mgorman@...e.de>
Subject: Re: nfs oom on 3.15

On Mon, 5 May 2014 02:42:35 -0700 (PDT)
David Rientjes <rientjes@...gle.com> wrote:

> On Mon, 5 May 2014, Marc Dietrich wrote:
> 
> > Hi,
> > 
> > this is spaming my log quite a bit.
> > 
> > Any idea?
> > 
> 
> I think rpc_malloc() really wants to be __GFP_NOWARN so that the warnings 
> are suppressed, doing order-1 allocations with GFP_NOWAIT is never 
> guaranteed to succeed and will have difficulty if memory is fragmented.  


Yes. We made a similar fix to xprt_alloc_slot a while back. The RPC
engine has a mechanism to handle retrying these allocations, so this
warning isn't particularly helpful.

-- 
Jeff Layton <jlayton@...chiereds.net>
--
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/