From: Edward Shishkin <edward.shishkin@gmail.com>
To: Metztli Information Technology <jose@metztli-it.com>,
reiserfs-devel@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: Linux 4.14.14 kernel bug on line 152 fs/reiser4/block_alloc.c
Date: Fri, 26 Jan 2018 14:51:50 +0100 [thread overview]
Message-ID: <983b9a19-bcc9-1f02-5fe6-a0958c22f7f0@gmail.com> (raw)
In-Reply-To: <20180126081539.10DD4E6762D@huitzilopochtli.metztli-it.com>
On 01/26/2018 09:15 AM, Metztli Information Technology wrote:
> Niltze, Ed-
Hello.
>
> I had been using Linux kernel 4.14.14 built 'the Debian way' for a couple of days
> --doing some light VirtualBox development and successful virtual machine test/creation.
>
> Notwithstanding, today 01-25-2018 experienced black screen kernel bug trace during browser usage.
> I wrote down line number of reiser4 file.
>
> FYI: No dataloss but had to reboot Debian AMD64 system due to 'kernel bug' at reference file/line:
>
> invalid opcode: 0000 [#2] SMP PTI
>
> file []-4.14.14/linux/fs/reiser4/block_alloc.c
> --------------------------------------------------
> [...]
> /* Static functions for <reiser4 super block>/<reiser4 context> block counters
> arithmetic. Mostly, they are isolated to not to code same assertions in
> several places. */
> static void sub_from_ctx_grabbed(reiser4_context * ctx, __u64 count)
> {
> BUG_ON(ctx->grabbed_blocks < count); # kernel bug line 152
> assert("zam-527", ctx->grabbed_blocks >= count);
> ctx->grabbed_blocks -= count;
> }
> [...]
This is an old bug: a leak of grabbed disk space (reservation).
If it is reproducible, then one needs to insert debugging messages
to find out where the grabbed space disappears. Otherwise, there
is no other means except code review.
> -----------------------------------------------------
>
> In addition to usual prior mentioned specific Linux 4.14.x series logged entries during kernel builds:
>
> fs/reiser4/carry.o: warning: objtool: fatal_carry_error.isra.5() falls through to next function print_level()
> fs/reiser4/txnmgr.o: warning: objtool: commit_txnh()+0x580: stack state mismatch: cfa1=7+120 cfa2=7+136
> fs/reiser4/flush.o: warning: objtool: reverse_allocate_parent() falls through to next function squalloc_right_twig_cut.isra.27()
> fs/reiser4/wander.o: warning: objtool: reiser4_write_logs()+0x5a2: stack state mismatch: cfa1=7+184 cfa2=7+200
> fs/reiser4/vfs_ops.o: warning: objtool: .text: unexpected end of section
I am aware of those warnings: a friendship with objtool is required.
Not of high priority.
Thanks,
Edward.
prev parent reply other threads:[~2018-01-26 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 8:15 Linux 4.14.14 kernel bug on line 152 fs/reiser4/block_alloc.c Metztli Information Technology
2018-01-26 13:51 ` 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=983b9a19-bcc9-1f02-5fe6-a0958c22f7f0@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=debian-kernel@lists.debian.org \
--cc=jose@metztli-it.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).