Displaying 7 results from an estimated 7 matches for "netdev_warn_once".
2014 Oct 30
0
[PATCH v2 net 1/2] drivers/net: Disable UFO through virtio
...wrote:
> + {
> + static bool warned;
> +
> + if (!warned) {
> + warned = true;
> + netdev_warn(tun->dev,
> + "%s: using disabled UFO feature; please fix this program\n",
> + current->comm);
> + }
>
It might be time to add netdev_warn_once() ;)
Alternatively, you could use
pr_warn_once("%s: using disabled UFO feature; please fix this program\n",
tun->dev->name, current->comm);
2014 Oct 30
1
[PATCH v2 net 1/2] drivers/net: Disable UFO through virtio
...t; > +
> > + if (!warned) {
> > + warned = true;
> > + netdev_warn(tun->dev,
> > + "%s: using disabled UFO feature; please fix this program\n",
> > + current->comm);
> > + }
> >
>
> It might be time to add netdev_warn_once() ;)
Could do. I'm trying to make small fixes that are suitable for stable.
> Alternatively, you could use
> pr_warn_once("%s: using disabled UFO feature; please fix this program\n",
> tun->dev->name, current->comm);
That's missing a "%s: "...
2014 Oct 30
1
[PATCH v2 net 1/2] drivers/net: Disable UFO through virtio
...t; > +
> > + if (!warned) {
> > + warned = true;
> > + netdev_warn(tun->dev,
> > + "%s: using disabled UFO feature; please fix this program\n",
> > + current->comm);
> > + }
> >
>
> It might be time to add netdev_warn_once() ;)
Could do. I'm trying to make small fixes that are suitable for stable.
> Alternatively, you could use
> pr_warn_once("%s: using disabled UFO feature; please fix this program\n",
> tun->dev->name, current->comm);
That's missing a "%s: "...
2014 Oct 30
3
[PATCH v2 net 1/2] drivers/net: Disable UFO through virtio
IPv6 does not allow fragmentation by routers, so there is no
fragmentation ID in the fixed header. UFO for IPv6 requires the ID to
be passed separately, but there is no provision for this in the virtio
net protocol.
Until recently our software implementation of UFO/IPv6 generated a new
ID, but this was a bug. Now we will use ID=0 for any UFO/IPv6 packet
passed through a tap, which is even
2014 Oct 30
3
[PATCH v2 net 1/2] drivers/net: Disable UFO through virtio
IPv6 does not allow fragmentation by routers, so there is no
fragmentation ID in the fixed header. UFO for IPv6 requires the ID to
be passed separately, but there is no provision for this in the virtio
net protocol.
Until recently our software implementation of UFO/IPv6 generated a new
ID, but this was a bug. Now we will use ID=0 for any UFO/IPv6 packet
passed through a tap, which is even
2014 Oct 30
5
[PATCH v2 net 0/2] drivers/net,ipv6: Fix IPv6 fragment ID selection for virtio
The virtio net protocol supports UFO but does not provide for passing a
fragment ID for fragmentation of IPv6 packets. We used to generate a
fragment ID wherever such a packet was fragmented, but currently we
always use ID=0!
v2: Add blank lines after declarations
Ben.
Ben Hutchings (2):
drivers/net: Disable UFO through virtio
drivers/net,ipv6: Select IPv6 fragment idents for virtio UFO
2014 Oct 30
5
[PATCH v2 net 0/2] drivers/net,ipv6: Fix IPv6 fragment ID selection for virtio
The virtio net protocol supports UFO but does not provide for passing a
fragment ID for fragmentation of IPv6 packets. We used to generate a
fragment ID wherever such a packet was fragmented, but currently we
always use ID=0!
v2: Add blank lines after declarations
Ben.
Ben Hutchings (2):
drivers/net: Disable UFO through virtio
drivers/net,ipv6: Select IPv6 fragment idents for virtio UFO