From: Jethro Beekman <kernel@jbeekman.nl> To: Scott Bauer <scott.bauer@intel.com>, linux-nvme@lists.infradead.org Cc: Rafael.Antognolli@intel.com, axboe@fb.com, keith.busch@intel.com, jonathan.derrick@intel.com, viro@zeniv.linux.org.uk, hch@infradead.org, linux-kernel@vger.kernel.org, sagi@grimberg.me Subject: Re: [PATCH v3 1/5] include: Add definitions for sed Date: Sun, 25 Dec 2016 15:15:53 +0100 [thread overview] Message-ID: <26b9c96f-99ae-6669-5cbe-bff563e20255@jbeekman.nl> (raw) In-Reply-To: <1482176149-2257-2-git-send-email-scott.bauer@intel.com> On 19-12-16 20:35, Scott Bauer wrote: > diff --git a/include/linux/sed.h b/include/linux/sed.h > > +/* > + * These constant values come from: > + * TCG Storage Architecture Core Spec v2.01 r1 > + * Section: 3.3 Interface Communications > + */ > +enum { > + TCG_SECP_00 = 0, Protocol 0 is not defined by TCG. Perhaps you should reference SPC-4 section 6.30 SECURITY PROTOCOL IN command / table 265. > diff --git a/include/uapi/linux/sed.h b/include/uapi/linux/sed.h > > +enum sed_key_type { > + OPAL, > + OPAL_PW, > + OPAL_ACT_USR, > + OPAL_LR_SETUP, > + OPAL_LOCK_UNLOCK, > + OPAL_MBR_DATA, > +}; > + > +struct sed_key { > + __u32 sed_type; > + union { > + struct opal_key opal; > + struct opal_new_pw opal_pw; > + struct opal_session_info opal_session; > + struct opal_user_lr_setup opal_lrs; > + struct opal_lock_unlock opal_lk_unlk; > + struct opal_mbr_data opal_mbr; > + /* additional command set key types */ > + }; > +}; > + > +#define IOC_SED_SAVE _IOW('p', 220, struct sed_key) > +#define IOC_SED_LOCK_UNLOCK _IOW('p', 221, struct sed_key) > +#define IOC_SED_TAKE_OWNERSHIP _IOW('p', 222, struct sed_key) > +#define IOC_SED_ACTIVATE_LSP _IOW('p', 223, struct sed_key) > +#define IOC_SED_SET_PW _IOW('p', 224, struct sed_key) > +#define IOC_SED_ACTIVATE_USR _IOW('p', 225, struct sed_key) > +#define IOC_SED_REVERT_TPR _IOW('p', 226, struct sed_key) > +#define IOC_SED_LR_SETUP _IOW('p', 227, struct sed_key) > +#define IOC_SED_ADD_USR_TO_LR _IOW('p', 228, struct sed_key) > +#define IOC_SED_ENABLE_DISABLE_MBR _IOW('p', 229, struct sed_key) > +#define IOC_SED_ERASE_LR _IOW('p', 230, struct sed_key) > +#define IOC_SED_SECURE_ERASE_LR _IOW('p', 231, struct sed_key) I'm slightly confused by the split between SED-generic and OPAL-specific files here. Maybe I'm misunderstanding the intent of these ioctls. I think SED means "possible any drive supporting the security command set". Therefore these definitions (quoted) should have OPAL names and live in an OPAL header. Jethro
WARNING: multiple messages have this Message-ID (diff)
From: kernel@jbeekman.nl (Jethro Beekman) Subject: [PATCH v3 1/5] include: Add definitions for sed Date: Sun, 25 Dec 2016 15:15:53 +0100 [thread overview] Message-ID: <26b9c96f-99ae-6669-5cbe-bff563e20255@jbeekman.nl> (raw) In-Reply-To: <1482176149-2257-2-git-send-email-scott.bauer@intel.com> On 19-12-16 20:35, Scott Bauer wrote: > diff --git a/include/linux/sed.h b/include/linux/sed.h > > +/* > + * These constant values come from: > + * TCG Storage Architecture Core Spec v2.01 r1 > + * Section: 3.3 Interface Communications > + */ > +enum { > + TCG_SECP_00 = 0, Protocol 0 is not defined by TCG. Perhaps you should reference SPC-4 section 6.30 SECURITY PROTOCOL IN command / table 265. > diff --git a/include/uapi/linux/sed.h b/include/uapi/linux/sed.h > > +enum sed_key_type { > + OPAL, > + OPAL_PW, > + OPAL_ACT_USR, > + OPAL_LR_SETUP, > + OPAL_LOCK_UNLOCK, > + OPAL_MBR_DATA, > +}; > + > +struct sed_key { > + __u32 sed_type; > + union { > + struct opal_key opal; > + struct opal_new_pw opal_pw; > + struct opal_session_info opal_session; > + struct opal_user_lr_setup opal_lrs; > + struct opal_lock_unlock opal_lk_unlk; > + struct opal_mbr_data opal_mbr; > + /* additional command set key types */ > + }; > +}; > + > +#define IOC_SED_SAVE _IOW('p', 220, struct sed_key) > +#define IOC_SED_LOCK_UNLOCK _IOW('p', 221, struct sed_key) > +#define IOC_SED_TAKE_OWNERSHIP _IOW('p', 222, struct sed_key) > +#define IOC_SED_ACTIVATE_LSP _IOW('p', 223, struct sed_key) > +#define IOC_SED_SET_PW _IOW('p', 224, struct sed_key) > +#define IOC_SED_ACTIVATE_USR _IOW('p', 225, struct sed_key) > +#define IOC_SED_REVERT_TPR _IOW('p', 226, struct sed_key) > +#define IOC_SED_LR_SETUP _IOW('p', 227, struct sed_key) > +#define IOC_SED_ADD_USR_TO_LR _IOW('p', 228, struct sed_key) > +#define IOC_SED_ENABLE_DISABLE_MBR _IOW('p', 229, struct sed_key) > +#define IOC_SED_ERASE_LR _IOW('p', 230, struct sed_key) > +#define IOC_SED_SECURE_ERASE_LR _IOW('p', 231, struct sed_key) I'm slightly confused by the split between SED-generic and OPAL-specific files here. Maybe I'm misunderstanding the intent of these ioctls. I think SED means "possible any drive supporting the security command set". Therefore these definitions (quoted) should have OPAL names and live in an OPAL header. Jethro
next prev parent reply other threads:[~2016-12-25 14:43 UTC|newest] Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-12-19 19:35 [PATCH v3 0/5] SED OPAL Library Scott Bauer 2016-12-19 19:35 ` Scott Bauer 2016-12-19 19:35 ` [PATCH v3 1/5] include: Add definitions for sed Scott Bauer 2016-12-19 19:35 ` Scott Bauer 2016-12-20 6:46 ` Christoph Hellwig 2016-12-20 6:46 ` Christoph Hellwig 2016-12-25 14:15 ` Jethro Beekman [this message] 2016-12-25 14:15 ` Jethro Beekman 2016-12-27 22:14 ` Scott Bauer 2016-12-27 22:14 ` Scott Bauer 2016-12-19 19:35 ` [PATCH v3 2/5] lib: Add Sed-opal library Scott Bauer 2016-12-19 19:35 ` Scott Bauer 2016-12-19 21:34 ` Keith Busch 2016-12-19 21:34 ` Keith Busch 2016-12-20 6:07 ` Christoph Hellwig 2016-12-20 6:07 ` Christoph Hellwig 2016-12-20 3:21 ` kbuild test robot 2016-12-20 3:21 ` kbuild test robot 2016-12-20 3:48 ` kbuild test robot 2016-12-20 3:48 ` kbuild test robot 2016-12-20 6:50 ` Al Viro 2016-12-20 6:50 ` Al Viro 2016-12-20 7:28 ` Christoph Hellwig 2016-12-20 7:28 ` Christoph Hellwig 2016-12-20 21:55 ` Scott Bauer 2016-12-20 21:55 ` Scott Bauer 2016-12-21 9:42 ` Christoph Hellwig 2016-12-21 9:42 ` Christoph Hellwig 2016-12-20 22:07 ` Jon Derrick 2016-12-20 22:07 ` Jon Derrick 2016-12-21 9:47 ` Christoph Hellwig 2016-12-21 9:47 ` Christoph Hellwig 2016-12-19 19:35 ` [PATCH v3 3/5] fs: Wire up SED/Opal to ioctl Scott Bauer 2016-12-19 19:35 ` Scott Bauer 2016-12-20 6:21 ` Christoph Hellwig 2016-12-20 6:21 ` Christoph Hellwig 2016-12-19 19:35 ` [PATCH v3 4/5] nvme: Implement resume_from_suspend and SED Allocation code Scott Bauer 2016-12-19 19:35 ` Scott Bauer 2016-12-19 21:59 ` Keith Busch 2016-12-19 21:59 ` Keith Busch 2016-12-19 22:23 ` Scott Bauer 2016-12-19 22:23 ` Scott Bauer 2016-12-20 6:17 ` Christoph Hellwig 2016-12-20 6:17 ` Christoph Hellwig 2016-12-20 15:49 ` Keith Busch 2016-12-20 15:49 ` Keith Busch 2016-12-20 15:46 ` Christoph Hellwig 2016-12-20 15:46 ` Christoph Hellwig 2016-12-20 16:05 ` Scott Bauer 2016-12-20 16:05 ` Scott Bauer 2016-12-21 9:01 ` Christoph Hellwig 2016-12-21 9:01 ` Christoph Hellwig 2016-12-20 17:52 ` Scott Bauer 2016-12-20 17:52 ` Scott Bauer 2016-12-21 9:37 ` Christoph Hellwig 2016-12-21 9:37 ` Christoph Hellwig 2016-12-20 4:11 ` kbuild test robot 2016-12-20 4:11 ` kbuild test robot 2016-12-20 6:21 ` Christoph Hellwig 2016-12-20 6:21 ` Christoph Hellwig 2016-12-20 6:49 ` Christoph Hellwig 2016-12-20 6:49 ` Christoph Hellwig 2016-12-25 14:15 ` Jethro Beekman 2016-12-25 14:15 ` Jethro Beekman 2016-12-27 22:12 ` Scott Bauer 2016-12-27 22:12 ` Scott Bauer 2016-12-28 8:39 ` Christoph Hellwig 2016-12-28 8:39 ` Christoph Hellwig 2016-12-19 19:35 ` [PATCH v3 5/5] Maintainers: Add Information for SED Opal library Scott Bauer 2016-12-19 19:35 ` Scott Bauer
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=26b9c96f-99ae-6669-5cbe-bff563e20255@jbeekman.nl \ --to=kernel@jbeekman.nl \ --cc=Rafael.Antognolli@intel.com \ --cc=axboe@fb.com \ --cc=hch@infradead.org \ --cc=jonathan.derrick@intel.com \ --cc=keith.busch@intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=sagi@grimberg.me \ --cc=scott.bauer@intel.com \ --cc=viro@zeniv.linux.org.uk \ /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: linkBe 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.