The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: NeilBrown <neilb@suse.com>, Tejun Heo <tj@kernel.org>,
	Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
	Ming Lei <ming.lei@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: [lkp-robot] [blk] 47e0fb461f: BUG:unable_to_handle_kernel
Date: Mon, 9 Oct 2017 16:10:50 +0800	[thread overview]
Message-ID: <20171009081050.GA31518@yexl-desktop> (raw)
In-Reply-To: <CA+55aFy6GJdq=N1uK7KmdV5XRSBjYv1Sdg=NbjOJsZr_+hadYQ@mail.gmail.com>

On 09/30, Linus Torvalds wrote:
>On Thu, Sep 21, 2017 at 12:02 AM, NeilBrown <neilb@suse.com> wrote:
>>
>> I think it is crashing in
>> static inline bool ata_is_host_link(const struct ata_link *link)
>> {
>>         return link == &link->ap->link || link == link->ap->slave_link;
>> }
>
>Yes. The code is
>
>  1a: 8b 3a                mov    (%edx),%edi
>  1c: 8d 8f 40 16 00 00    lea    0x1640(%edi),%ecx
>  22: 39 ca                cmp    %ecx,%edx
>  24: 74 49                je     0x6f
>  26: b9 01 00 00 00        mov    $0x1,%ecx
>  2b:* 39 97 80 24 00 00    cmp    %edx,0x2480(%edi) <-- trapping instruction
>  31: 74 3c                je     0x6f
>
>and that first "je" is the test for "link == &link->ap->link" (which
>only takes the address relative to "link->ap" - thus the "lea"), and
>that cmp that oopses is indeed loading that actual slave_link value.
>
>So I agree. "link->ap" is NULL for some odd reason.
>
>Hmm. Absolutely nothing has changed in libata-core.c recently,
>certainly not that async_port_probe() thing.
>
>So I suspect either it's just a timing difference, or it's some
>unrelated memory corruption.
>
>Xiaolong, I see that you have SLUB_DEBUG and SLUB_DEBUG_ON enabled,
>but wonder if you can recreate this with DEBUG_PAGEALLOC and/or
>DEBUG_OBJECTS enabled too?
>

Sorry for the late, just come back from vacation.
I retested with with DEBUG_PAGEALLOC and DEBUG_OBJECTS enabled for both
commit 47e0fb461f and commit 011067b056, and both showed the ata_dev_next
crash issue, so commit 47e0fb461f should be irrelevant, sorry for the noise.

Thanks,
Xiaolong

>Tejun, any ideas? The original report is at
>
>   https://lkml.org/lkml/2017/9/20/939
>
>in case you don't see it in your inbox from lkml.
>
>                       Linus

  reply	other threads:[~2017-10-09  8:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21  2:46 [lkp-robot] [blk] 47e0fb461f: BUG:unable_to_handle_kernel kernel test robot
2017-09-21  7:02 ` NeilBrown
2017-09-30 20:21   ` Linus Torvalds
2017-10-09  8:10     ` Ye Xiaolong [this message]
2017-10-09 16:05     ` Tejun Heo
2017-10-13  0:51       ` Ye Xiaolong
2017-10-21 16:39         ` Tejun Heo

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=20171009081050.GA31518@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=ming.lei@redhat.com \
    --cc=neilb@suse.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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