From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 45621] Kernel ooops: BUG: unable to handle kernel paging request at 000000080000001c
Date: Wed, 7 Nov 2012 14:18:31 +0000 (UTC) [thread overview]
Message-ID: <20121107141831.8C1BB11FB59@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-45621-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=45621
Shapovalov Ivan <ishapic@mail.ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ishapic@mail.ru
--- Comment #9 from Shapovalov Ivan <ishapic@mail.ru> 2012-11-07 14:18:31 ---
(In reply to comment #8)
> So you use raiser4(which is known to have such type of corruption) and
> wondering that other parts of dcache becomes corrupted? Have you ever reproduce
> this w/o raiser4-pc ? I'm pretty sure that his is raiser's bug and absolutely
> not related with ext4
Could you please elaborate - which type of corruption reiser4 is known to have?
I'm not aware of these...
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-11-07 14:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 23:33 [Bug 45621] New: Kernel ooops: BUG: unable to handle kernel paging request at 000000080000001c bugzilla-daemon
2012-08-04 23:45 ` [Bug 45621] " bugzilla-daemon
2012-08-05 22:12 ` bugzilla-daemon
2012-08-05 22:24 ` bugzilla-daemon
2012-08-05 22:36 ` bugzilla-daemon
2012-08-06 15:15 ` bugzilla-daemon
2012-08-06 22:14 ` bugzilla-daemon
2012-08-06 22:21 ` Gordan Bobic
2012-11-07 9:58 ` bugzilla-daemon
2012-11-07 12:42 ` bugzilla-daemon
2012-11-07 14:18 ` bugzilla-daemon [this message]
2013-11-19 23:43 ` bugzilla-daemon
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=20121107141831.8C1BB11FB59@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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.