linux-ext4 - Re: Help required for Debugging JBD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTimhig+_Lb52KMcRyk5S4YQcdYozVg@mail.gmail.com>
Date:	Wed, 22 Jun 2011 09:43:52 +0300
From:	Amir Goldstein <amir73il@...il.com>
To:	Niraj Kulkarni <kulkarniniraj14@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Help required for Debugging JBD

On Tue, Jun 21, 2011 at 7:52 PM, Niraj Kulkarni
<kulkarniniraj14@...il.com> wrote:
> Hi all,
>        I have modified my JBD (no change to Ext3) to support
> Transactional-Flash. For that I require only to collect metadata and data
> blocks and send them simultaneously (no transaction record, revoke record
> etc).

It's hard to help without knowing what your patches do in more details.
Could you post the patches or give a more detailed description of how they
work?
For example, how do you collect data blocks without them being already
written? or is this not a requirement for your use case?

>       The problem is, though it works well for small number of operations,
> the kernel completely hangs when I run any benchmark (like blogbench or
> postmark) over them. The bad thing is that there is no trace left
> afterwards, ie logs don't contain any message since the operation was
> started, kernel OOPS are not shown, no faults are shown, no panic is shown
> even though I have enabled panic on hard/soft lockup. I have to hard reboot
> machine each time.

Did you try alt+sysrq+w to dump waiting tasks?

>        So essentially, I am totally clueless about the point  at which it is
> crashing or reason behind it. There is a small possibility that bug may be
> in modified MTD layer (which I've written myself), but since I have run
> unmodified Ext3 on that MTD layer without any bug, the chance of buggy MTD
> layer appears very slim.
>
> Any help in greatly appreciated.
>
> Niraj
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html