From: Borislav Petkov <petkovbb@googlemail.com>
To: David Miller <davem@davemloft.net>
Cc: bzolnier@gmail.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] ide-tape: misc stuff
Date: Thu, 16 Jul 2009 08:52:33 +0200 [thread overview]
Message-ID: <20090716065233.GA7242@liondog.tnic> (raw)
In-Reply-To: <20090715.124150.120992830.davem@davemloft.net>
On Wed, Jul 15, 2009 at 12:41:50PM -0700, David Miller wrote:
> From: Borislav Petkov <petkovbb@googlemail.com>
> Date: Wed, 15 Jul 2009 20:43:50 +0200
>
> > Well, the downside to that is whenever there's a bug report and I want
> > the user to do a debug build and send me the output, I'll have to rehash
> > that debug patch and send it to her/him, maybe teach her/him how to
> > patch a kernel, build it and catch the output and send it my way before
> > we do some real work. Having the change upstream makes it _a_ _lot_
> > _more_ easier to do that and this is experience talking, we had several
> > scenarious like that already.
>
> Your PFX patch has no effect at all, it's just cleanup noise.
Yes, that one I don't need, I can drop it.
> The other patch moves the debug mask from one place to another,
> why can't the debug selections bet set properly as is?
Where the debug_mask is set is all the same to me, its the additional
information added to the debug calls that I care about. I don't mention
that in the commit message which is my bad, sorry, will fix. With those
you can actually follow what happens, for example:
[ 51.945800] ide-tape: ide_tape_get_bsize_from_bdesc: blk_size: 512, write_prot: 0
[ 51.945821] ide-tape: idetape_chrdev_ioctl: cmd: 0x40086d01
[ 51.945826] ide-tape: idetape_mtioctop: MTIOCTOP ioctl: mt_op: 13, mt_count: 1
[ 51.945830] ide-tape: idetape_rewind_tape: enter
[ 51.945843] ide-tape: idetape_do_request: cmd: 0x1, sector: 4294967295, nr_sectors: 0
Those debug calls were simply not there/not complete wrt to the
information they were dumping because nobody had an ide-tape to play
with. After I got one and started debugging, I've added that missing
information which made a dbg output more understandable (e.g. request
cmd, args the ioctl is being called with, etc.)
This is the only reason for that change and because it doesn't break
anything but helps a whole lot when debugging, it's a win-win thing and
that's why I advocate its inclusion so vehemently :).
Thanks.
--
Regards/Gruss,
Boris.
prev parent reply other threads:[~2009-07-16 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 15:18 Borislav Petkov
2009-07-15 15:18 ` [PATCH 1/4] ide-tape: fix debug call Borislav Petkov
2009-07-15 15:18 ` [PATCH 2/4] ide-tape: use PFX to all printks Borislav Petkov
2009-07-15 15:18 ` [PATCH 3/4] ide-tape: convert to ide_debug_log macro Borislav Petkov
2009-07-15 15:18 ` [PATCH 4/4] ide-tape: fix handling of postponed rqs Borislav Petkov
2009-07-15 18:16 ` [PATCH 0/4] ide-tape: misc stuff David Miller
2009-07-15 18:43 ` Borislav Petkov
2009-07-15 19:41 ` David Miller
2009-07-16 6:52 ` Borislav Petkov [this message]
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=20090716065233.GA7242@liondog.tnic \
--to=petkovbb@googlemail.com \
--cc=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®