From: Edward Shishkin <edward.shishkin@gmail.com>
To: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Cc: dimas <dimas000@ya.ru>
Subject: Re: insserv on Debian triggers "kernel BUG at fs/reiser4/plugin/object.c:58"
Date: Mon, 19 Nov 2012 21:06:38 +0100 [thread overview]
Message-ID: <50AA914E.6020303@gmail.com> (raw)
In-Reply-To: <20121119231557.69d2488d@Ulf.tvoe.tv>
On 11/19/2012 08:15 PM, dimas wrote:
> any news about this? do i need to provide some more info?
Hello.
Everything is more, or less clear with this BUG at object.c:58:
for every directory reiser4 installs aops with stubs, which cause oops.
Nobody remembers the purpose of these stubs. I think we'll just get rid
of them in the next release..
The more unpleasant issue is that the corruption is not gone: I have
reproduced this again for both plugins (w/ and w/o compression).
So will continue to narrow down...
Thanks,
Edward.
prev parent reply other threads:[~2012-11-19 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 15:49 insserv on Debian triggers "kernel BUG at fs/reiser4/plugin/object.c:58" dimas
2012-11-07 20:47 ` Edward Shishkin
2012-11-07 20:50 ` Edward Shishkin
2012-11-08 14:44 ` dimas
2012-11-08 14:48 ` dimas
2012-11-19 19:15 ` dimas
2012-11-19 20:06 ` Edward Shishkin [this message]
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=50AA914E.6020303@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=dimas000@ya.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).