linux-kernel - Re: [PULL] vhost: tcm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Mar 2013 16:05:23 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	mst@...hat.com
Cc:	kvm@...r.kernel.org, virtualization@...ts.osdl.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	asias@...hat.com, nab@...ux-iscsi.org, target-devel@...r.kernel.org
Subject: Re: [PULL] vhost: tcm_vhost fixes for 3.9

From: "Michael S. Tsirkin" <mst@...hat.com>
Date: Mon, 18 Mar 2013 21:54:43 +0200

> On Mon, Mar 18, 2013 at 01:01:36PM -0400, David Miller wrote:
>> From: "Michael S. Tsirkin" <mst@...hat.com>
>> Date: Mon, 18 Mar 2013 13:20:03 +0200
>> 
>> > The following changes since commit 8c6216d7f118a128678270824b6a1286a63863ca:
>> > 
>> >   Revert "ip_gre: make ipgre_tunnel_xmit() not parse network header as IP unconditionally" (2013-03-16 23:00:41 -0400)
>> > 
>> > are available in the git repository at:
>> > 
>> >   git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-net
>> > 
>> > for you to fetch changes up to deb7cb067dabd3be625eaf5495da8bdc97377fc1:
>> > 
>> >   tcm_vhost: Flush vhost_work in vhost_scsi_flush() (2013-03-17 13:04:14 +0200)
>> 
>> This is a scsi driver, I therefore don't think this pull request is for me.
>> 
>> Please avoid such confusion in the future, and don't use branch names
>> like "vhost-net" for SCSI driver fixes.
>> 
>> Thanks.
> 
> We are sharing quite a bit of code, so it's a common tree.
> There was a vhost-net patch there too but you picked it up
> directly so I dropped that and what's left is vhost-scsi.
> Typically vhost-net dominates so I'm just used to merging all vhost
> things through you but if you think it's wrong I can send it directly to
> Linus.

Just like any other "bus" or "layer" for drivers, you should
really just send the networking bits my way.

Now, in situations where some generic vhost infrastructure is
necessary for a vhost-net specific change, that might be a
situation where we can merge the infrastructure change into
my tree so that the networking bits can go in too.
--
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/