From: Theodore Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-nvdimm@lists.01.org,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH 2/2] ext4: Fix ENOSPC handling in DAX page fault handler
Date: Sun, 7 Jan 2018 16:51:34 -0500 [thread overview]
Message-ID: <20180107215134.GF17380@thunk.org> (raw)
In-Reply-To: <20180103100844.12787-3-jack@suse.cz>
On Wed, Jan 03, 2018 at 11:08:44AM +0100, Jan Kara wrote:
> When allocation of underlying block for a page fault fails, we fail the
> fault with SIGBUS. However we may well hit ENOSPC just due to lots of
> free blocks being held by the running / committing transaction. So
> propagate the error from ext4_iomap_begin() and implement do standard
> allocation retry loop in ext4_dax_huge_fault().
>
> Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> Signed-off-by: Jan Kara <jack@suse.cz>
Applied, thanks.
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: Theodore Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-nvdimm@lists.01.org
Subject: Re: [PATCH 2/2] ext4: Fix ENOSPC handling in DAX page fault handler
Date: Sun, 7 Jan 2018 16:51:34 -0500 [thread overview]
Message-ID: <20180107215134.GF17380@thunk.org> (raw)
In-Reply-To: <20180103100844.12787-3-jack@suse.cz>
On Wed, Jan 03, 2018 at 11:08:44AM +0100, Jan Kara wrote:
> When allocation of underlying block for a page fault fails, we fail the
> fault with SIGBUS. However we may well hit ENOSPC just due to lots of
> free blocks being held by the running / committing transaction. So
> propagate the error from ext4_iomap_begin() and implement do standard
> allocation retry loop in ext4_dax_huge_fault().
>
> Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> Signed-off-by: Jan Kara <jack@suse.cz>
Applied, thanks.
- Ted
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-01-07 21:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 10:08 [PATCH 0/2 v3] ext4: Fix ENOSPC handling for DAX faults Jan Kara
2018-01-03 10:08 ` Jan Kara
2018-01-03 10:08 ` Jan Kara
[not found] ` <20180103100844.12787-1-jack-AlSwsSmVLrQ@public.gmane.org>
2018-01-03 10:08 ` [PATCH 1/2] dax: Pass detailed error code from dax_iomap_fault() Jan Kara
2018-01-03 10:08 ` Jan Kara
2018-01-03 10:08 ` Jan Kara
2018-01-07 21:51 ` Theodore Ts'o
2018-01-07 21:51 ` Theodore Ts'o
2018-01-03 10:08 ` [PATCH 2/2] ext4: Fix ENOSPC handling in DAX page fault handler Jan Kara
2018-01-03 10:08 ` Jan Kara
2018-01-03 10:08 ` Jan Kara
2018-01-07 21:51 ` Theodore Ts'o [this message]
2018-01-07 21:51 ` Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2017-12-21 16:30 [PATCH 0/2 v2] ext4: Fix ENOSPC handling for DAX faults Jan Kara
[not found] ` <20171221163055.3943-1-jack-AlSwsSmVLrQ@public.gmane.org>
2017-12-21 16:30 ` [PATCH 2/2] ext4: Fix ENOSPC handling in DAX page fault handler Jan Kara
2017-12-21 16:30 ` Jan Kara
2017-12-21 16:30 ` Jan Kara
[not found] ` <20171221163055.3943-3-jack-AlSwsSmVLrQ@public.gmane.org>
2017-12-21 17:17 ` Ross Zwisler
2017-12-21 17:17 ` Ross Zwisler
2017-12-21 17:17 ` Ross Zwisler
2017-12-13 9:13 [PATCH 0/2] ext4: Fix ENOSPC handling for DAX faults Jan Kara
[not found] ` <20171213091352.23448-1-jack-AlSwsSmVLrQ@public.gmane.org>
2017-12-13 9:13 ` [PATCH 2/2] ext4: Fix ENOSPC handling in DAX page fault handler Jan Kara
2017-12-13 9:13 ` Jan Kara
2017-12-13 9:13 ` Jan Kara
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=20180107215134.GF17380@thunk.org \
--to=tytso@mit.edu \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=ross.zwisler@linux.intel.com \
/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.