Revision 544586f742b43c6fd5fcb74c794d33b2ef189e64 authored by Satish Ashok on 28 July 2015, 10:28:27 UTC, committed by David S. Miller on 29 July 2015, 21:57:05 UTC
When fast leave is configured on a bridge port and an IGMP leave is received for a group, the group is not deleted immediately if there is a router detected or if multicast querier is configured. Ideally the group should be deleted immediately when fast leave is configured. Signed-off-by: Satish Ashok <sashok@cumulusnetworks.com> Signed-off-by: David S. Miller <davem@davemloft.net>
1 parent df356d5
| File | Mode | Size |
|---|---|---|
| apparmor | ||
| integrity | ||
| keys | ||
| selinux | ||
| smack | ||
| tomoyo | ||
| yama | ||
| Kconfig | -rw-r--r-- | 5.7 KB |
| Makefile | -rw-r--r-- | 900 bytes |
| commoncap.c | -rw-r--r-- | 29.1 KB |
| device_cgroup.c | -rw-r--r-- | 21.1 KB |
| inode.c | -rw-r--r-- | 6.5 KB |
| lsm_audit.c | -rw-r--r-- | 9.5 KB |
| min_addr.c | -rw-r--r-- | 1.3 KB |
| security.c | -rw-r--r-- | 53.2 KB |
Computing file changes ...
