From: David Miller <davem@davemloft.net>
To: ebiederm@xmission.com
Cc: netdev@vger.kernel.org, James.Bottomley@parallels.com,
James.Smart@Emulex.Com
Subject: Re: [PATCH] scsi_netlink: Remove dead and buggy code
Date: Sat, 08 Sep 2012 18:51:05 -0400 (EDT) [thread overview]
Message-ID: <20120908.185105.2033125004492160106.davem@davemloft.net> (raw)
In-Reply-To: <87pq5xjw4m.fsf@xmission.com>
From: ebiederm@xmission.com (Eric W. Biederman)
Date: Fri, 07 Sep 2012 15:39:21 -0700
>
> The scsi netlink code confuses the netlink port id with a process id,
> going so far as to read NETLINK_CREDS(skb)->pid instead of the correct
> NETLINK_CB(skb).pid. Fortunately it does not matter because nothing
> registers to respond to scsi netlink requests.
>
> The only interesting use of the scsi_netlink interface is
> fc_host_post_vendor_event which sends a netlink multicast message.
>
> Since nothing registers to handle scsi netlink messages kill all of the
> registration logic, while retaining the same error handling behavior
> preserving the userspace visible behavior and removing all of the
> confused code that thought a netlink port id was a process id.
>
> This was tested with a kernel allyesconfig build which had no problems.
>
> Cc: James Bottomley <James.Bottomley@parallels.com>
> Cc: James Smart <James.Smart@Emulex.Com>
> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Yeah I can't see anyone, anywhere, using these scsi_send_nl_*()
interfaces at all.
When I get an ACK from the scsi folks I'll add this to net-next,
thanks Eric.
next prev parent reply other threads:[~2012-09-08 22:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 22:39 [PATCH] scsi_netlink: Remove dead and buggy code Eric W. Biederman
2012-09-08 22:51 ` David Miller [this message]
2012-09-10 19:07 ` David Miller
2012-09-10 22:07 ` James Bottomley
2012-09-11 22:40 ` Eric W. Biederman
2012-09-11 22:48 ` David Miller
2012-09-13 20:24 ` David Miller
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=20120908.185105.2033125004492160106.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@parallels.com \
--cc=James.Smart@Emulex.Com \
--cc=ebiederm@xmission.com \
--cc=netdev@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).