public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k <linux-m68k@vger.kernel.org>
Subject: Re: Fwd: [PATCH] [RFC] ataflop: remove buggy IRQ disable from do_fd_request()
Date: Mon, 12 Oct 2009 09:58:50 +0200	[thread overview]
Message-ID: <20091012075850.GX9228@kernel.dk> (raw)
In-Reply-To: <alpine.DEB.2.00.0910110846420.20140@zirkon.biophys.uni-duesseldorf.de>

On Sun, Oct 11 2009, Michael Schmitz wrote:
> Hi Geert,
> 
> > There is a nice gem in drivers/block/ataflop.c::do_fd_request()
> > 
> > 	void do_fd_request(struct request_queue * q)
> > 	{
> > 		unsigned long flags;
> > 
> > 		DPRINT(("do_fd_request for pid %d\n",current->pid));
> > 		while( fdc_busy ) sleep_on( &fdc_wait );
> > 		fdc_busy = 1;
> > 		stdma_lock(floppy_irq, NULL);
> > 
> > 		atari_disable_irq( IRQ_MFP_FDC );
> > 		local_save_flags(flags);        /* The request function is called with ints
> > 		local_irq_disable();             * disabled... so must save the IPL
> > for later */
> > 		redo_fd_request();
> > 		local_irq_restore(flags);
> > 		atari_enable_irq( IRQ_MFP_FDC );
> > 	}
> > 
> > If you look at the code long enough, you will notioce that the
> > local_irq_disable() call is actually commented out. This has been
> > introduced back in 2002 in [1], but as you can see, the same bug has been
> > there even before, with the sti() call being commented out in the very
> > same way :)
> > 
> > I am not familiar with the code myself at all, but I guess that the whole
> > stuff can just be removed. Why do we need save_flags/restore_flags at all,
> > without actually disabling the local IRQs afterwards? The
> 
> The IRQ source has been disabled in the MFC by the atari_disable_irq(
> IRQ_MFP_FDC ) call just before local_save_flags(flags).  For that
> reason, the fact that local_irq_disable is commented out will not
> usually matter (a timer interrupt that would result in retrying the
> floppy request or removing the request from the queue excepted).
> 
> I would rather suggest to leave the code in, and fix the buggy
> comments instead.

What buggy comments? The comments states that interrupts are already
disabled when entering this function, which is correct. The point is
that doing a flags save and then an irq disable is pointless, since we
KNOW that interrupts are already disabled.

-- 
Jens Axboe


  reply	other threads:[~2009-10-12  7:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LSU.2.00.0910091141150.19284@wotan.suse.de>
2009-10-10  9:01 ` Fwd: [PATCH] [RFC] ataflop: remove buggy IRQ disable from do_fd_request() Geert Uytterhoeven
2009-10-11  7:01   ` Michael Schmitz
2009-10-12  7:58     ` Jens Axboe [this message]
2009-10-18  8:24       ` Michael Schmitz
2009-10-12  9:19     ` Jiri Kosina
     [not found]     ` <alpine.LSU.2.00.0910121106330.19284@wotan.suse.de>
2009-10-18 21:14       ` Michael Schmitz
2009-10-19  7:35         ` Jiri Kosina
2009-10-20  6:51           ` Michael Schmitz
     [not found]           ` <alpine.DEB.2.00.0910200847320.8658@zirkon.biophys.uni-duesseldorf.de>
2009-10-20  9:24             ` Andreas Schwab
2009-10-31  3:58               ` Michael Schmitz

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=20091012075850.GX9228@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schmitz@biophys.uni-duesseldorf.de \
    /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