From: Keith Busch <kbusch@kernel.org>
To: Talker Alex <alextalker@yandex.ru>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-nvme <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvmet: fix null-pointer when removing a referral
Date: Fri, 17 Jan 2020 01:08:11 +0900 [thread overview]
Message-ID: <20200116160811.GB28993@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <416341579184141@vla4-9d01d86ae0b7.qloud-c.yandex.net>
On Thu, Jan 16, 2020 at 05:15:40PM +0300, Talker Alex wrote:
> Ping.
>
> Would anyone kindly finally merge this fix?
Patch applied for-5.6, thank you for the ping.
> 12.12.2019, 13:43, "Christoph Hellwig" <hch@infradead.org>:
> > On Thu, Dec 12, 2019 at 01:36:28PM +0300, Talker Alex wrote:
> >> nvmet_referral_release() was called when item->ci_parent
> >> or item->ci_group were already set to NULL by configfs internals.
> >>
> >> Signed-off-by: Aleksandr Diadiushkin <alextalker@ya.ru>
> >
> > Looks good,
> >
> > Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> _______________________________________________
> linux-nvme mailing list
> linux-nvme@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2020-01-16 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 20:39 [PATCH] nvmet: fix null-pointer when removing a referral Talker Alex
2019-12-06 22:31 ` Sagi Grimberg
2019-12-07 10:21 ` Talker Alex
2019-12-12 9:33 ` Christoph Hellwig
2019-12-12 10:36 ` Talker Alex
2019-12-12 10:40 ` Talker Alex
2019-12-12 10:43 ` Christoph Hellwig
2020-01-16 14:15 ` Talker Alex
2020-01-16 16:08 ` Keith Busch [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=20200116160811.GB28993@redsun51.ssa.fujisawa.hgst.com \
--to=kbusch@kernel.org \
--cc=alextalker@yandex.ru \
--cc=hch@infradead.org \
--cc=linux-nvme@lists.infradead.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.