From: Luben Tuikov <ltuikov@yahoo.com>
To: Greg KH <greg@kroah.com>
Cc: Matthew Wilcox <willy@linux.intel.com>,
linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] [USB] UAS: eliminate infinite loop; add debug print
Date: Mon, 8 Nov 2010 09:57:48 -0800 (PST) [thread overview]
Message-ID: <513136.91622.qm@web31804.mail.mud.yahoo.com> (raw)
In-Reply-To: <20101108173808.GA13326@kroah.com>
--- On Mon, 11/8/10, Greg KH <greg@kroah.com> wrote:
> On Mon, Nov 08, 2010 at 09:27:22AM
> -0800, Luben Tuikov wrote:
> > --- On Mon, 11/8/10, Matthew Wilcox <willy@linux.intel.com>
> wrote:
> > > -0700, Luben Tuikov wrote:
> > > > Eliminate an infinite loop whereby the SCSI
> layer
> > > > would reissue a command (which would be
> failed by
> > > > the driver) ad infinitum. (Invariably due to
> the
> > > > driver's profuse use of the
> > > > SCSI_MLQUEUE_DEVICE_BUSY returned result in
> its
> > > > queuecommand() method.)
> > > >
> > > > Also add a debug option and a few debug
> prints.
> > >
> > > Why have you added your own debug scheme instead
> of using
> > > dev_dbg?
> >
> > Because, this debug "scheme" produces copious and
> otherwise
> > unnecessary volume of debug information in a working
> driver. And
> > because you can turn it on/off just for this driver.
> It is intended to
> > be used only for debugging this driver and the UAS
> device(s) to which
> > the driver communicates. 99.9% of the time, this
> setting will be a 'N'
> > out there. And this is what the Kconfig help
> entry says: "If unsure,
> > say 'N'."
>
> dev_dbg() is able to be turned on and off dynamically when
> the kernel is
> running without rebuilding anything, which is what you
> really want to
> have happen for a driver being used by normal users.
>
> It also produces the output in a standard manner that we
> have all agreed
> to follow.
I'll modify the code in my tree and resubmit what I have now using dev_dbg. I'll also integrate the hint from Michal.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-08 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 0:33 [PATCH] [USB] UAS: eliminate infinite loop; add debug print Luben Tuikov
2010-11-03 16:24 ` Greg KH
2010-11-08 11:24 ` Matthew Wilcox
2010-11-08 15:55 ` Greg KH
2010-11-08 17:27 ` Luben Tuikov
[not found] ` <272723.33242.qm-5Es2LHxk9sSvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-11-08 17:38 ` Greg KH
2010-11-08 17:57 ` Luben Tuikov [this message]
2010-11-08 17:40 ` Michał Nazarewicz
-- strict thread matches above, loose matches on Subject: below --
2010-12-10 10:51 Luben Tuikov
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=513136.91622.qm@web31804.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=greg@kroah.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=willy@linux.intel.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 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.