reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ivan Shapovalov <intelfx100@gmail.com>
Cc: Oleg Drokin <green@linuxhacker.ru>, reiserfs-devel@vger.kernel.org
Subject: Re: [PATCH 3/3] reiser4: in our own sync writes, mark pages dirty before marking them writeback.
Date: Mon, 12 Oct 2015 11:07:35 +0200	[thread overview]
Message-ID: <561B7857.1030000@gmail.com> (raw)
In-Reply-To: <1444473863.4257.10.camel@gmail.com>

On 10/10/2015 12:44 PM, Ivan Shapovalov wrote:
[...]
> I didn't check the code yet; I'll probably try with that assertion converted into warning and split into two
> (one for formatted and another for unformatted nodes), so that I could check what type of nodes is responsible
> for generating the final oops in set_page_writeback().

I suppose that oops happens on unformatted nodes, because
all formatted nodes have the same host - a special "fake" inode
with number 1, which gets i_wb at mount time (init_fake_inode()
calls inode_attach_wb()).

Edward.

>
>> For unformatted nodes only code review
>> can help. Normally, all modifications of unformatted nodes should
>> look like the following:
>>
>> struct page *page = jnode_page(node);
>> lock_page(page);
>> char *data = kmap(page);
>> /* modifications are going here */
>> kunmap(page);
>> set_page_dirty_nobuffers(page); /* somebody forgets to do this */
>> unlock_page(page);
>>
>> Modifications of formatted nodes should look like the following:
>>
>> longterm_lock_znode(node);
>> zload(node);
>> /* modifications are going here */
>> zrelse(node);
>> znode_make_dirty(node); /* somebody forgets to do this */
>> longterm_unlock_znode();
>>
>> Anyway, we can use your patch 3 as a temporal fixup.
> The most persistent things are those conseived as the most temporary
> ones... ;)


  parent reply	other threads:[~2015-10-12  9:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 11:16 [PATCH 0/3] reiser4: another batch of fixes for 4.2 Ivan Shapovalov
2015-10-09 11:16 ` [PATCH 1/3] reiser4: remove last traces of JNODE_NEW in the debugging code Ivan Shapovalov
2015-10-09 11:16 ` [PATCH 2/3] reiser4: call account_page_redirty() on re-dirtying pages before giving them to entd Ivan Shapovalov
2015-10-09 11:16 ` [PATCH 3/3] reiser4: in our own sync writes, mark pages dirty before marking them writeback Ivan Shapovalov
2015-10-09 13:27   ` Edward Shishkin
2015-10-09 13:50     ` Ivan Shapovalov
2015-10-09 14:55       ` Edward Shishkin
2015-10-09 16:13         ` Ivan Shapovalov
2015-10-09 16:27           ` Oleg Drokin
2015-10-09 16:29             ` Ivan Shapovalov
2015-10-09 17:14         ` Ivan Shapovalov
2015-10-09 20:23           ` Edward Shishkin
2015-10-10  7:19             ` Dušan Čolić
2015-10-10 10:44             ` Ivan Shapovalov
2015-10-10 15:03               ` Edward Shishkin
2015-10-10 16:51                 ` Oleg Drokin
2015-10-12  9:10                   ` Edward Shishkin
2015-10-12  9:07               ` Edward Shishkin [this message]
2015-10-14 10:05                 ` Ivan Shapovalov
2015-10-14 10:55                   ` Ivan Shapovalov
2015-10-14 19:06                     ` Ivan Shapovalov
2015-10-15 17:20                       ` Edward Shishkin
2015-10-24  7:17                         ` Ivan Shapovalov
2015-11-04 18:09                         ` Ivan Shapovalov
2015-11-09 11:40                           ` Edward Shishkin
2015-10-09 15:29   ` Oleg Drokin

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=561B7857.1030000@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=green@linuxhacker.ru \
    --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).