From: YOSHIFUJI Hideaki <[email protected]> Date: Sun, 10 Feb 2013 02:00:59 +0900
> To allow both of protocol-specific data and device-specific data > attached with neighbour entry, and to eliminate size calculation > cost when allocating entry, sizeof protocol-speicic data must be > multiple of NEIGH_PRIV_ALIGN. On 64bit archs, > sizeof(struct dn_neigh) is multiple of NEIGH_PRIV_ALIGN, but on > 32bit archs, it was not. > > Introduce NEIGH_ENTRY_SPACE() macro to ensure that protocol-specific > entry-size meets our requirement. > > Reported-by: Fengguang Wu <[email protected]> > Signed-off-by: YOSHIFUJI Hideaki <[email protected]> Applied. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
