Commit Message

When we're saving kdat we check if fs is laying on
is on tmpfs thus on machine reboot it get removed
and regenerated on next run. Still there is no
proof that when we're reading it the underlied
fs has not been changed. Lets add this check.
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
---
criu/kerndat.c | 7 +++++++
1 file changed, 7 insertions(+)

Comments

2018-04-03 18:46 GMT+01:00 Cyrill Gorcunov <gorcunov@gmail.com>:
> When we're saving kdat we check if fs is laying on> is on tmpfs thus on machine reboot it get removed> and regenerated on next run. Still there is no> proof that when we're reading it the underlied> fs has not been changed. Lets add this check.>> Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
I'm not really sure if we need to care about someone remounting fs
and placing a copy of criu.kdat over again..
I don't mind, maybe we should bother, I don't have an opinion about this.
Anyway, +Cc: Pasha, Andrei, who also introduced this.

On Tue, Apr 03, 2018 at 07:05:26PM +0100, Dmitry Safonov wrote:
> 2018-04-03 18:46 GMT+01:00 Cyrill Gorcunov <gorcunov@gmail.com>:> > When we're saving kdat we check if fs is laying on> > is on tmpfs thus on machine reboot it get removed> > and regenerated on next run. Still there is no> > proof that when we're reading it the underlied> > fs has not been changed. Lets add this check.> >> > Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>> > I'm not really sure if we need to care about someone remounting fs> and placing a copy of criu.kdat over again..> I don't mind, maybe we should bother, I don't have an opinion about this.> > Anyway, +Cc: Pasha, Andrei, who also introduced this.
Thanks a lot for review, Dima! I'll resend the series one day.

On Thu, Apr 05, 2018 at 10:57:57AM +0300, Pavel Emelyanov wrote:
> On 04/03/2018 08:46 PM, Cyrill Gorcunov wrote:> > When we're saving kdat we check if fs is laying on> > is on tmpfs thus on machine reboot it get removed> > and regenerated on next run. Still there is no> > proof that when we're reading it the underlied> > fs has not been changed. Lets add this check.> > Can you describe the scenario in which kdat.cache writing happened on tmpfs, while> reading on non-tmpfs?
I thought I put it into changelog. The fs happen to change for various reasons
(including node operator errors), the check has neglible perf penalty so I think
it worth having it here. The patch series has to be reworked anyway so for
now just drop it.