| Age | Commit message (Collapse) | Author |
|---|
|
Changes specific to vendor kernels
Signed-off-by: Dominik Sliwa <dominik.sliwa@toradex.com>
|
|
Signed-off-by: Dominik Sliwa <dominik.sliwa@toradex.com>
|
|
Replace all the different nested versions of generic netlink
backport with a single one, covering from < 3.13 all the way
to the upcoming netlink policy improvements in 4.20.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
If compiling on 3.13, struct genl_family isn't actually
struct backport_genl_family, and then family->family
doesn't exist. In other cases, it's actually necessary
to update it, so add an #ifdef with the same logic as
the override from genl_family -> backport_genl_family.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Family ID from the original family struct will be used when building
genl messages (sent as nlmsg_type), so the new id should be updated in
the original (older kernel format) family struct too
Signed-off-by: Aaron Komisar <aaron.komisar@tandemg.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
This is filled with family->id, which needs to be set after registering
the copy.
Signed-off-by: Felix Fietkau <nbd@nbd.name>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
The multicast group offset needs to be synced after registering the
family, otherwise multicast messages will use the wrong id
Signed-off-by: Felix Fietkau <nbd@nbd.name>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
Backport upstream
commit 4f6265d485ea0a2507692ded8ed47b323f49587c
Author: David Ahern <dsahern@gmail.com>
Date: Fri Oct 27 17:37:12 2017 -0700
netlink: Allow ext_ack to carry non-error messages
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
I also never seem to have really tested unload after dumps,
and using the family->attrbuf was causing memory corruption
in the copied family.
Fix this by keeping track of the family copies separately
and actually copying the attrbuf over so the family can use
it from there.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
I neglected to take into account that the spatch will also
be applied to the backport-4.12.c file itself, fix that.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
The previous backport just made the code compatible, but removed
the extack functionality entirely.
By ignoring the setsockopt() and just assuming that userspace does
in fact support extack (which is true for all of wifi and in fact
all users of libnl), we can support full extack functionality even
on kernels that don't support it.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
