kinvolk-archives / fuse-userns-patches Goto Github PK

check list:

• it has a cover letter
• it compiles
• it works
• cc the correct lists and people
• ./scripts/checkpatch.pl
• preparing "Changes since v5"
• review comments from v5 were addressed

Previous check list from #1:

• Each patch has a "From" line in the commit message
• Contain a description of the tests
• List of remaining TODO in the cover letter
• Link to previous version v4 on patchwork
• "Changes since v4"
• "This patchset is based on work by..." could be a the top, as introduction
• Include a pointer to a git repo

/cc @dongsupark

Patch set checklist:

• Each patch has a "From" line in the commit message
• Contain a description of the tests
• List of remaining TODO in the cover letter
• Link to previous version v4 on patchwork
• "Changes since v4"
• "This patchset is based on work by..." could be a the top, as introduction
• Include a pointer to a git repo. I suggest to name the branch "dongsu/fuse-userns-v5-1" and not updating the branch once published
• Remove patches unrelated to fuse: patch 12 (fuse does not use block device)

Hi, I'm researching the possibility of CentOS supporting fuse in user namespaces and was wondering if the goal of this repo was to upstream into the linux kernel? If so, woohoo!