Skip to content

Conversation

@quitschbo
Copy link
Contributor

This PR contains the latest changes to compile for Kernel v6.17

The latest stable kernel I tested to load the module was v6.17.5

I also compiled it against v6.18-rc2 source. However, I did not tested to actually run it on hardware.

This is a partial backport of following mainline commit in v6.13:

    commit 4b42fbc6bd8f73d9ded535d8c61ccaa837ff3bd4
    Author: Petr Machata <petrm@nvidia.com>
    Date:   Thu Nov 14 15:09:53 2024 +0100

    ndo_fdb_add: Add a parameter to report whether notification was sent

    Currently when FDB entries are added to or deleted from a VXLAN netdevice,
    the VXLAN driver emits one notification, including the VXLAN-specific
    attributes. The core however always sends a notification as well, a generic
    one. Thus two notifications are unnecessarily sent for these operations. A
    similar situation comes up with bridge driver, which also emits
    notifications on its own:

     # ip link add name vx type vxlan id 1000 dstport 4789
     # bridge monitor fdb &
     [1] 1981693
     # bridge fdb add de:ad:be:ef:13:37 dev vx self dst 192.0.2.1
     de:ad:be:ef:13:37 dev vx dst 192.0.2.1 self permanent
     de:ad:be:ef:13:37 dev vx self permanent

    In order to prevent this duplicity, add a paremeter to ndo_fdb_add,
    bool *notified. The flag is primed to false, and if the callee sends a
    notification on its own, it sets it to true, thus informing the core that
    it should not generate another notification.

    Signed-off-by: Petr Machata <petrm@nvidia.com>
    Reviewed-by: Amit Cohen <amcohen@nvidia.com>
    Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
    Link: https://patch.msgid.link/cbf6ae8195e85cbf922f8058ce4eba770f3b71ed.1731589511.git.petrm@nvidia.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

Signed-off-by: Michael Weiß <michael.weiss@aisec.fraunhofer.de>
Since mainline commit (8fa7292fee5c) in v6.15 timer_delete[_sync]()
replaces del_timer[_sync](). Thus, we need to do this in igb_main.c, too.

    treewide: Switch/rename to timer_delete[_sync]()

    timer_delete[_sync]() replaces del_timer[_sync](). Convert the whole tree
    over and remove the historical wrapper inlines.

    Conversion was done with coccinelle plus manual fixups where necessary.

    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Ingo Molnar <mingo@kernel.org>

Signed-off-by: Michael Weiß <michael.weiss@aisec.fraunhofer.de>
This is a backport of following mainline commit in v6.17:

    commit e78f70bad29c5ae1e1076698b690b15794e9b81e (HEAD)
    Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Date:   Tue Jul 1 14:32:25 2025 +0200

    time/timecounter: Fix the lie that struct cyclecounter is const

    In both the read callback for struct cyclecounter, and in struct
    timecounter, struct cyclecounter is declared as a const pointer.

    Unfortunatly, a number of users of this pointer treat it as a non-const
    pointer as it is burried in a larger structure that is heavily modified by
    the callback function when accessed.  This lie had been hidden by the fact
    that container_of() "casts away" a const attribute of a pointer without any
    compiler warning happening at all.

    Fix this all up by removing the const attribute in the needed places so
    that everyone can see that the structure really isn't const, but can,
    and is, modified by the users of it.

    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Link: https://lore.kernel.org/all/2025070124-backyard-hurt-783a@gregkh

Signed-off-by: Michael Weiß <michael.weiss@aisec.fraunhofer.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant