Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better handle filesystem optional features. #66

Merged
merged 4 commits into from
Jan 10, 2025
Merged

Conversation

cwize1
Copy link
Contributor

@cwize1 cwize1 commented Jan 7, 2025

Filesystems (e.g. ext4, xfs) sometimes receive new features. When these features are enabled, anything that loads the filesystem (e.g. kernel, grub, etc.) must support the new feature or it will refuse to load it.

When formatting a new partition, there are a few considerations for if a filesystem feature should be enabled:

  • Does the version of mkfs support that feature?
  • Does the build host kernel support that feature?
  • Does the target OS support that feature?

This change ensure that all these considerations are handled correctly for the ext4 and xfs filesystem types.


Checklist

  • Tests added/updated
  • Documentation updated (if needed)
  • Code conforms to style guidelines

@cwize1 cwize1 requested a review from a team as a code owner January 7, 2025 22:22
liulanze
liulanze previously approved these changes Jan 8, 2025
Filesystems (e.g. ext4, xfs) sometimes receive new features. When these
features are enabled, anything that loads the filesystem (e.g. kernel,
grub, etc.) must support the new feature or it will refuse to load it.

When formatting a new partition, there are a few considerations for if a
filesystem feature should be enabled:

- Does the version of mkfs support that feature?
- Does the build host kernel support that feature?
- Does the target OS support that feature?

This change ensure that all these considerations are handled correctly
for the ext4 and xfs filesystem types.
@cwize1 cwize1 force-pushed the user/chrisgun/xfsOptions branch from e0cb1c4 to 37f090a Compare January 10, 2025 18:37
Copy link
Contributor

@romoh romoh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few comments

toolkit/tools/imagegen/diskutils/diskutils.go Outdated Show resolved Hide resolved
toolkit/tools/internal/targetos/targetos.go Show resolved Hide resolved
Copy link
Contributor

@romoh romoh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I won't block on my comment for now, but I think we should revisit the default behavior logic in a separate change.

@cwize1 cwize1 merged commit a4d53a5 into main Jan 10, 2025
7 checks passed
@cwize1 cwize1 deleted the user/chrisgun/xfsOptions branch January 10, 2025 20:18
elainezhao1 pushed a commit that referenced this pull request Jan 23, 2025
Filesystems (e.g. ext4, xfs) sometimes receive new features. When these
features are enabled, anything that loads the filesystem (e.g. kernel,
grub, etc.) must support the new feature or it will refuse to load it.

When formatting a new partition, there are a few considerations for if a
filesystem feature should be enabled:

- Does the version of mkfs support that feature?
- Does the build host kernel support that feature?
- Does the target OS support that feature?

This change ensure that all these considerations are handled correctly
for the ext4 and xfs filesystem types.
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.

6 participants