From: David Brownell <david-b@pacbell.net>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [patch 2.6.23-rc1] dma_free_coherent() needs irqs enabled (sigh)
Date: Tue, 24 Jul 2007 17:35:55 -0700 [thread overview]
Message-ID: <200707241735.55427.david-b@pacbell.net> (raw)
In-Reply-To: <20070724231157.GA30861@flint.arm.linux.org.uk>
On Tuesday 24 July 2007, Russell King wrote:
> > >
> > > I think you got the year wrong:
> > >
> > > 5edf71ae (Russell King 2005-11-25 15:52:51 +0000 364) WARN_ON(irqs_disabled());
> > >
> > > which is due to this commit:
> > >
> > > [ARM] Do not call flush_tlb_kernel_range() with IRQs disabled.
> >
> > This little "to do" list item has been sitting in my mailbox way
> > too long then. Certainly since it was fair to say "last year"! ;)
>
> Are you intentionally not reading what I said?
Hardly. Go back and read what *I* wrote!
It just took a while to notice that behavioral change, since
I don't normally run the relevant regression tests using lockdep.
It was sometime in the first half of 2006, ergo "since it was
fair to say 'last year'".
A bunch of piecemeal workarounds followed; and recently they were
all replaced with a more fundamental fix. This doc patch was the
tail end of the process of recovering from that change ... and the
warnings are there to help other folk from seeing the same issue
in other contexts.
- Dave
next prev parent reply other threads:[~2007-07-25 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 21:29 [patch 2.6.23-rc1] dma_free_coherent() needs irqs enabled (sigh) David Brownell
2007-07-24 22:07 ` Russell King
2007-07-24 23:08 ` David Brownell
2007-07-24 23:11 ` Russell King
2007-07-25 0:35 ` David Brownell [this message]
2007-07-25 10:46 ` Stefan Richter
2007-07-25 17:18 ` [PATCH] firewire: fw-ohci: dma_free_coherent needs IRQs enabled Stefan Richter
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=200707241735.55427.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.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: link
Be 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.