public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: James.Bottomley@HansenPartnership.com, mingo@elte.hu,
	linux-driver@qlogic.com, linux-scsi@vger.kernel.org,
	akpm@linux-foundation.org
Subject: Re: [PATCH] qla2xxx: firmware semaphore to mutex
Date: Mon, 28 Apr 2008 12:21:58 -0700	[thread overview]
Message-ID: <1209410518.12461.71.camel@localhost.localdomain> (raw)
In-Reply-To: <20080428190425.GY14990@parisc-linux.org>


On Mon, 2008-04-28 at 13:04 -0600, Matthew Wilcox wrote:
> it returns -EINTR and it's
> up to the caller to handle it and unwind back to userspace.  ie it's
> halfway between mutex_lock_interruptible() (any signal) and
> mutex_lock()
> (no signal).


In the hunk you quoted (below),

> > -       down(&qla_fw_lock);
> > +       if (mutex_lock_killable(&qla_fw_lock))
> > +               return NULL;

Don't you need to return the -EINTR so the caller knows the nature of
the failure? You might also need to re-factor the caller of this
function so it properly reports the failure to userspace .. In this case
your just returning NULL .. 

(CC'd Andrew since I think this was something he was concerned about,
with mutex_lock_interruptible().)

Daniel


  reply	other threads:[~2008-04-28 19:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 17:47 [PATCH] qla2xxx: firmware semaphore to mutex Daniel Walker
2008-04-28 18:08 ` Matthew Wilcox
2008-04-28 18:57   ` Daniel Walker
2008-04-28 19:04     ` Matthew Wilcox
2008-04-28 19:21       ` Daniel Walker [this message]
2008-04-28 19:24         ` Matthew Wilcox
2008-04-28 19:33           ` Ingo Molnar
2008-04-28 19:54           ` Daniel Walker
2008-04-28 20:55 ` Andrew Vasquez

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=1209410518.12461.71.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-driver@qlogic.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mingo@elte.hu \
    /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