[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210325163028.GA737@lst.de>
Date: Thu, 25 Mar 2021 17:30:28 +0100
From: Christoph Hellwig <hch@....de>
To: Niklas Cassel <Niklas.Cassel@....com>
Cc: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...com>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
"minwoo.im.dev@...il.com" <minwoo.im.dev@...il.com>,
"javier@...igon.com" <javier@...igon.com>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] nvme: disallow passthru cmd from targeting a nsid !=
nsid of the block dev
On Thu, Mar 25, 2021 at 09:48:37AM +0000, Niklas Cassel wrote:
> @@ -1632,6 +1632,8 @@ static int nvme_user_cmd(struct nvme_ctrl *ctrl, struct nvme_ns *ns,
> return -EFAULT;
> if (cmd.flags)
> return -EINVAL;
> + if (ns && cmd.nsid != ns->head->ns_id)
> + return -EINVAL;
Shouldn't we log something to the kernel log including the device
and current->comm?
Powered by blists - more mailing lists