linux-kernel - Re: PROBLEM: ARM-dma-mapping-fix-for-speculative-prefetching cause OOPS

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: <BANLkTimBTayh_mjOLMZbz3D+wqdtZ10=wA@mail.gmail.com>
Date:	Thu, 30 Jun 2011 19:16:24 +0800
From:	Qin Dehua <qindehua@...il.com>
To:	Russell King <rmk@....linux.org.uk>
Cc:	linux-kernel@...r.kernel.org, santosh.shilimkar@...com,
	dan.j.williams@...el.com, neilb@...e.de
Subject: Re: PROBLEM: ARM-dma-mapping-fix-for-speculative-prefetching cause OOPS

Commit 2ffe2da3e follows v2.6.32, the message is from kernel build on
commit 2ffe2da3e.

The config has CONFIG_BUG=y and CONFIG_DEBUG_BUGVERBOSE=y, but the
message is Oops, not BUG() macro, so they don't have line number.

Regards,
QinDehua

2011/6/30, Russell King <rmk@....linux.org.uk>:
> These traces are from 2.6.32... And I assume have CONFIG_BUG unset
> because you have no verbose bug reporting (it's not reporting the
> file/line which is necessary to identify which BUG has been hit in
> the raid code.)
>
> Could you reproduce with CONFIG_BUG=y please?
>
> --
> Russell King
>  Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
>  maintainer of:
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/