Linux-NVME Archive on lore.kernel.org
 help / color / Atom feed
From: Stefan Majer <stefan.majer@gmail.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Keith Busch <kbusch@kernel.org>,
	linux-nvme <linux-nvme@lists.infradead.org>
Subject: Re: null pointer dereference in nvme_tcp_io_work
Date: Thu, 16 Jan 2020 07:28:34 +0100
Message-ID: <CADdPHGtfGX=ZnJ_K+T+1CuF2HyFJA2zw-KU39foX5em+kXw1Bg@mail.gmail.com> (raw)
In-Reply-To: <27c302af-0a0e-2739-6f54-b09007d088e8@grimberg.me>

Hi Sagi,
Sure, no problem.
Wil report back. Thanks for looking into.
Greetings
Stefan

On Wed, Jan 15, 2020 at 9:03 PM Sagi Grimberg <sagi@grimberg.me> wrote:
>
>
> > Hi,
> >
> > is there anything i can help with to further nail down the problem ?
>
> Hi Stephen,
>
> I cannot reproduce this issue with my environment (both host and target
> are VMs on my laptop, kernel 5.4.0 qemu version 3.1.0).
>
> Would it be possible to try and use kernel 5.4 for the sake of the test?



-- 
Stefan Majer

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

      reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25 10:06 Stefan Majer
2019-12-26 17:47 ` Keith Busch
2019-12-27  7:18   ` Stefan Majer
     [not found]     ` <CAB5Wxwco3KD1e_nRGQ_mWAMa_2d-wP2-1Aao4ZXtDeVgFQQM_w@mail.gmail.com>
2019-12-27  7:54       ` Stefan Majer
2019-12-28 17:49         ` Stefan Majer
2019-12-28 17:53           ` Stefan Majer
2020-01-07 15:41             ` Stefan Majer
2020-01-07 16:48               ` Nadolski, Edmund
2020-01-15 20:03               ` Sagi Grimberg
2020-01-16  6:28                 ` Stefan Majer [this message]

Reply instructions:

You may reply publically 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='CADdPHGtfGX=ZnJ_K+T+1CuF2HyFJA2zw-KU39foX5em+kXw1Bg@mail.gmail.com' \
    --to=stefan.majer@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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

Linux-NVME Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-nvme/0 linux-nvme/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nvme linux-nvme/ https://lore.kernel.org/linux-nvme \
		linux-nvme@lists.infradead.org
	public-inbox-index linux-nvme

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-nvme


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git