-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix logging on virtiofs shutdown #11359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix logging on virtiofs shutdown #11359
Conversation
e598eef
to
2e7b608
Compare
Please add a subsystem name before your PR title and commit title, like |
2e7b608
to
255dd76
Compare
sure, should be good now |
aaace9c
to
3398fdd
Compare
Hey @justxuewei could you have a look at it? 🙏 |
Hi @pawelbeza, I am out of office until next week. Sorry:( |
ahh sure no worries, let's revisit it next week then have a great holidays!:) |
3398fdd
to
04136f7
Compare
@justxuewei sorry for late reply, agree with your comments, it should be good now:) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm, thanks!
Fixes a confusing log message shown when Virtio-FS is disabled. Previously we logged “The virtiofsd had stopped” regardless of whether Virtio-FS was actually enabled or not. Signed-off-by: Paweł Bęza <pawel.beza99@gmail.com>
04136f7
to
91db412
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the caveat that I don't actually work with runtime-go or clh, this looks good to me by inspection. Thanks @pawelbeza!
Fixes a confusing log message shown when Virtio-FS is disabled.
Currently, we log “The virtiofsd had stopped” regardless of whether Virtio-FS was actually enabled or not.