[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150729.152651.331017965932467028.davem@davemloft.net>
Date: Wed, 29 Jul 2015 15:26:51 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: decui@...rosoft.com
Cc: gregkh@...uxfoundation.org, stephen@...workplumber.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
driverdev-devel@...uxdriverproject.org, olaf@...fle.de,
apw@...onical.com, jasowang@...hat.com, kys@...rosoft.com,
pebolle@...cali.nl, stefanha@...hat.com, vkuznets@...hat.com,
dan.carpenter@...cle.com
Subject: Re: [PATCH V4 4/7] Drivers: hv: vmbus: add APIs to register
callbacks to process hvsock connection
From: Dexuan Cui <decui@...rosoft.com>
Date: Tue, 28 Jul 2015 05:35:11 -0700
> With the 2 APIs supplied by the VMBus driver, the coming net/hvsock driver
> can register 2 callbacks and can know when a new hvsock connection is
> offered by the host, and when a hvsock connection is being closed by the
> host.
>
> Signed-off-by: Dexuan Cui <decui@...rosoft.com>
This is an extremely terrible interface.
It's an opaque hook that allows on registry, and it's solve purpose
is to allow a backdoor call into a foreign driver in another module.
These are exactly the things we try to avoid.
Why not create a real abstraction where clients register an object,
that can be contained as a sub-member inside of their own driver
private, that provides the callback registry mechanism.
That way you can register multiple clients, do things like allow
AF_PACKET capturing of vmbus traffic, etc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists