From: Christoph Hellwig <hch@infradead.org>
To: jd <jpd_hp_linux_scsi@yahoo.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: 1st REVIEW : UNH iSCSI for 2.6-test5
Date: Thu, 25 Sep 2003 09:19:49 +0100 [thread overview]
Message-ID: <20030925091949.A6827@infradead.org> (raw)
In-Reply-To: <20030924151228.8206.qmail@web60208.mail.yahoo.com>; from jpd_hp_linux_scsi@yahoo.com on Wed, Sep 24, 2003 at 08:12:28AM -0700
More comments:
- unh_iscsi/security should really go away. We have a nice crypto API
in 2.6 and late 2.4, but authentification really shouldn't be done
in kernelspace anyway.
- kill iscsi_device.c. A scsi LLDD has no business messing with device
nodes..
- you're comment style is strange. In kernel code we tend to use
/*
* Foo, blah
* baz..
*/
not
/*
*/
but that's just a minor nitpick.
Having the module description over the copyright boilerplate also is
very strange.
- your split into common/ and initiator/ is strange. You can build
multiple modules in one directory and that would cleanup your
includes mess nicely
- having a single host for all of iscsi looks strange. Why do you
do that?
- the #ifdef K26 is totally unreadble. Especially when it's around
code that works for both 2.4 and 2.6..
- kill my_kmallocd / my_free
- you seems to not handle lots of error returns, e.g. from down_interruptible
or kernel_thread
- the UNH_LOCK/UNH_UNLOCK obsfucation hinders reading
- kill ISCSI_INITIATOR, there's no need for this #define - just initialize
the host template directly
next prev parent reply other threads:[~2003-09-25 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 15:12 1st REVIEW : UNH iSCSI for 2.6-test5 jd
2003-09-24 16:09 ` Jeff Garzik
2003-09-26 11:27 ` jd
2003-10-01 19:34 ` jd
2003-09-24 17:39 ` Christoph Hellwig
2003-09-24 17:48 ` Christoph Hellwig
2003-09-25 8:19 ` Christoph Hellwig [this message]
2003-09-26 11:17 ` jd
2003-10-01 19:19 ` 1st REVIEW : UNH iSCSI for 2.6-test5 - Questions jd
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=20030925091949.A6827@infradead.org \
--to=hch@infradead.org \
--cc=jpd_hp_linux_scsi@yahoo.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