Searched hist:12932 (Results 1 - 1 of 1) sorted by relevance
| /netbsd-current/sys/net/ | ||
| H A D | if_vlan.c | diff 1.41 Thu Jul 08 19:09:12 MDT 2004 mycroft If the parent interface is not IFF_RUNNING, do not call its start function. This prevent a variety of fun panics, and therefore fixes PR 12932, PR 17561, and PR 18376... XXX ...however this is most definitely a hack. The real problem here is that there is no callback to notify a "client" interface like vlan when a "parent" interface's status changes, and therefore the vlan interface is always IFF_RUNNING. This allows packets to be queued on vlan interface at any time. We can't simply leave the packets on the vlan interface, either, because there is no callback to dequeue them. And last, since it's always IFF_RUNNING, if we just *toss* the packets, we lose gratuitous ARPs and DAD packets. "This needs work," but at least it no longer bleeds. diff 1.41 Thu Jul 08 19:09:12 MDT 2004 mycroft If the parent interface is not IFF_RUNNING, do not call its start function. This prevent a variety of fun panics, and therefore fixes PR 12932, PR 17561, and PR 18376... XXX ...however this is most definitely a hack. The real problem here is that there is no callback to notify a "client" interface like vlan when a "parent" interface's status changes, and therefore the vlan interface is always IFF_RUNNING. This allows packets to be queued on vlan interface at any time. We can't simply leave the packets on the vlan interface, either, because there is no callback to dequeue them. And last, since it's always IFF_RUNNING, if we just *toss* the packets, we lose gratuitous ARPs and DAD packets. "This needs work," but at least it no longer bleeds. diff 1.41 Thu Jul 08 19:09:12 MDT 2004 mycroft If the parent interface is not IFF_RUNNING, do not call its start function. This prevent a variety of fun panics, and therefore fixes PR 12932, PR 17561, and PR 18376... XXX ...however this is most definitely a hack. The real problem here is that there is no callback to notify a "client" interface like vlan when a "parent" interface's status changes, and therefore the vlan interface is always IFF_RUNNING. This allows packets to be queued on vlan interface at any time. We can't simply leave the packets on the vlan interface, either, because there is no callback to dequeue them. And last, since it's always IFF_RUNNING, if we just *toss* the packets, we lose gratuitous ARPs and DAD packets. "This needs work," but at least it no longer bleeds. diff 1.41 Thu Jul 08 19:09:12 MDT 2004 mycroft If the parent interface is not IFF_RUNNING, do not call its start function. This prevent a variety of fun panics, and therefore fixes PR 12932, PR 17561, and PR 18376... XXX ...however this is most definitely a hack. The real problem here is that there is no callback to notify a "client" interface like vlan when a "parent" interface's status changes, and therefore the vlan interface is always IFF_RUNNING. This allows packets to be queued on vlan interface at any time. We can't simply leave the packets on the vlan interface, either, because there is no callback to dequeue them. And last, since it's always IFF_RUNNING, if we just *toss* the packets, we lose gratuitous ARPs and DAD packets. "This needs work," but at least it no longer bleeds. diff 1.41 Thu Jul 08 19:09:12 MDT 2004 mycroft If the parent interface is not IFF_RUNNING, do not call its start function. This prevent a variety of fun panics, and therefore fixes PR 12932, PR 17561, and PR 18376... XXX ...however this is most definitely a hack. The real problem here is that there is no callback to notify a "client" interface like vlan when a "parent" interface's status changes, and therefore the vlan interface is always IFF_RUNNING. This allows packets to be queued on vlan interface at any time. We can't simply leave the packets on the vlan interface, either, because there is no callback to dequeue them. And last, since it's always IFF_RUNNING, if we just *toss* the packets, we lose gratuitous ARPs and DAD packets. "This needs work," but at least it no longer bleeds. diff 1.41 Thu Jul 08 19:09:12 MDT 2004 mycroft If the parent interface is not IFF_RUNNING, do not call its start function. This prevent a variety of fun panics, and therefore fixes PR 12932, PR 17561, and PR 18376... XXX ...however this is most definitely a hack. The real problem here is that there is no callback to notify a "client" interface like vlan when a "parent" interface's status changes, and therefore the vlan interface is always IFF_RUNNING. This allows packets to be queued on vlan interface at any time. We can't simply leave the packets on the vlan interface, either, because there is no callback to dequeue them. And last, since it's always IFF_RUNNING, if we just *toss* the packets, we lose gratuitous ARPs and DAD packets. "This needs work," but at least it no longer bleeds. diff 1.41 Thu Jul 08 19:09:12 MDT 2004 mycroft If the parent interface is not IFF_RUNNING, do not call its start function. This prevent a variety of fun panics, and therefore fixes PR 12932, PR 17561, and PR 18376... XXX ...however this is most definitely a hack. The real problem here is that there is no callback to notify a "client" interface like vlan when a "parent" interface's status changes, and therefore the vlan interface is always IFF_RUNNING. This allows packets to be queued on vlan interface at any time. We can't simply leave the packets on the vlan interface, either, because there is no callback to dequeue them. And last, since it's always IFF_RUNNING, if we just *toss* the packets, we lose gratuitous ARPs and DAD packets. "This needs work," but at least it no longer bleeds. diff 1.41 Thu Jul 08 19:09:12 MDT 2004 mycroft If the parent interface is not IFF_RUNNING, do not call its start function. This prevent a variety of fun panics, and therefore fixes PR 12932, PR 17561, and PR 18376... XXX ...however this is most definitely a hack. The real problem here is that there is no callback to notify a "client" interface like vlan when a "parent" interface's status changes, and therefore the vlan interface is always IFF_RUNNING. This allows packets to be queued on vlan interface at any time. We can't simply leave the packets on the vlan interface, either, because there is no callback to dequeue them. And last, since it's always IFF_RUNNING, if we just *toss* the packets, we lose gratuitous ARPs and DAD packets. "This needs work," but at least it no longer bleeds. diff 1.41 Thu Jul 08 19:09:12 MDT 2004 mycroft If the parent interface is not IFF_RUNNING, do not call its start function. This prevent a variety of fun panics, and therefore fixes PR 12932, PR 17561, and PR 18376... XXX ...however this is most definitely a hack. The real problem here is that there is no callback to notify a "client" interface like vlan when a "parent" interface's status changes, and therefore the vlan interface is always IFF_RUNNING. This allows packets to be queued on vlan interface at any time. We can't simply leave the packets on the vlan interface, either, because there is no callback to dequeue them. And last, since it's always IFF_RUNNING, if we just *toss* the packets, we lose gratuitous ARPs and DAD packets. "This needs work," but at least it no longer bleeds. diff 1.41 Thu Jul 08 19:09:12 MDT 2004 mycroft If the parent interface is not IFF_RUNNING, do not call its start function. This prevent a variety of fun panics, and therefore fixes PR 12932, PR 17561, and PR 18376... XXX ...however this is most definitely a hack. The real problem here is that there is no callback to notify a "client" interface like vlan when a "parent" interface's status changes, and therefore the vlan interface is always IFF_RUNNING. This allows packets to be queued on vlan interface at any time. We can't simply leave the packets on the vlan interface, either, because there is no callback to dequeue them. And last, since it's always IFF_RUNNING, if we just *toss* the packets, we lose gratuitous ARPs and DAD packets. "This needs work," but at least it no longer bleeds. |
Completed in 702 milliseconds