Remove mount namespace from shim#1856
Conversation
|
@Random-Liu can you try this PR to see if it fixes #1785 I was able to, kinda reproduce, this type of error in the stress tests but it wasn't rootfs related, it was mount related. |
9f4b3ce to
fd0af30
Compare
|
There's already an option for this, why removing the feature entirely? In which scenarios the mountns causes the issue on a recent kernel? |
Signed-off-by: Michael Crosby <[email protected]>
fd0af30 to
fd2e3cd
Compare
|
@mlaventure if you remember how we had this initially, we had extra code to disconnect that mounts in the new ns but that broke propagation. We removed that but left the namespace. However, we are seeing more issues, the zfs issue and I ran into a couple during stress tests with leaking mounts. This fixes my stress test findings and hopefully fixes #1785 |
Codecov Report
@@ Coverage Diff @@
## master #1856 +/- ##
==========================================
+ Coverage 44.25% 49.18% +4.93%
==========================================
Files 67 86 +19
Lines 7105 8244 +1139
==========================================
+ Hits 3144 4055 +911
- Misses 3468 3519 +51
- Partials 493 670 +177
Continue to review full report at Codecov.
|
|
😞 Shame, it makes the world so much easier not to have to deal with the mounts cleanup |
|
Ya, but you did add all that mount cleanup code already ;) |
|
LGTM |
Signed-off-by: Michael Crosby [email protected]