Re: [PATCH v3 00/25] RFC: Read-only dynamic update implementation

On Wed, Mar 25, 2026 at 02:00:23AM +0100, Stefano Brivio wrote:

On Wed, 25 Mar 2026 01:56:51 +0100 Stefano Brivio wrote:

...

On Mon, 23 Mar 2026 18:37:07 +1100 David Gibson wrote:

...

Here's a new draft of dynamic updates. This now can successfully update rules, though I've not tested it very extensively. Essentially this is just barely enough to work, it still could do with rather a lot of polish.

Patches 1..12/22 are preliminary reworks that make moderate sense even without pesto - feel free to apply if you're happy with them.

I'm applying (in a moment, tests are running now):

- 1/25, 2/25, - not 3/25 (comments pending) - not 4/25 (depends on 3/25) - 5/25, 6/25, - not 7/25 (Coverity Scan warnings), - not 8/25 (comments pending), - 9/25, 10/25, 11/25, 12/25.

Never mind, most of the "TCP/IPv4: ns to host" tests fail, probably I missed something while cherry-picking patches from this series. I guess a re-spin up to 12/25 would be more convenient in this case.

Will do. -- David Gibson (he or they) | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you, not the other way | around. http://www.ozlabs.org/~dgibson