From: Michal Hocko <mhocko@kernel.org>
To: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
djwong@kernel.org, Theodore Ts'o <tytso@mit.edu>,
Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.cz>,
Jan Kara <jack@suse.cz>,
ceph-devel@vger.kernel.org, cluster-devel@redhat.com,
linux-nfs@vger.kernel.org, logfs@logfs.org,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-mtd@lists.infradead.org,
reiserfs-devel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
linux-f2fs-devel@lists.sourceforge.net,
linux-afs@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>
Subject: [DEBUG PATCH 0/2] debug explicit GFP_NO{FS,IO} usage from the scope context
Date: Fri, 6 Jan 2017 15:18:43 +0100 [thread overview]
Message-ID: <20170106141845.24362-1-mhocko@kernel.org> (raw)
In-Reply-To: <20170106141107.23953-1-mhocko@kernel.org>
These two patches should help to identify explicit GFP_NO{FS,IO} usage
from withing a scope context and reduce such a usage as a result. Such
a usage can be changed to the full GFP_KERNEL because all the calls
from within the NO{FS,IO} scope will drop the __GFP_FS resp. __GFP_IO
automatically and if the function is called outside of the scope then
we do not need to restrict it to NOFS/NOIO as long as all the reclaim
recursion unsafe contexts are marked properly. This means that each such
a reported allocation site has to be checked before converted.
The debugging has to be enabled explicitly by a kernel command line
parameter and then it reports the stack trace of the allocation and
also the function which has started the current scope.
These two patches are _not_ intended to be merged and they are only
aimed at debugging.
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [DEBUG PATCH 0/2] debug explicit GFP_NO{FS, IO} usage from the scope context
Date: Fri, 6 Jan 2017 15:18:43 +0100 [thread overview]
Message-ID: <20170106141845.24362-1-mhocko@kernel.org> (raw)
In-Reply-To: <20170106141107.23953-1-mhocko@kernel.org>
These two patches should help to identify explicit GFP_NO{FS,IO} usage
from withing a scope context and reduce such a usage as a result. Such
a usage can be changed to the full GFP_KERNEL because all the calls
from within the NO{FS,IO} scope will drop the __GFP_FS resp. __GFP_IO
automatically and if the function is called outside of the scope then
we do not need to restrict it to NOFS/NOIO as long as all the reclaim
recursion unsafe contexts are marked properly. This means that each such
a reported allocation site has to be checked before converted.
The debugging has to be enabled explicitly by a kernel command line
parameter and then it reports the stack trace of the allocation and
also the function which has started the current scope.
These two patches are _not_ intended to be merged and they are only
aimed at debugging.
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: <linux-mm@kvack.org>, <linux-fsdevel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
djwong@kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.cz>,
Jan Kara <jack@suse.cz>,
ceph-devel@vger.kernel.org, cluster-devel@redhat.com,
linux-nfs@vger.kernel.org, logfs@logfs.org,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-mtd@lists.infradead.org,
reiserfs-devel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
linux-f2fs-devel@lists.sourceforge.net,
linux-afs@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>
Subject: [DEBUG PATCH 0/2] debug explicit GFP_NO{FS,IO} usage from the scope context
Date: Fri, 6 Jan 2017 15:18:43 +0100 [thread overview]
Message-ID: <20170106141845.24362-1-mhocko@kernel.org> (raw)
In-Reply-To: <20170106141107.23953-1-mhocko@kernel.org>
These two patches should help to identify explicit GFP_NO{FS,IO} usage
from withing a scope context and reduce such a usage as a result. Such
a usage can be changed to the full GFP_KERNEL because all the calls
from within the NO{FS,IO} scope will drop the __GFP_FS resp. __GFP_IO
automatically and if the function is called outside of the scope then
we do not need to restrict it to NOFS/NOIO as long as all the reclaim
recursion unsafe contexts are marked properly. This means that each such
a reported allocation site has to be checked before converted.
The debugging has to be enabled explicitly by a kernel command line
parameter and then it reports the stack trace of the allocation and
also the function which has started the current scope.
These two patches are _not_ intended to be merged and they are only
aimed at debugging.
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: <linux-mm@kvack.org>, <linux-fsdevel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
djwong@kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.cz>,
Jan Kara <jack@suse.cz>,
ceph-devel@vger.kernel.org, cluster-devel@redhat.com,
linux-nfs@vger.kernel.org, logfs@logfs.org,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-mtd@lists.infradead.org,
reiserfs-devel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
linux-f2fs-devel@lists.sourceforge.net,
linux-afs@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>
Subject: [DEBUG PATCH 0/2] debug explicit GFP_NO{FS,IO} usage from the scope context
Date: Fri, 6 Jan 2017 15:18:43 +0100 [thread overview]
Message-ID: <20170106141845.24362-1-mhocko@kernel.org> (raw)
In-Reply-To: <20170106141107.23953-1-mhocko@kernel.org>
These two patches should help to identify explicit GFP_NO{FS,IO} usage
from withing a scope context and reduce such a usage as a result. Such
a usage can be changed to the full GFP_KERNEL because all the calls
from within the NO{FS,IO} scope will drop the __GFP_FS resp. __GFP_IO
automatically and if the function is called outside of the scope then
we do not need to restrict it to NOFS/NOIO as long as all the reclaim
recursion unsafe contexts are marked properly. This means that each such
a reported allocation site has to be checked before converted.
The debugging has to be enabled explicitly by a kernel command line
parameter and then it reports the stack trace of the allocation and
also the function which has started the current scope.
These two patches are _not_ intended to be merged and they are only
aimed at debugging.
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: <linux-mm@kvack.org>, <linux-fsdevel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
djwong@kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.cz>,
Jan Kara <jack@suse.cz>,
ceph-devel@vger.kernel.org, cluster-devel@redhat.com,
linux-nfs@vger.kernel.org, logfs@logfs.org,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-mtd@lists.infradead.org,
reiserfs-devel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
linux-f2fs-devel@lists.sourceforge.net,
linux-afs@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>
Subject: [DEBUG PATCH 0/2] debug explicit GFP_NO{FS, IO} usage from the scope context
Date: Fri, 6 Jan 2017 15:18:43 +0100 [thread overview]
Message-ID: <20170106141845.24362-1-mhocko@kernel.org> (raw)
In-Reply-To: <20170106141107.23953-1-mhocko@kernel.org>
These two patches should help to identify explicit GFP_NO{FS,IO} usage
from withing a scope context and reduce such a usage as a result. Such
a usage can be changed to the full GFP_KERNEL because all the calls
from within the NO{FS,IO} scope will drop the __GFP_FS resp. __GFP_IO
automatically and if the function is called outside of the scope then
we do not need to restrict it to NOFS/NOIO as long as all the reclaim
recursion unsafe contexts are marked properly. This means that each such
a reported allocation site has to be checked before converted.
The debugging has to be enabled explicitly by a kernel command line
parameter and then it reports the stack trace of the allocation and
also the function which has started the current scope.
These two patches are _not_ intended to be merged and they are only
aimed at debugging.
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
djwong@kernel.org, Theodore Ts'o <tytso@mit.edu>,
Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.cz>,
Jan Kara <jack@suse.cz>,
ceph-devel@vger.kernel.org, cluster-devel@redhat.com,
linux-nfs@vger.kernel.org, logfs@logfs.org,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-mtd@lists.infradead.org,
reiserfs-devel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
linux-f2fs-devel@lists.sourceforge.net,
linux-afs@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>
Subject: [DEBUG PATCH 0/2] debug explicit GFP_NO{FS,IO} usage from the scope context
Date: Fri, 6 Jan 2017 15:18:43 +0100 [thread overview]
Message-ID: <20170106141845.24362-1-mhocko@kernel.org> (raw)
In-Reply-To: <20170106141107.23953-1-mhocko@kernel.org>
These two patches should help to identify explicit GFP_NO{FS,IO} usage
from withing a scope context and reduce such a usage as a result. Such
a usage can be changed to the full GFP_KERNEL because all the calls
from within the NO{FS,IO} scope will drop the __GFP_FS resp. __GFP_IO
automatically and if the function is called outside of the scope then
we do not need to restrict it to NOFS/NOIO as long as all the reclaim
recursion unsafe contexts are marked properly. This means that each such
a reported allocation site has to be checked before converted.
The debugging has to be enabled explicitly by a kernel command line
parameter and then it reports the stack trace of the allocation and
also the function which has started the current scope.
These two patches are _not_ intended to be merged and they are only
aimed at debugging.
next prev parent reply other threads:[~2017-01-06 14:18 UTC|newest]
Thread overview: 172+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 14:10 [PATCH 0/8 v3] scope GFP_NOFS api Michal Hocko
2017-01-06 14:10 ` Michal Hocko
2017-01-06 14:10 ` Michal Hocko
2017-01-06 14:10 ` Michal Hocko
2017-01-06 14:10 ` [Cluster-devel] " Michal Hocko
2017-01-06 14:11 ` [PATCH 1/8] lockdep: allow to disable reclaim lockup detection Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` [Cluster-devel] " Michal Hocko
2017-01-09 12:56 ` Vlastimil Babka
2017-01-09 12:56 ` Vlastimil Babka
2017-01-09 12:56 ` [Cluster-devel] " Vlastimil Babka
2017-01-06 14:11 ` [PATCH 2/8] xfs: abstract PF_FSTRANS to PF_MEMALLOC_NOFS Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` [Cluster-devel] " Michal Hocko
2017-01-09 12:59 ` Vlastimil Babka
2017-01-09 12:59 ` Vlastimil Babka
2017-01-09 12:59 ` [Cluster-devel] " Vlastimil Babka
2017-01-09 14:29 ` Michal Hocko
2017-01-09 14:29 ` Michal Hocko
2017-01-09 14:29 ` [Cluster-devel] " Michal Hocko
2017-01-09 20:58 ` Darrick J. Wong
2017-01-09 20:58 ` Darrick J. Wong
2017-01-09 20:58 ` [Cluster-devel] " Darrick J. Wong
2017-01-06 14:11 ` [PATCH 3/8] mm: introduce memalloc_nofs_{save,restore} API Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` [Cluster-devel] [PATCH 3/8] mm: introduce memalloc_nofs_{save, restore} API Michal Hocko
2017-01-09 13:04 ` [PATCH 3/8] mm: introduce memalloc_nofs_{save,restore} API Vlastimil Babka
2017-01-09 13:04 ` Vlastimil Babka
2017-01-09 13:04 ` [Cluster-devel] [PATCH 3/8] mm: introduce memalloc_nofs_{save, restore} API Vlastimil Babka
2017-01-09 13:42 ` [PATCH 3/8] mm: introduce memalloc_nofs_{save,restore} API Michal Hocko
2017-01-09 13:42 ` Michal Hocko
2017-01-09 13:42 ` [Cluster-devel] [PATCH 3/8] mm: introduce memalloc_nofs_{save, restore} API Michal Hocko
2017-01-09 13:59 ` [PATCH 3/8] mm: introduce memalloc_nofs_{save,restore} API Michal Hocko
2017-01-09 13:59 ` Michal Hocko
2017-01-09 13:59 ` [Cluster-devel] [PATCH 3/8] mm: introduce memalloc_nofs_{save, restore} API Michal Hocko
2017-01-09 14:04 ` [PATCH 3/8] mm: introduce memalloc_nofs_{save,restore} API Vlastimil Babka
2017-01-09 14:04 ` Vlastimil Babka
2017-01-09 14:04 ` [Cluster-devel] [PATCH 3/8] mm: introduce memalloc_nofs_{save, restore} API Vlastimil Babka
2017-01-06 14:11 ` [PATCH 4/8] xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio* Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` [PATCH 4/8] xfs: use memalloc_nofs_{save, restore} " Michal Hocko
2017-01-06 14:11 ` [PATCH 4/8] xfs: use memalloc_nofs_{save,restore} " Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` [Cluster-devel] [PATCH 4/8] xfs: use memalloc_nofs_{save, restore} " Michal Hocko
2017-01-09 14:08 ` [PATCH 4/8] xfs: use memalloc_nofs_{save,restore} " Vlastimil Babka
2017-01-09 14:08 ` Vlastimil Babka
2017-01-09 14:08 ` [Cluster-devel] [PATCH 4/8] xfs: use memalloc_nofs_{save, restore} " Vlastimil Babka
2017-01-09 14:25 ` [PATCH 4/8] xfs: use memalloc_nofs_{save,restore} " Michal Hocko
2017-01-09 14:25 ` Michal Hocko
2017-01-09 14:25 ` [Cluster-devel] [PATCH 4/8] xfs: use memalloc_nofs_{save, restore} " Michal Hocko
2017-01-09 15:56 ` [PATCH 4/8] xfs: use memalloc_nofs_{save,restore} " Brian Foster
2017-01-09 15:56 ` Brian Foster
2017-01-09 15:56 ` [Cluster-devel] [PATCH 4/8] xfs: use memalloc_nofs_{save, restore} " Brian Foster
2017-01-09 20:59 ` [PATCH 4/8] xfs: use memalloc_nofs_{save,restore} " Darrick J. Wong
2017-01-09 20:59 ` Darrick J. Wong
2017-01-09 20:59 ` [Cluster-devel] [PATCH 4/8] xfs: use memalloc_nofs_{save, restore} " Darrick J. Wong
2017-01-06 14:11 ` [PATCH 5/8] jbd2: mark the transaction context with the scope GFP_NOFS context Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` [Cluster-devel] " Michal Hocko
2017-01-06 14:11 ` [PATCH 6/8] jbd2: make the whole kjournald2 kthread NOFS safe Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` [Cluster-devel] " Michal Hocko
2017-01-06 14:11 ` [PATCH 7/8] Revert "ext4: avoid deadlocks in the writeback path by using sb_getblk_gfp" Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` [Cluster-devel] " Michal Hocko
2017-01-17 3:01 ` Theodore Ts'o
2017-01-17 3:01 ` Theodore Ts'o
2017-01-17 3:01 ` [Cluster-devel] " Theodore Ts'o
2017-01-17 7:54 ` Michal Hocko
2017-01-17 7:54 ` Michal Hocko
2017-01-17 7:54 ` [Cluster-devel] " Michal Hocko
2017-03-06 11:59 ` Michal Hocko
2017-03-06 11:59 ` Michal Hocko
2017-03-06 11:59 ` [Cluster-devel] " Michal Hocko
2017-01-06 14:11 ` [PATCH 8/8] Revert "ext4: fix wrong gfp type under transaction" Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` Michal Hocko
2017-01-06 14:11 ` [Cluster-devel] " Michal Hocko
2017-01-17 2:56 ` Theodore Ts'o
2017-01-17 2:56 ` Theodore Ts'o
2017-01-17 2:56 ` [Cluster-devel] " Theodore Ts'o
2017-01-17 8:24 ` Michal Hocko
2017-01-17 8:24 ` Michal Hocko
2017-01-17 8:24 ` [Cluster-devel] " Michal Hocko
[not found] ` <20170117082425.GD19699-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-01-17 15:18 ` Michal Hocko
2017-01-17 15:18 ` Michal Hocko
2017-01-17 15:18 ` Michal Hocko
2017-01-17 15:18 ` [Cluster-devel] " Michal Hocko
2017-01-17 15:59 ` Theodore Ts'o
2017-01-17 15:59 ` Theodore Ts'o
2017-01-17 15:59 ` [Cluster-devel] " Theodore Ts'o
2017-01-17 16:16 ` Michal Hocko
2017-01-17 16:16 ` Michal Hocko
2017-01-17 16:16 ` [Cluster-devel] " Michal Hocko
2017-01-17 17:29 ` Jan Kara
2017-01-17 17:29 ` Jan Kara
2017-01-17 17:29 ` [Cluster-devel] " Jan Kara
2017-01-19 8:39 ` Michal Hocko
2017-01-19 8:39 ` Michal Hocko
2017-01-19 8:39 ` [Cluster-devel] " Michal Hocko
2017-01-19 9:22 ` Jan Kara
2017-01-19 9:22 ` Jan Kara
2017-01-19 9:22 ` [Cluster-devel] " Jan Kara
2017-01-19 9:44 ` Michal Hocko
2017-01-19 9:44 ` Michal Hocko
2017-01-19 9:44 ` [Cluster-devel] " Michal Hocko
2017-01-26 7:44 ` Michal Hocko
2017-01-26 7:44 ` Michal Hocko
2017-01-26 7:44 ` [Cluster-devel] " Michal Hocko
[not found] ` <20170126074455.GC8456-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-01-27 6:13 ` Theodore Ts'o
2017-01-27 6:13 ` Theodore Ts'o
2017-01-27 6:13 ` Theodore Ts'o
2017-01-27 6:13 ` [Cluster-devel] " Theodore Ts'o
2017-01-27 9:37 ` Michal Hocko
2017-01-27 9:37 ` Michal Hocko
2017-01-27 9:37 ` [Cluster-devel] " Michal Hocko
2017-01-27 16:40 ` Theodore Ts'o
2017-01-27 16:40 ` Theodore Ts'o
2017-01-27 16:40 ` [Cluster-devel] " Theodore Ts'o
2017-01-28 7:32 ` Christoph Hellwig
2017-01-28 7:32 ` Christoph Hellwig
2017-01-28 7:32 ` Christoph Hellwig
2017-01-28 8:17 ` David Lang
2017-01-28 8:17 ` David Lang
2017-01-28 8:17 ` David Lang
2017-01-30 8:12 ` Michal Hocko
2017-01-30 8:12 ` Michal Hocko
2017-01-30 8:12 ` [Cluster-devel] " Michal Hocko
2017-02-03 15:32 ` Michal Hocko
2017-02-03 15:32 ` Michal Hocko
2017-02-03 15:32 ` [Cluster-devel] " Michal Hocko
[not found] ` <20170117155916.dcizr65bwa6behe7-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2017-01-17 21:04 ` Andreas Dilger
2017-01-17 21:04 ` Andreas Dilger
2017-01-17 21:04 ` [Cluster-devel] " Andreas Dilger
2017-01-18 8:29 ` Michal Hocko
2017-01-18 8:29 ` Michal Hocko
2017-01-18 8:29 ` [Cluster-devel] " Michal Hocko
2017-01-06 14:18 ` Michal Hocko [this message]
2017-01-06 14:18 ` [DEBUG PATCH 0/2] debug explicit GFP_NO{FS,IO} usage from the scope context Michal Hocko
2017-01-06 14:18 ` [DEBUG PATCH 0/2] debug explicit GFP_NO{FS, IO} " Michal Hocko
2017-01-06 14:18 ` [DEBUG PATCH 0/2] debug explicit GFP_NO{FS,IO} " Michal Hocko
2017-01-06 14:18 ` Michal Hocko
2017-01-06 14:18 ` [Cluster-devel] [DEBUG PATCH 0/2] debug explicit GFP_NO{FS, IO} " Michal Hocko
2017-01-06 14:18 ` [DEBUG PATCH 1/2] mm, debug: report when GFP_NO{FS,IO} is used explicitly from memalloc_no{fs,io}_{save,restore} context Michal Hocko
2017-01-06 14:18 ` Michal Hocko
2017-01-06 14:18 ` [DEBUG PATCH 1/2] mm, debug: report when GFP_NO{FS, IO} is used explicitly from memalloc_no{fs, io}_{save, restore} context Michal Hocko
2017-01-06 14:18 ` [DEBUG PATCH 1/2] mm, debug: report when GFP_NO{FS,IO} is used explicitly from memalloc_no{fs,io}_{save,restore} context Michal Hocko
2017-01-06 14:18 ` Michal Hocko
2017-01-06 14:18 ` [Cluster-devel] [DEBUG PATCH 1/2] mm, debug: report when GFP_NO{FS, IO} is used explicitly from memalloc_no{fs, io}_{save, restore} context Michal Hocko
2017-01-06 14:18 ` [DEBUG PATCH 2/2] silent warnings which we cannot do anything about Michal Hocko
2017-01-06 14:18 ` Michal Hocko
2017-01-06 14:18 ` Michal Hocko
2017-01-06 14:18 ` Michal Hocko
2017-01-06 14:18 ` [Cluster-devel] " Michal Hocko
-- strict thread matches above, loose matches on Subject: below --
2016-12-15 14:07 [PATCH 0/9 v2] scope GFP_NOFS api Michal Hocko
2016-12-16 12:46 ` [DEBUG PATCH 0/2] debug explicit GFP_NO{FS,IO} usage from the scope context Michal Hocko
2016-12-16 12:46 ` Michal Hocko
2016-12-16 12:46 ` [DEBUG PATCH 0/2] debug explicit GFP_NO{FS, IO} " Michal Hocko
2016-12-16 12:46 ` [DEBUG PATCH 0/2] debug explicit GFP_NO{FS,IO} " Michal Hocko
2016-12-16 12:46 ` Michal Hocko
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=20170106141845.24362-1-mhocko@kernel.org \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ceph-devel@vger.kernel.org \
--cc=clm@fb.com \
--cc=cluster-devel@redhat.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.cz \
--cc=jack@suse.cz \
--cc=linux-afs@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=linux-xfs@vger.kernel.org \
--cc=logfs@logfs.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.