Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jonathan.derrick@intel.com (Jon Derrick)
Subject: [PATCH v4 2/6] block: Add Sed-opal library
Date: Fri, 30 Dec 2016 14:02:56 -0700	[thread overview]
Message-ID: <20161230210255.GA4148@localhost.localdomain> (raw)
In-Reply-To: <1483039615-22407-3-git-send-email-scott.bauer@intel.com>

Hi Scott,

I haven't had much time with this yet, but..

[snip]
> +static int do_cmds(struct opal_dev *dev)
> +{
> +	int ret;
> +	ret = next(dev);
> +	mutex_unlock(&dev->dev_lock);
> +	return ret;
> +}
> +
> +static struct opal_dev *get_opal_dev(struct sed_context *sedc,
> +				     const opal_step *funcs)
> +{
> +	struct opal_dev *dev = sedc->dev;
> +	if (dev) {
> +		mutex_lock(&dev->dev_lock);
> +		dev->state = 0;
> +		dev->funcs = funcs;
> +		dev->tsn = 0;
> +		dev->hsn = 0;
> +		dev->error_cb = end_opal_session_error;
> +		dev->error_cb_data = dev;
> +		dev->func_data = NULL;
> +		dev->prev_data = NULL;
> +		dev->sed_ctx = sedc;
> +		dev->save_discovery = false;
> +	}
> +	return dev;
> +}
> +
> 

It's a bit nontraditional to lock and unlock in different functions, but
I see why you're doing it this way.

Can we move the mutex locking/unlocking to the callers of these
functions, such that they are both in the same function; then we can use
lockdep_assert_held(..) on the in-between?

Cheers

  reply	other threads:[~2016-12-30 21:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 19:26 [PATCH v4 0/6] SED OPAL Library Scott Bauer
2016-12-29 19:26 ` [PATCH v4 1/6] Include: Uapi: Add user ABI for Sed/Opal Scott Bauer
2016-12-29 19:26 ` [PATCH v4 2/6] block: Add Sed-opal library Scott Bauer
2016-12-30 21:02   ` Jon Derrick [this message]
2017-01-08 13:32     ` Christoph Hellwig
2017-01-08 14:05   ` Christoph Hellwig
2017-01-11 17:47     ` J Freyensee
2017-01-30 17:08     ` Scott Bauer
2017-01-19 18:28   ` Scott Bauer
2017-01-24  0:20     ` J Freyensee
2017-01-24  7:46     ` Christoph Hellwig
2016-12-29 19:26 ` [PATCH v4 3/6] block: add ioctl interface for interfacing with Opal library Scott Bauer
2017-01-08 14:06   ` Christoph Hellwig
2016-12-29 19:26 ` [PATCH v4 4/6] block: Add Opal Files to Makefile & add config option to Kconfig Scott Bauer
2017-01-08 14:09   ` Christoph Hellwig
2016-12-29 19:26 ` [PATCH v4 5/6] nvme: Add Support for Opal: Unlock from S3 & Opal Allocation/Ioctls Scott Bauer
2017-01-08 14:20   ` Christoph Hellwig
2017-01-18 18:45     ` Keith Busch
2017-01-24  8:14     ` Christoph Hellwig
2017-01-19 19:32   ` Jon Derrick
2016-12-29 19:26 ` [PATCH v4 6/6] Maintainers: Add maintainer info for SED/Opal library Scott Bauer
2016-12-29 21:00 ` [PATCH v4 0/6] SED OPAL Library Scott Bauer
2016-12-30  8:28 ` Christoph Hellwig
2016-12-30 22:52   ` Scott Bauer
2016-12-31  3:51     ` Christoph Hellwig
2016-12-31  5:41       ` Scott Bauer
2016-12-31  5:47         ` Christoph Hellwig
2017-01-03 22:09           ` 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=20161230210255.GA4148@localhost.localdomain \
    --to=jonathan.derrick@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