From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ivan Shapovalov <intelfx100@gmail.com>, reiserfs-devel@vger.kernel.org
Subject: Re: [PATCHv2 2/3] reiser4: call account_page_redirty() on re-dirtying pages before giving them to entd.
Date: Mon, 9 Nov 2015 12:50:42 +0100 [thread overview]
Message-ID: <56408892.6000709@gmail.com> (raw)
In-Reply-To: <1445727740-12361-3-git-send-email-intelfx100@gmail.com>
OK.
On 10/25/2015 01:02 AM, Ivan Shapovalov wrote:
> I guess we want that to rollback effects of account_page_dirtied()
> in set_page_dirty_notag().
>
> Signed-off-by: Ivan Shapovalov <intelfx100@gmail.com>
> ---
> fs/reiser4/entd.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/reiser4/entd.c b/fs/reiser4/entd.c
> index bff4bfa..c254e71 100644
> --- a/fs/reiser4/entd.c
> +++ b/fs/reiser4/entd.c
> @@ -303,6 +303,7 @@ int write_page_by_ent(struct page *page, struct writeback_control *wbc)
> * write it - it will remain dirty
> */
> set_page_dirty_notag(page);
> + account_page_redirty(page);
>
> /*
> * pin inode in memory, unlock page, entd_flush will iput. We can not
next prev parent reply other threads:[~2015-11-09 11:50 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 [this message]
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
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=56408892.6000709@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).