On Wed, Aug 05, 2015 at 11:51:23AM +0200, mho...@kernel.org wrote:
> From: Michal Hocko
...
> Fix this by reintroducing the no-fail behavior of this allocation path
> with the explicit __GFP_NOFAIL.
>
> Signed-off-by: Michal Hocko
Reviewed-by: David Sterba
--
To unsubscribe from this list:
From: Michal Hocko
Btrfs relies on GFP_NOFS allocation when commiting the transaction but
since "mm: page_alloc: do not lock up GFP_NOFS allocations upon OOM"
those allocations are allowed to fail which can lead to a pre-mature
transaction abort:
[ 55.328093] Call Trace:
[ 55.328890] []
From: Michal Hocko mho...@suse.com
Btrfs relies on GFP_NOFS allocation when commiting the transaction but
since mm: page_alloc: do not lock up GFP_NOFS allocations upon OOM
those allocations are allowed to fail which can lead to a pre-mature
transaction abort:
[ 55.328093] Call Trace:
[
On Wed, Aug 05, 2015 at 11:51:23AM +0200, mho...@kernel.org wrote:
From: Michal Hocko mho...@suse.com
...
Fix this by reintroducing the no-fail behavior of this allocation path
with the explicit __GFP_NOFAIL.
Signed-off-by: Michal Hocko mho...@suse.com
Reviewed-by: David Sterba
4 matches
Mail list logo