linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Joshua Hoblitt <josh@hoblitt.com>,
	Kim H?jgaard-Hansen <kimhh@control.aau.dk>,
	erich@areca.com.tw, linux-scsi@vger.kernel.org,
	j_gentoo@hoblitt.com, nick.cheng@areca.com.tw
Subject: Re: arcmsr + archttp64 calls dma_free_coherent() with irqs   disabled - dmesg filled with warnings
Date: Sat, 16 Feb 2008 23:36:44 +0000	[thread overview]
Message-ID: <47B7738C.9050107@gentoo.org> (raw)
In-Reply-To: <1203173535.3182.11.camel@localhost.localdomain>

James Bottomley wrote:
> On Sat, 2008-02-16 at 11:49 +0000, Daniel Drake wrote:
>> I assume you're aware that this patch is just a subset of commit 
>> 76d78300a6eb8 which you've already pushed up to Linus. Adding Nick Cheng 
>> (commit author) to CC so that he can go over the feedback.
> 
> Well, in case it's not obvious by now:  The way to get bad code upstream
> is to send a patch that combines many changes (the more the better) so
> that any potential reviewer has no idea which change is meant by which
> hunk and then to make sure Andrew picks it up so he'll hound the
> subsystem Maintainer until it's applied.  Best of all, mention that it
> fixes a bug and you're made.

Sorry, I didn't mean to sound that as a criticism. I'm sure you have a 
lot of patches flowing by you at any one time.

Here is a patch to address your comments.
Joshua, would you mind testing this before I submit it properly? It will 
apply cleanly to 2.6.24 on top of the previous patch you tested. I have 
compile-tested it.

> The odd thing is, it should have triggered a might_sleep() warning under
> testing ... do you know why it didn't?

No, and I can see that scsi_dispatch_command does invoke ->queuecommand 
under a spinlock so it must be atomic context...
I'm not sure which might_sleep() codepath you are looking at though. At 
a guess it depends on SLUB vs SLAB?

Daniel

  reply	other threads:[~2008-02-16 23:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 15:31 arcmsr + archttp64 calls dma_free_coherent() with irqs disabled - dmesg filled with warnings Kim Højgaard-Hansen
2008-02-09 18:01 ` James Bottomley
2008-02-09 19:35   ` Joshua Hoblitt
2008-02-09 19:43     ` James Bottomley
2008-02-12 20:53       ` Joshua Hoblitt
2008-02-12 22:21         ` Joshua Hoblitt
2008-02-12 22:30           ` James Bottomley
2008-02-13  2:08             ` arcmsr + archttp64 calls dma_free_coherent() with irqsdisabled " nickcheng
2008-02-15 20:56             ` arcmsr + archttp64 calls dma_free_coherent() with irqs disabled " Joshua Hoblitt
2008-02-15 21:57               ` James Bottomley
2008-02-15 22:04                 ` James Bottomley
2008-02-16 11:49                   ` Daniel Drake
2008-02-16 14:52                     ` James Bottomley
2008-02-16 23:36                       ` Daniel Drake [this message]
2008-02-16 23:37                         ` Daniel Drake
2008-02-17  1:15                           ` Joshua Hoblitt
2008-02-19 20:38                           ` Joshua Hoblitt
2008-02-13 12:55           ` Daniel Drake

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=47B7738C.9050107@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=erich@areca.com.tw \
    --cc=j_gentoo@hoblitt.com \
    --cc=josh@hoblitt.com \
    --cc=kimhh@control.aau.dk \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nick.cheng@areca.com.tw \
    /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;
as well as URLs for NNTP newsgroup(s).