Skip to content

[Release 1.2] Cherry-pick: metadata/gc: remove the noop-loop for snapshot reference#2965

Merged
crosbymichael merged 1 commit intocontainerd:release/1.2from
fuweid:remove-noop
Jan 30, 2019
Merged

[Release 1.2] Cherry-pick: metadata/gc: remove the noop-loop for snapshot reference#2965
crosbymichael merged 1 commit intocontainerd:release/1.2from
fuweid:remove-noop

Conversation

@fuweid
Copy link
Copy Markdown
Member

@fuweid fuweid commented Jan 30, 2019

The noop-loop does nothing.

The containerd doesn't have any snapshotter buckets at the beginning.
If user uses specific dir as rootfs to create container, and sets
snapshotter key to the container, like overlayfs by mistake,
the gc scheduler will try to scan the snapshotter and panic.

In order to avoid this case, remove the noop-loop here.

Signed-off-by: Wei Fu [email protected]
(cherry picked from commit 34672d4)
Signed-off-by: Wei Fu [email protected]

@codecov-io
Copy link
Copy Markdown

codecov-io commented Jan 30, 2019

Codecov Report

Merging #2965 into release/1.2 will increase coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@               Coverage Diff               @@
##           release/1.2    #2965      +/-   ##
===============================================
+ Coverage        43.66%   43.66%   +<.01%     
===============================================
  Files              101      101              
  Lines            10755    10754       -1     
===============================================
  Hits              4696     4696              
+ Misses            5330     5329       -1     
  Partials           729      729
Flag Coverage Δ
#linux 47.35% <ø> (+0.01%) ⬆️
#windows 40.75% <ø> (ø) ⬆️
Impacted Files Coverage Δ
metadata/gc.go 61.51% <ø> (+0.16%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d86a73a...9b6a318. Read the comment docs.

The noop-loop does nothing.

The containerd doesn't have any snapshotter buckets at the beginning.
If user uses specific dir as rootfs to create container, and sets
`snapshotter` key to the container, like `overlayfs` by mistake,
the gc scheduler will try to scan the snapshotter and panic.

In order to avoid this case, remove the noop-loop here.

Signed-off-by: Wei Fu <[email protected]>
(cherry picked from commit 34672d4)
Signed-off-by: Wei Fu <[email protected]>
Copy link
Copy Markdown
Member

@estesp estesp left a comment

Choose a reason for hiding this comment

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

LGTM

@crosbymichael
Copy link
Copy Markdown
Member

LGTM

@crosbymichael crosbymichael merged commit dba2e5e into containerd:release/1.2 Jan 30, 2019
@fuweid fuweid deleted the remove-noop branch February 20, 2019 06:32
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.

4 participants