From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v3] nvmet-rdma: fix null dereference under heavy load
Date: Sat, 19 Jan 2019 05:34:10 -0800 [thread overview]
Message-ID: <20190119133410.GA6963@infradead.org> (raw)
In-Reply-To: <20190103173531.7987-1-rajur@chelsio.com>
This looks ok to me:
Reviewed-by: Christoph Hellwig <hch at lst.de>
In the long run I wonder if we should get rid of the ?tatic
preallocation entirely and just use a free pool to avoid constant
reallocations..
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Raju Rangoju <rajur@chelsio.com>
Cc: sagi@grimberg.me, linux-nvme@lists.infradead.org,
maxg@mellanox.com, swise@opengridcomputing.com,
stable@vger.kernel.org
Subject: Re: [PATCH v3] nvmet-rdma: fix null dereference under heavy load
Date: Sat, 19 Jan 2019 05:34:10 -0800 [thread overview]
Message-ID: <20190119133410.GA6963@infradead.org> (raw)
In-Reply-To: <20190103173531.7987-1-rajur@chelsio.com>
This looks ok to me:
Reviewed-by: Christoph Hellwig <hch@lst.de>
In the long run I wonder if we should get rid of the ѕtatic
preallocation entirely and just use a free pool to avoid constant
reallocations..
next prev parent reply other threads:[~2019-01-19 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 17:35 [PATCH v3] nvmet-rdma: fix null dereference under heavy load Raju Rangoju
2019-01-03 17:35 ` Raju Rangoju
2019-01-03 23:13 ` Sagi Grimberg
2019-01-03 23:13 ` Sagi Grimberg
2019-01-07 15:59 ` Steve Wise
2019-01-07 15:59 ` Steve Wise
2019-01-18 7:37 ` Raju Rangoju
2019-01-18 7:37 ` Raju Rangoju
2019-01-19 13:34 ` Christoph Hellwig [this message]
2019-01-19 13:34 ` Christoph Hellwig
2019-01-21 9:10 ` Sagi Grimberg
2019-01-21 9:10 ` Sagi Grimberg
2019-01-21 13:07 ` Max Gurtovoy
2019-01-21 13:07 ` Max Gurtovoy
2019-01-21 15:46 ` Steve Wise
2019-01-21 15:46 ` Steve Wise
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=20190119133410.GA6963@infradead.org \
--to=hch@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.