From: Ivan Shapovalov <intelfx100@gmail.com>
To: Edward Shishkin <edward.shishkin@gmail.com>,
reiserfs-devel@vger.kernel.org
Cc: Oleg Drokin <green@linuxhacker.ru>
Subject: Re: [PATCH 3/3] reiser4: in our own sync writes, mark pages dirty before marking them writeback.
Date: Fri, 09 Oct 2015 20:14:02 +0300 [thread overview]
Message-ID: <1444410842.2213.5.camel@gmail.com> (raw)
In-Reply-To: <5617D55D.2040908@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
On 2015-10-09 at 16:55 +0200, Edward Shishkin wrote:
>
> On 10/09/2015 03:50 PM, Ivan Shapovalov wrote:
> > On 2015-10-09 at 15:27 +0200, Edward Shishkin wrote:
> > > Hi Ivan,
> > >
> > > On 10/09/2015 01:16 PM, Ivan Shapovalov wrote:
> > > > Ref.: https://www.mail-archive.com/linux-f2fs-devel%40lists.sou
> > > > rcef
> > > > orge.net/msg02745.html
> > > Do you have a stack trace for reiser4?
> > > How to reproduce it?
> > I'll rebuild the kernel without the fix and provide you with the
> > oops'
> > stacktrace asap.
> >
> > I guess that it's tied to the config. In my case, it is
> > reproducible on
> > each boot, just as the DE starts up and something issues the first
> > fsync().
>
>
> Yes, let's try to find the culprit who doesn't set i_wb...
So, here are the traces I've got after adding an
assert(PageDirty(node->pg)) to queue_jnode():
/* captured by hand as these are panics, not oopses */
1.
queue_jnode()
unformatted_make_reloc()
assign_real_blocknrs()
forward_relocate_unformatted()
forward_alloc_unformatted_journal()
? coord_num_units()
handle_pos_on_twig()
flush_current_atom()
flush_some_atom()
reiser4_writeout()
reiser4_writeback_inodes()
<...>
2.
znode_make_reloc()
forward_alloc_formatted_wa()
? zload_ra()
allocate_znode()
alloc_pos_and_ancestors()
flush_current_atom()
reiser4_txn_end()
? reiser4_txn_end()
reiser4_txn_restart_current()
force_commit_atom()
? reiser4_txn_restart_current()
txnmgr_force_commit_all()
writepages_cryptcompress()
reiser4_writepages_dispatch()
<...>
sys_fsync()
--
Ivan Shapovalov / intelfx /
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next prev parent reply other threads:[~2015-10-09 17:14 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 [this message]
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
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=1444410842.2213.5.camel@gmail.com \
--to=intelfx100@gmail.com \
--cc=edward.shishkin@gmail.com \
--cc=green@linuxhacker.ru \
--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).