mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Gabriele Brugnoni <news@dveprojects.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: interruptible_sleep_on, interrupts and device drivers
Date: Sat, 15 Oct 2005 12:36:29 +0200	[thread overview]
Message-ID: <1129372589.2908.8.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200510151229.37124.news@dveprojects.com>

On Sat, 2005-10-15 at 12:29 +0200, Gabriele Brugnoni wrote:
> Arjan van de Ven wrote:
> 
> > 
> > don't.
> > 
> > interruptible_sleep_on() is a broken interface (see the comments in the
> > header) and should not be used in any new code (where "new" is "since
> > the year 2000" :)
> > 
> > Just use the wait_event() interfaces .... or just a simple semaphore
> > even if what you want to do is simple and performance isn't too
> > critical.
> > 
> 
> OK, i'll not use, but the kernel has a lot of device drivers using it, that 
> may present the problem explained in my message.
> 
> In my code i've try the following:
> 
> 		save_flags(flags); cli();

this is broken code; cli() cannot and should not be used. (and isn't
even available on SMP kernels anymore)

> 		if( !rs.txdone ) {
> 			if( arg < 0 ) arg = rs.ttimeout;
> 			if( arg > 0 )
> 				interruptible_sleep_on_timeout ( &rs.txwait, arg );
> 			else
> 				interruptible_sleep_on ( &rs.txwait );
> 		}
> 		restore_flags(flags);

and this is missing a sti()

> 		return rs.txdone;


your code is just wrong. Yes I know many really old drivers do this, but
those are getting extinct fast..


  reply	other threads:[~2005-10-15 10:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 10:29 Gabriele Brugnoni
2005-10-15 10:36 ` Arjan van de Ven [this message]
2005-10-15 10:57   ` Russell King
     [not found] <4XQZI-5QC-1@gated-at.bofh.it>
2005-10-15 20:21 ` Robert Hancock
  -- strict thread matches above, loose matches on Subject: below --
2005-10-15 10:00 Gabriele Brugnoni
2005-10-15 10:05 ` Arjan van de Ven
2005-10-15 13:01 ` Tushar Adeshara

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=1129372589.2908.8.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=news@dveprojects.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

all inboxes | Powered by JetHome®