From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f181.google.com (mail-ig0-f181.google.com [209.85.213.181]) by kanga.kvack.org (Postfix) with ESMTP id 3FF7F6B0035 for ; Wed, 3 Sep 2014 22:18:54 -0400 (EDT) Received: by mail-ig0-f181.google.com with SMTP id h15so319360igd.2 for ; Wed, 03 Sep 2014 19:18:54 -0700 (PDT) Received: from userp1040.oracle.com (userp1040.oracle.com. [156.151.31.81]) by mx.google.com with ESMTPS id cr6si4231248igb.30.2014.09.03.19.18.53 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 03 Sep 2014 19:18:53 -0700 (PDT) Message-ID: <5407CBEA.9090909@oracle.com> Date: Thu, 04 Sep 2014 10:18:18 +0800 From: Junxiao Bi MIME-Version: 1.0 Subject: Re: [PATCH] mm: clear __GFP_FS when PF_MEMALLOC_NOIO is set References: <1409723694-16047-1-git-send-email-junxiao.bi@oracle.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Trond Myklebust Cc: david@fromorbit.com, akpm@linux-foundation.org, xuejiufei@huawei.com, ming.lei@canonical.com, Linux Kernel mailing list , linux-mm@kvack.org, Devel FS Linux On 09/03/2014 08:20 PM, Trond Myklebust wrote: > On Wed, Sep 3, 2014 at 1:54 AM, Junxiao Bi wrote: >> commit 21caf2fc1931 ("mm: teach mm by current context info to not do I/O during memory allocation") >> introduces PF_MEMALLOC_NOIO flag to avoid doing I/O inside memory allocation, __GFP_IO is cleared >> when this flag is set, but __GFP_FS implies __GFP_IO, it should also be cleared. Or it may still >> run into I/O, like in superblock shrinker. >> >> Signed-off-by: Junxiao Bi >> Cc: joyce.xue >> Cc: Ming Lei >> --- >> include/linux/sched.h | 6 ++++-- >> 1 file changed, 4 insertions(+), 2 deletions(-) >> >> diff --git a/include/linux/sched.h b/include/linux/sched.h >> index 5c2c885..2fb2c47 100644 >> --- a/include/linux/sched.h >> +++ b/include/linux/sched.h >> @@ -1936,11 +1936,13 @@ extern void thread_group_cputime_adjusted(struct task_struct *p, cputime_t *ut, >> #define tsk_used_math(p) ((p)->flags & PF_USED_MATH) >> #define used_math() tsk_used_math(current) >> >> -/* __GFP_IO isn't allowed if PF_MEMALLOC_NOIO is set in current->flags */ >> +/* __GFP_IO isn't allowed if PF_MEMALLOC_NOIO is set in current->flags >> + * __GFP_FS is also cleared as it implies __GFP_IO. >> + */ >> static inline gfp_t memalloc_noio_flags(gfp_t flags) >> { >> if (unlikely(current->flags & PF_MEMALLOC_NOIO)) >> - flags &= ~__GFP_IO; >> + flags &= ~(__GFP_IO | __GFP_FS); >> return flags; >> } >> > > Shouldn't this be a stable fix? If it is needed, then it will affect > all kernels that define PF_MEMALLOC_NOIO. Yes, should be. An ocfs2 deadlock bug related to this. Thanks, Junxiao. > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org