From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ivan Shapovalov <intelfx100@gmail.com>, reiserfs-devel@vger.kernel.org
Subject: Re: [PATCHv2 3/3] reiser4: mark pages created during tail2extent conversion as dirty.
Date: Mon, 9 Nov 2015 13:18:56 +0100 [thread overview]
Message-ID: <56408F30.3060404@gmail.com> (raw)
In-Reply-To: <1445727740-12361-4-git-send-email-intelfx100@gmail.com>
On 10/25/2015 01:02 AM, Ivan Shapovalov wrote:
> This is responsible for an oops in v4.2 in
> write_jnodes_to_disk_extent() -> set_page_writeback().
>
> The pages needs to be marked dirty before marked writeback.
>
> From a similar problem in f2fs:
> "The cgroup attaches inode->i_wb via mark_inode_dirty and when
> set_page_writeback is called, __inc_wb_stat() updates i_wb's stat.
>
> So, we need to explicitly call set_page_dirty->__mark_inode_dirty in
> prior to any writebacking pages."
>
> Signed-off-by: Ivan Shapovalov <intelfx100@gmail.com>
> ---
> fs/reiser4/plugin/file/tail_conversion.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/reiser4/plugin/file/tail_conversion.c b/fs/reiser4/plugin/file/tail_conversion.c
> index 7542c03..c856b73 100644
> --- a/fs/reiser4/plugin/file/tail_conversion.c
> +++ b/fs/reiser4/plugin/file/tail_conversion.c
> @@ -175,6 +175,7 @@ static int replace(struct inode *inode, struct page **pages, unsigned nr_pages,
> i_mapping));
> if (result)
> break;
> + set_page_dirty_notag(pages[i]);
So, at this point the page is dirty but not uptodate.
I am confused with this. Why not to set the page
uptodate right before setting it dirty? At this point
everything has been copied already, so the page is
in fact uptodate. Could you please try this?
Thanks,
Edward.
> unlock_page(pages[i]);
> result = find_or_create_extent(pages[i]);
> if (result) {
next prev parent reply other threads:[~2015-11-09 12:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 23:02 [PATCHv2 0/3] reiser4: another batch of fixes for 4.2 Ivan Shapovalov
2015-10-24 23:02 ` [PATCHv2 1/3] reiser4: remove last traces of JNODE_NEW in the debugging code Ivan Shapovalov
2015-11-09 11:49 ` Edward Shishkin
2015-10-24 23:02 ` [PATCHv2 2/3] reiser4: call account_page_redirty() on re-dirtying pages before giving them to entd Ivan Shapovalov
2015-11-09 11:50 ` Edward Shishkin
2015-10-24 23:02 ` [PATCHv2 3/3] reiser4: mark pages created during tail2extent conversion as dirty Ivan Shapovalov
2015-11-09 12:18 ` Edward Shishkin [this message]
2015-11-11 10:30 ` Edward Shishkin
2015-11-12 10:00 ` Edward Shishkin
2015-11-12 11:31 ` Ivan Shapovalov
2015-11-12 15:50 ` Edward Shishkin
2015-12-04 5:09 ` [PATCHv2 0/3] reiser4: another batch of fixes for 4.2 doiggl
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=56408F30.3060404@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=intelfx100@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
/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.