Re: [RFC v2 4/6] fs: distinguish between user initiated freeze and kernel initiated freeze

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Luis Chamberlain <mcgrof@xxxxxxxxxx>
Subject: Re: [RFC v2 4/6] fs: distinguish between user initiated freeze and kernel initiated freeze
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 20 Apr 2021 13:46:26 +0100
Cc: rafael@xxxxxxxxxx, gregkh@xxxxxxxxxxxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, jack@xxxxxxx, bvanassche@xxxxxxx, jeyu@xxxxxxxxxx, ebiederm@xxxxxxxxxxxx, mchehab@xxxxxxxxxx, keescook@xxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, kernel@xxxxxxxxxxx, kexec@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20210417001026.23858-5-mcgrof@kernel.org>

Wouldn't it be simpler to just add a new flag to signal a kernel
initiated freeze, or even better the exact reason (suspend) instead of
overloading the state machine?

References:
- [RFC v2 0/6] vfs: provide automatic kernel freeze / resume
  - From: Luis Chamberlain
- [RFC v2 4/6] fs: distinguish between user initiated freeze and kernel initiated freeze
  - From: Luis Chamberlain

Prev by Date: Re: [PATCH v2] docs: proc.rst: meminfo: briefly describe gaps in memory accounting
Next by Date: Re: [RFC v2 6/6] fs: add automatic kernel fs freeze / thaw and remove kthread freezing
Previous by thread: [RFC v2 4/6] fs: distinguish between user initiated freeze and kernel initiated freeze
Next by thread: [RFC v2 6/6] fs: add automatic kernel fs freeze / thaw and remove kthread freezing
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux