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)
Tue, Sep 8, 5:34 PM
Unknown Object (File)
Mon, Sep 7, 6:21 PM
Unknown Object (File)
Sat, Sep 5, 5:50 PM
Unknown Object (File)
Sat, Sep 5, 5:50 PM
Unknown Object (File)
Sat, Sep 5, 5:38 PM
Unknown Object (File)
Sat, Sep 5, 1:24 PM
Unknown Object (File)
Sat, Sep 5, 6:29 AM
Unknown Object (File)
Fri, Sep 4, 6:19 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.