[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <27943e06-a503-162e-356b-abb9e106ab2e@grimberg.me>
Date: Thu, 25 Jul 2019 12:05:29 -0700
From: Sagi Grimberg <sagi@...mberg.me>
To: Matthew Wilcox <willy@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Jens Axboe <axboe@...com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>,
linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org,
Stephen Bates <sbates@...thlin.com>,
linux-block@...r.kernel.org, Keith Busch <kbusch@...nel.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-fsdevel@...r.kernel.org, Max Gurtovoy <maxg@...lanox.com>,
Logan Gunthorpe <logang@...tatee.com>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v6 02/16] chardev: introduce cdev_get_by_path()
>>> NVMe-OF is configured using configfs. The target is specified by the
>>> user writing a path to a configfs attribute. This is the way it works
>>> today but with blkdev_get_by_path()[1]. For the passthru code, we need
>>> to get a nvme_ctrl instead of a block_device, but the principal is the same.
>>
>> Why isn't a fd being passed in there instead of a random string?
>
> I suppose we could echo a string of the file descriptor number there,
> and look up the fd in the process' file descriptor table ...
Assuming that there is a open handle somewhere out there...
> I'll get my coat.
Grab mine too..
Powered by blists - more mailing lists