[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160427203010.GD22544@dhcp22.suse.cz>
Date: Wed, 27 Apr 2016 22:30:10 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Dave Chinner <david@...morbit.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, Theodore Ts'o <tytso@....edu>,
Chris Mason <clm@...com>, Jan Kara <jack@...e.cz>,
ceph-devel@...r.kernel.org, cluster-devel@...hat.com,
linux-nfs@...r.kernel.org, logfs@...fs.org, xfs@....sgi.com,
linux-ext4@...r.kernel.org, linux-btrfs@...r.kernel.org,
linux-mtd@...ts.infradead.org, reiserfs-devel@...r.kernel.org,
linux-ntfs-dev@...ts.sourceforge.net,
linux-f2fs-devel@...ts.sourceforge.net,
linux-afs@...ts.infradead.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1.2/2] mm: introduce memalloc_nofs_{save,restore} API
On Wed 27-04-16 22:09:27, Michal Hocko wrote:
[...]
> [ 53.993480] [<ffffffff810945e3>] mark_held_locks+0x5e/0x74
> [ 53.993480] [<ffffffff8109722c>] lockdep_trace_alloc+0xb2/0xb5
> [ 53.993480] [<ffffffff81174e56>] kmem_cache_alloc+0x36/0x2b0
Scratch that. I got it. It is the lockdep annotation which I got wrong
with my patch. I thought this was done much later in the slow path.
My head is burnt so I will get back to it tomorrow. The patch 1.1 should
be OK to go for XFS though because it doesn't really introduce anything
new.
Sorry about the noise!
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists