From: Edward Shishkin <edward.shishkin@gmail.com>
To: Dushan Tcholich <dusanc@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 Oops
Date: Wed, 05 Jan 2011 13:10:49 +0100 [thread overview]
Message-ID: <4D245FC9.4040006@gmail.com> (raw)
In-Reply-To: <AANLkTinbSRgNhi5heC2npLNzU4xsuUjzEXBD5qDBiYDw@mail.gmail.com>
On 01/05/2011 12:04 PM, Dushan Tcholich wrote:
> Hello
>
> Can we have some version number after kernel version for fixups as
> latest upload for .36 on kernel.org is from 27-Dec-2010 21:17
> That's the 3rd version for .36 with same name, so there'll probably be
> some confusion :D
>
Ok, I'll put additional ones suffixed with "-x" (x=1, 2, ...)
Edward.
> Thanks
>
> Dushan
>
> On Mon, Dec 20, 2010 at 11:31 PM, Edward Shishkin
> <edward.shishkin@gmail.com> wrote:
>
>> Hello.
>>
>> Could you please try the attached patch?
>>
>> This patch is against reiser4-for-2.6.36.
>> Also please make sure you have the latest one
>> (I have updated the stuff 11-Dec-2010).
>>
>> Report, if any problems.
>>
>> Thanks,
>> Edward.
>>
>>
>> On Sun, Dec 19, 2010 at 11:33 PM, Edward Shishkin
>> <edward.shishkin@gmail.com> wrote:
>>
>>> Андрей Колченко wrote:
>>>
>>>> Wanted to try reiser4. I have compiled a kernel with reiser4, format
>>>> the partition and began to copy the folder /home.
>>>> After a short time the screen goes black and there was one console
>>>> with the error output. After switching to other tty and back up
>>>> continued. dmesg output copied to the pastebin
>>>> (http://pastebin.com/XyDKWJ8J).
>>>> This was repeated several times and the computer hangs perfectly still.
>>>> I have ubuntu 10.10 on a laptop Acer Aspire 7720z.
>>>>
>>> Yup, I see the bug:
>>> instead of writing pages reiser4 kicks ext4 to do it,
>>> and, I guess, doesn't clear journal_info (this is why
>>> ext4 oopses).
>>>
>>> [ 278.062271] [<c0318822>] ? jbd2_journal_start+0x12/0x20
>>> [ 278.062322] [<c02f5858>] ? ext4_journal_start_sb+0xc8/0x100
>>> [ 278.062377] [<c02e0957>] ? ext4_meta_trans_blocks+0x67/0xc0
>>> [ 278.062431] [<c02e47e3>] ? ext4_da_writepages+0x203/0x560
>>> [ 278.062484] [<c060fccd>] ? _raw_spin_lock+0xd/0x10
>>> [ 278.062530] [<c0281ca2>] ? flush_some_atom+0x312/0x540
>>> [ 278.062578] [<c02a4cdd>] ? writepages_cryptcompress+0x19d/0x220
>>> [ 278.062636] [<c02913a8>] ? reiser4_writeout+0xa8/0x1a0
>>> [ 278.062684] [<c022c186>] ? iput+0x36/0x270
>>> [ 278.062724] [<c02367e4>] ? generic_writeback_sb_inodes+0xe4/0x150
>>> [ 278.062782] [<c01dfaac>] ? do_writepages+0x1c/0x40
>>> [ 278.062826] [<c0236125>] ? writeback_single_inode+0x85/0x250
>>> [ 278.062877] [<c060fccd>] ? _raw_spin_lock+0xd/0x10
>>> [ 278.062921] [<c028db64>] ? reiser4_writeback_inodes+0xa4/0x130
>>> [ 278.062974] [<c02367b1>] ? generic_writeback_sb_inodes+0xb1/0x150
>>> [ 278.063031] [<c0236c6b>] ? writeback_inodes_wb+0x10b/0x150
>>>
>>>
>>> here should be writeback_sb_inodes() instead of writeback_inodes_wb
>>>
>>>
>>> [ 278.063082] [<c0291d06>] ? entd_flush+0xa6/0xe0
>>> [ 278.063127] [<c0291d40>] ? entd+0x0/0x240
>>> [ 278.063166] [<c0291e51>] ? entd+0x111/0x240
>>> [ 278.063208] [<c0165fd0>] ? autoremove_wake_function+0x0/0x50
>>> [ 278.064008] [<c0291d40>] ? entd+0x0/0x240
>>> [ 278.067417] [<c0165ba4>] ? kthread+0x74/0x80
>>> [ 278.067417] [<c0165b30>] ? kthread+0x0/0x80
>>> [ 278.067417] [<c010357e>] ? kernel_thread_helper+0x6/0x10
>>>
>>>
>>> It is interesting that the path
>>> entd -> writeback_inodes_wb -> ext4_da_writepages
>>> has never been triggered on my testing machine (I also
>>> have reiser4 and ext4 there). Perhaps, this is because
>>> of different system configurations.
>>>
>>> I'll try to fix it in the near future, so that you'll be able to
>>> try reiser4.
>>>
>>> Thanks for your report,
>>> Edward.
>>>
>>>
>>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-05 12:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 19:01 Reiser4 Oops Андрей Колченко
2010-12-19 22:33 ` Edward Shishkin
2010-12-20 22:31 ` Edward Shishkin
[not found] ` <AANLkTinbSRgNhi5heC2npLNzU4xsuUjzEXBD5qDBiYDw@mail.gmail.com>
2011-01-05 12:10 ` Edward Shishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-02 8:34 Reiser4 oops Piotr Sawuk
2006-07-01 20:08 reiser4 oops Łukasz Mierzwa
2006-07-01 20:13 ` Łukasz Mierzwa
2006-07-03 4:24 ` Jake Maciejewski
[not found] ` <1151921448.6335.42.camel@tribesman.namesys.com>
2006-07-03 11:51 ` Łukasz Mierzwa
2006-07-03 23:23 ` Jake Maciejewski
2006-07-07 7:18 ` Jake Maciejewski
[not found] ` <1152278167.6236.21.camel@tribesman.namesys.com>
2006-07-11 6:43 ` Jake Maciejewski
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=4D245FC9.4040006@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=dusanc@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).