From: piaojun <piaojun@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] kernel bug
Date: Wed, 10 Jan 2018 20:03:43 +0800 [thread overview]
Message-ID: <5A56011F.8000906@huawei.com> (raw)
In-Reply-To: <CAN+OZjTsnQr8ybyA6kFz8eK=zQf6EOpDm4AHa7NvyCLCcOPGzQ@mail.gmail.com>
Hi C?dric,
You'd better paste the core dump stack and the method of reproducing
this BUG.
thanks,
Jun
On 2018/1/10 19:48, BASSAGET C?dric wrote:
> Hello
> Today I reported a bug related to ocfs2 1.8.on proxmox forum, maybe somebody here will be able to help me...
> The bog on proxmox forum : https://urldefense.proofpoint.com/v2/url?u=https-3A__forum.proxmox.com_threads_ocfs2-2Dkernel-2Dbug.39163_&d=DwID-g&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=C7gAd4uDxlAvTdc0vmU6X8CMk6L2iDY8-HD0qT6Fo7Y&m=Cjs_sZYvlRtRCpsPU_lWPoen_rJyr14Cw3AxxedrGac&s=1IlEt5_VsnceBwz_3AYQq8zKNy6viF9oxQGtp8odqn4&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__forum.proxmox.com_threads_ocfs2-2Dkernel-2Dbug.39163_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=C7gAd4uDxlAvTdc0vmU6X8CMk6L2iDY8-HD0qT6Fo7Y&m=93_F2INiG6ig-q6s8P3sPY09iW1NMx6_H9zZx13OxhM&s=j8Ae2cUQUVQJOimaDZOI0C-HbAhHPvEV-l6BS23AaSw&e=>
>
> to resume : kernel BUG at fs/ocfs2/suballoc.c:2017!
>
> is this related to proxmox kernel or ocfs2 ? or both ?
> does it have something to do with https://oss.oracle.com/pipermail/ocfs2-devel/2017-January/012701.html ?
>
> Thanks for your help.
> Regards,
> C?dric
>
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
>
prev parent reply other threads:[~2018-01-10 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 11:48 [Ocfs2-devel] kernel bug BASSAGET Cédric
2018-01-10 11:57 ` Changwei Ge
2018-01-10 14:34 ` BASSAGET Cédric
2018-01-11 1:03 ` Changwei Ge
2018-01-11 6:49 ` BASSAGET Cédric
2018-01-11 7:06 ` Changwei Ge
2018-01-11 11:51 ` BASSAGET Cédric
2018-01-12 2:16 ` Changwei Ge
2018-01-10 12:03 ` piaojun [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=5A56011F.8000906@huawei.com \
--to=piaojun@huawei.com \
--cc=ocfs2-devel@oss.oracle.com \
/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.