Skip to content

Conversation

@aversecat
Copy link
Contributor

@aversecat aversecat commented Sep 17, 2025

  • working mounts, utils, quorum setup
  • tests mounts by default using ::1 but scratch mounts are ipv4.
  • el7/el8 support still blocked due to folio changes
  • counter patches aren't right yet, might BUG

@aversecat aversecat added the WIP label Sep 17, 2025
@aversecat aversecat changed the title ** WIP ** ipv6 changes. ipv6 changes. Oct 24, 2025
@aversecat aversecat removed the WIP label Oct 31, 2025
@aversecat aversecat force-pushed the auke/ipv6 branch 2 times, most recently from 9452997 to b79fcee Compare November 17, 2025 20:57
The size of this thing is well over 1kb, and the compiler will
error on several supported distributions that this particular
function reaches over 2k stack frame size, which is excessive,
even for a function that isn't called regularly.

We can allocate the thing in one go if we smartly allocate this
as an array of (an array of structs) which allows us to index
it as a 2d array as before, taking away some of the additional
complexities.

Signed-off-by: Auke Kok <auke.kok@versity.com>
This change adds ipv6 support to various scoutfs sub-commands, allowing
users to mkfs, print and change-quorum-config using ipv6 addresses, and
modifies the outputs.

Any ipv6 address/port is displayed as [::1]:5000 to comply with the
related RFC's. Input strings remain consistent as the quorum config
input value is comma-separated already, not posing any issues.

Signed-off-by: Auke Kok <auke.kok@versity.com>
Instead of using 127.0.0.1, we initialize the quorum slots to ::1,
enabling all ipv6 support.

Signed-off-by: Auke Kok <auke.kok@versity.com>
This adds IPv6 support to the kernel module side.

Signed-off-by: Auke Kok <auke.kok@versity.com>
@aversecat aversecat changed the title ipv6 changes. ipv6 support. Dec 5, 2025
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.

2 participants