diff options
| author |   Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp> | 2013-10-16 17:07:16 +0900 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2013-10-18 16:02:53 -0400 |
| commit | dfb5fa32c66496a53ec6a45302d902416b51ade2 (patch) | |
| tree | 3db8a5398a20be4884b5fb753626331e43d35dc9 /net/unix/af_unix.c | |
| parent | bridge: Fix the way the PVID is referenced (diff) | |
| download | wireguard-linux-dfb5fa32c66496a53ec6a45302d902416b51ade2.tar.xz wireguard-linux-dfb5fa32c66496a53ec6a45302d902416b51ade2.zip | |
bridge: Fix updating FDB entries when the PVID is applied
We currently set the value that variable vid is pointing, which will be
used in FDB later, to 0 at br_allowed_ingress() when we receive untagged
or priority-tagged frames, even though the PVID is valid.
This leads to FDB updates in such a wrong way that they are learned with
VID 0.
Update the value to that of PVID if the PVID is applied.
Signed-off-by: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Reviewed-by: Vlad Yasevich <vyasevic@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions