summaryrefslogtreecommitdiffstats
path: root/net/x25/x25_out.c
diff options
context:
space:
mode:
authorNeil Horman <nhorman@tuxdriver.com>2011-06-15 05:25:01 +0000
committerDavid S. Miller <davem@conan.davemloft.net>2011-06-16 23:53:10 -0400
commitbebd097a0af8bd6c51f50a65f3a435019b0e906a (patch)
tree22215109ca9499577da0690f84c7b691ee8e6df7 /net/x25/x25_out.c
parentae6e86b7fb15520ac64513ad643de63e0b077aa5 (diff)
downloadlinux-bebd097a0af8bd6c51f50a65f3a435019b0e906a.tar.gz
linux-bebd097a0af8bd6c51f50a65f3a435019b0e906a.tar.bz2
linux-bebd097a0af8bd6c51f50a65f3a435019b0e906a.zip
tun: teach the tun/tap driver to support netpoll
Commit 8d8fc29d02a33e4bd5f4fa47823c1fd386346093 changed the behavior of slave devices in regards to netpoll. Specifically it created a mutually exclusive relationship between being a slave and a netpoll-capable device. This creates problems for KVM because guests relied on needing netconsole active on a slave device to a bridge. Ideally libvirtd could just attach netconsole to the bridge device instead, but thats currently infeasible, because while the bridge device supports netpoll, it requires that all slave interface also support it, but the tun/tap driver currently does not. The most direct solution is to teach tun/tap to support netpoll, which is implemented by the patch below. I've not tested this yet, but its pretty straightforward. Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Reported-by: Rik van Riel <riel@redhat.com> CC: Rik van Riel <riel@redhat.com> CC: Maxim Krasnyansky <maxk@qualcomm.com> CC: Cong Wang <amwang@redhat.com> CC: "David S. Miller" <davem@davemloft.net> Reviewed-by: Rik van Riel <riel@redhat.com> Tested-by: Rik van Riel <riel@redhat.com> Reviewed-by: WANG Cong <amwang@redhat.com> Signed-off-by: David S. Miller <davem@conan.davemloft.net>
Diffstat (limited to 'net/x25/x25_out.c')
0 files changed, 0 insertions, 0 deletions