Page MenuHomeFreeBSD

tarfs: Support paths that spill into exthdrs.
ClosedPublic

Authored by des on Apr 2 2024, 8:15 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Feb 22, 1:46 PM
Unknown Object (File)
Feb 10 2025, 1:08 PM
Unknown Object (File)
Feb 4 2025, 11:56 AM
Unknown Object (File)
Feb 4 2025, 3:09 AM
Unknown Object (File)
Feb 4 2025, 3:07 AM
Unknown Object (File)
Feb 4 2025, 2:20 AM
Unknown Object (File)
Jan 25 2025, 4:11 AM
Unknown Object (File)
Oct 1 2024, 1:46 PM

Details

Summary

MFC after: 3 days
Sponsored by: Juniper Networks, Inc.
Sponsored by: Klara, Inc.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

des requested review of this revision.Apr 2 2024, 8:15 PM
kevans added a subscriber: kevans.
kevans added inline comments.
sys/fs/tarfs/tarfs_vfsops.c
619

Is there any value in complaining if we somehow see both a path and GNU.sparse.name exthdr?

This revision is now accepted and ready to land.Apr 3 2024, 4:48 AM
des marked an inline comment as done.Apr 3 2024, 9:14 AM
des added inline comments.
sys/fs/tarfs/tarfs_vfsops.c
619

I don't think so. I don't see how it can be exploited. We'll just use whichever came last, we won't leak memory or take a wrong turn somewhere.

des marked an inline comment as done.Apr 3 2024, 9:14 AM
This revision was automatically updated to reflect the committed changes.