All of lore.kernel.org
 help / color / mirror / Atom feed
From: yizhan@redhat.com (Yi Zhang)
Subject: kernel tried to execute NX-protected page - exploit attempt? (uid: 0) and kernel BUG observed on 4.13.0-rc7
Date: Fri, 1 Sep 2017 07:08:08 -0400 (EDT)	[thread overview]
Message-ID: <1813385109.3857319.1504264088445.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <862abde5-894b-3378-bd5b-7cd803d63667@redhat.com>

Hi Sagi

I reproduced this issue again, here is the full log:
server1: https://pastebin.com/4wTfrbLj
server2: https://pastebin.com/K1tpApgt

It's more complex to reproduce it this time:
steps I used:
1. set up target on both server1 and server2.
2. On server1, connect server2, do IO background and reset operation, cancel it after several seconds.
3. On server2, connect server1, do IO background and reset operation, cancel it after several seconds.
4. Do step 2-3 until reproduced it.


Best Regards,
  Yi Zhang


----- Original Message -----
From: "Yi Zhang" <yizhan@redhat.com>
To: linux-nvme at lists.infradead.org, "Sagi Grimberg" <sagi at grimberg.me>
Cc: "Max Gurtovoy" <maxg at mellanox.com>
Sent: Thursday, August 31, 2017 9:09:57 PM
Subject: Re: kernel tried to execute NX-protected page - exploit attempt? (uid: 0) and kernel BUG observed on 4.13.0-rc7



On 08/31/2017 08:19 PM, Sagi Grimberg wrote:
> Hi Yi,
>
> Can you share th host dmesg prior to the crash?
>

Hi Sagi
Here is the full console log from client side.
https://pastebin.com/dfmvuPhJ

> It looks like we get a timeout expiration on a request with
> an already freed resources...
>
> Did one of the controller resets in the loop fail by any chance?
>

I remember this bug occurred at the first reset operation and hang at 
there, from the log we can also confirm it

> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme


_______________________________________________
Linux-nvme mailing list
Linux-nvme at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

      reply	other threads:[~2017-09-01 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1054759477.3536176.1504148224403.JavaMail.zimbra@redhat.com>
2017-08-31  4:00 ` kernel tried to execute NX-protected page - exploit attempt? (uid: 0) and kernel BUG observed on 4.13.0-rc7 Yi Zhang
2017-08-31 12:19   ` Sagi Grimberg
2017-08-31 13:09     ` Yi Zhang
2017-09-01 11:08       ` Yi Zhang [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=1813385109.3857319.1504264088445.JavaMail.zimbra@redhat.com \
    --to=yizhan@redhat.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.