From: Jonathan Nell <crtrn13@gmail.com>
To: linux-scsi@vger.kernel.org
Subject: Re: scsi traffic sniffing
Date: Wed, 2 Sep 2009 15:05:21 +0300 [thread overview]
Message-ID: <48e952f40909020505m7efce7fdif79e4b0b6327f53e@mail.gmail.com> (raw)
In-Reply-To: <d364733c0909020103m41d6781fjad30be856b5f610c@mail.gmail.com>
>> Hmmm kills my pc when loaded into my kernel (2.6.30)... What kernel
>> version did you last use this with?
> O, it's my bad. I don't update the codes.
> Pls try the new attached. It works on the RHEL5 2.6.18-128.el5.
Thanks Xie but still causes a system crash unfortunately...
...I think that maybe the easiest way would be to rebuild the kernel
with aptly-placed prink()s.
But where's the best place to dump? I inserted into
scsi_lib.c:scsi_execute() and that does dump commands, but doesn't
seem to give me what I want. Just to clarify, I am running a dvd-drive
firmware update in a vmware VM (windows xp guest). I have the
dvd-drive (/dev/sr1) connected in the VM as a scsi device. I would
like to print out ALL traffic to /dev/sr1 - whether generated in the
VM or not - and i need both the cmds and the data in both directions.
I'm just not familiar with the scsi kernel code and there's quite a
lot of things going on there so if anyone could tell me where the best
place to put my printk()s in the kernel code would be - that would be
great!
--
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:[~2009-09-02 12:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48e952f40908312312w7765c2a1q3a4f022967735288@mail.gmail.com>
[not found] ` <48e952f40908312313u75e4d00cr3d934f1dbdd1cca9@mail.gmail.com>
2009-09-01 6:13 ` scsi traffic sniffing Jonathan Nell
2009-09-01 10:40 ` 谢纲
2009-09-01 11:19 ` Stefan Richter
2009-09-02 3:12 ` 谢纲
2009-09-02 4:20 ` Jonathan Nell
2009-09-02 4:49 ` 谢纲
2009-09-02 6:48 ` Jonathan Nell
2009-09-02 7:21 ` Xie Gang
2009-09-02 7:50 ` Jonathan Nell
2009-09-02 8:03 ` Xie Gang
2009-09-02 12:05 ` Jonathan Nell [this message]
2009-09-01 16:06 ` Grant Grundler
[not found] ` <48e952f40909010917n7590d364sc4a16317d5e7fb0a@mail.gmail.com>
2009-09-01 16:48 ` Grant Grundler
2009-09-01 16:57 ` Ric Wheeler
2009-09-01 17:13 ` Bart Van Assche
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=48e952f40909020505m7efce7fdif79e4b0b6327f53e@mail.gmail.com \
--to=crtrn13@gmail.com \
--cc=linux-scsi@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