From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: Re: [block] 7647d99c22: BUG: KASAN: global-out-of-bounds in ide_cd_queue_pc at addr ffffffff853d51e0
Date: Thu, 12 Jan 2017 17:33:41 +0800 [thread overview]
Message-ID: <20170112093341.GA21982@intel.com> (raw)
In-Reply-To: <20170110090537.fbqkry6oflki6w6u@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
On Tue, Jan 10, 2017 at 05:05:37PM +0800, Fengguang Wu wrote:
> Hi Christoph,
>
> On Tue, Jan 10, 2017 at 09:46:55AM +0100, Christoph Hellwig wrote:
> >>[ 82.521845] BUG: KASAN: global-out-of-bounds in ide_cd_queue_pc+0xcd/0x2fb at addr ffffffff853d51e0
> >
> >Just curious: how hard would be to resolve these function-relative addresses
> >to a source line (ala gdb, l *(ide_cd_queue_pc+0xcd)) automaticaly as
> >part of the lkp run?
>
> It should be relatively easy and worth trying.
>
> Our normal kernel builds do not save vmlinux and their kconfigs are
> not guaranteed to have the debug symbols built-in. However it'd be
> convenient to build one extra kernel image with the above debug info
> for the first-bad-commit before reporting regression out. CC Philip
> for managing it as a TODO feature.
sure, we will handle this in next planning cycle q2 to provide the feature support.
>
> Regards,
> Fengguang
prev parent reply other threads:[~2017-01-12 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 16:35 [block] 7647d99c22: BUG: KASAN: global-out-of-bounds in ide_cd_queue_pc at addr ffffffff853d51e0 kernel test robot
2017-01-10 8:46 ` Christoph Hellwig
2017-01-10 9:05 ` Fengguang Wu
2017-01-12 9:33 ` Philip Li [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=20170112093341.GA21982@intel.com \
--to=philip.li@intel.com \
--cc=lkp@lists.01.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 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.