From: Matthew Wilcox <matthew@wil.cx>
To: James Smart <James.Smart@Emulex.Com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC] FC Transport : Async Events via netlink interface
Date: Wed, 19 Apr 2006 08:59:31 -0600 [thread overview]
Message-ID: <20060419145931.GL24104@parisc-linux.org> (raw)
In-Reply-To: <1145306661.4151.0.camel@localhost.localdomain>
On Mon, Apr 17, 2006 at 04:44:21PM -0400, James Smart wrote:
> PS: Comments on Kconfig change appreciated. I don't have much experience on
> changing the kernel config and build process.
>
> diff -upNr a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
> --- a/drivers/scsi/Kconfig 2006-03-29 11:53:24.000000000 -0500
> +++ b/drivers/scsi/Kconfig 2006-04-17 12:03:31.000000000 -0400
> @@ -221,7 +221,7 @@ config SCSI_SPI_ATTRS
>
> config SCSI_FC_ATTRS
> tristate "FiberChannel Transport Attributes"
> - depends on SCSI
> + depends on SCSI && NET && NETFILTER && NETFILTER_NETLINK
> help
> If you wish to export transport-specific information about
> each attached FiberChannel device to sysfs, say Y.
I would use a select here rather than a depends. So enabling a driver
that uses FC_ATTRS will force netlink to be added. However, I think you
have the wrong symbols here. NETFILTER_NETLINK is the netlink interface
for netfilter -- entirely unrelated. It looks like you only need to
enable NET in order to force netlink to be built. So something like
this would be enough:
config SCSI_FC_ATTRS
tristate "FiberChannel Transport Attributes"
depends on SCSI
+ select NET
help
If you wish to export transport-specific information about
each attached FiberChannel device to sysfs, say Y.
> +#define get_list_head_entry(pos, head, member) \
> + pos = list_entry((head)->next, typeof(*pos), member)
> +
This one sets alarm bells ringing ...
> static void __exit fc_transport_exit(void)
> {
> + struct fc_nl_user *nluser;
> +
> + sock_release(fc_nl_sock->sk_socket);
> + netlink_unregister_notifier(&fc_netlink_notifier);
> + while (!list_empty(&fc_nl_user_list)) {
> + get_list_head_entry(nluser, &fc_nl_user_list, ulist);
> + list_del(&nluser->ulist);
> + kfree(nluser);
> + }
> transport_class_unregister(&fc_transport_class);
> transport_class_unregister(&fc_rport_class);
> transport_class_unregister(&fc_host_class);
I would write this as:
struct fc_nl_user *nluser, *tmp;
list_for_each_entry_safe(nluser, tmp, &fc_nl_user_list, ulist) {
kfree(nluser);
}
next prev parent reply other threads:[~2006-04-19 14:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 20:44 [RFC] FC Transport : Async Events via netlink interface James Smart
2006-04-18 16:01 ` Mike Anderson
2006-04-19 12:52 ` James Smart
2006-04-19 12:57 ` [RFC] Netlink and user-space buffer pointers James Smart
2006-04-19 16:22 ` Patrick McHardy
2006-04-19 17:08 ` James Smart
2006-04-19 17:16 ` Patrick McHardy
2006-04-19 16:26 ` Stephen Hemminger
2006-04-19 17:05 ` James Smart
2006-04-19 21:32 ` Mike Christie
2006-04-20 14:33 ` James Smart
2006-04-20 17:45 ` Mike Christie
2006-04-20 17:52 ` Mike Christie
2006-04-20 17:58 ` Mike Christie
2006-04-20 20:03 ` James Smart
2006-04-20 20:35 ` Mike Christie
2006-04-20 20:40 ` Mike Christie
2006-04-20 21:41 ` Mike Christie
2006-04-20 21:51 ` Mike Christie
2006-04-20 23:07 ` Mike Christie
2006-04-20 23:44 ` Andrew Vasquez
2006-04-20 20:18 ` Douglas Gilbert
2006-04-19 14:59 ` Matthew Wilcox [this message]
2006-04-19 16:11 ` [RFC] FC Transport : Async Events via netlink interface James Smart
-- strict thread matches above, loose matches on Subject: below --
2006-04-17 22:46 Moore, Eric
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=20060419145931.GL24104@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Smart@Emulex.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;
as well as URLs for NNTP newsgroup(s).