From: keith.busch@intel.com (Keith Busch)
Subject: Problem with new uapi header in Linux kernel 4.4+
Date: Thu, 6 Oct 2016 19:09:48 -0400 [thread overview]
Message-ID: <20161006230947.GA3696@localhost.localdomain> (raw)
In-Reply-To: <37b9f516-a945-d41f-b21a-48728d7f9680@fu-berlin.de>
On Thu, Oct 06, 2016@05:15:04PM +0200, Jan Luca Naumann wrote:
> Hey,
>
> at the moment I try to install a tool called "sedutil"[1]. The tool
> manages self encrypting drives that conform to the TCG OPAL 2.0
> specification.
>
> The program uses in the current version i.a. ioctl() to communicate with
> NVMe disks (see header [2] and source file [3]). The problem is that the
> tool uses the no longer to the user space exported header file
> "linux/nvme.h". In the new uapi header "linux/nvme_ioctl.h" are the
> enumeration "nvme_admin_opcode" and the structure "nvme_id_ctrl" no
> longer available that are used in the source code...
>
> Since I do not have much experience with ioctl/NVMe and the upstream
> author has no time at the moment, I want to ask you what would be the
> best attempt to fix this.
Yeah, we changed the uapi to only contain the what's necessary for the
user-kernel interface. We don't want user space to depend on the kernel
header for structure definitions when the kernel has no use for some them.
For the nvme-cli project, we define everything. I'm up for turning parts
of this into a shared library that sedutil and others can use.
next prev parent reply other threads:[~2016-10-06 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 15:15 Problem with new uapi header in Linux kernel 4.4+ Jan Luca Naumann
2016-10-06 23:09 ` Keith Busch [this message]
2016-10-07 7:29 ` Christoph Hellwig
2016-10-07 10:06 ` Jan Luca Naumann
2016-10-06 23:28 ` Bauer, Scott
2016-10-07 7:31 ` Christoph Hellwig
2016-10-07 14:31 ` Scott Bauer
2016-10-08 10:23 ` Jan Luca Naumann
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=20161006230947.GA3696@localhost.localdomain \
--to=keith.busch@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox