mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jia Zhu <zhujia.zj@bytedance.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-cachefs@redhat.com, linux-erofs@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, jefflexu@linux.alibaba.com,
	hsiangkao@linux.alibaba.com, yinxin.x@bytedance.com,
	zhujia.zj@bytedance.com
Subject: Re: Re: [PATCH V5 5/5] cachefiles: add restore command to recover inflight ondemand read requests
Date: Fri, 14 Apr 2023 23:12:55 +0800	[thread overview]
Message-ID: <65f424ca-d7cd-f53b-cefc-684ec0393bce@bytedance.com> (raw)
In-Reply-To: <1250439.1681480404@warthog.procyon.org.uk>



在 2023/4/14 21:53, David Howells 写道:
> Jia Zhu <zhujia.zj@bytedance.com> wrote:
> 
>> +int cachefiles_ondemand_restore(struct cachefiles_cache *cache, char *args)
>> +{
>> +	struct cachefiles_req *req;
>> +
>> +	XA_STATE(xas, &cache->reqs, 0);
>> +
>> +	if (!test_bit(CACHEFILES_ONDEMAND_MODE, &cache->flags))
>> +		return -EOPNOTSUPP;
>> +
>> +	/*
>> +	 * Reset the requests to CACHEFILES_REQ_NEW state, so that the
>> +	 * requests have been processed halfway before the crash of the
>> +	 * user daemon could be reprocessed after the recovery.
>> +	 */
>> +	xas_lock(&xas);
>> +	xas_for_each(&xas, req, ULONG_MAX)
>> +		xas_set_mark(&xas, CACHEFILES_REQ_NEW);
>> +	xas_unlock(&xas);
>> +
>> +	wake_up_all(&cache->daemon_pollwq);
>> +	return 0;
>> +}
> 
> Should there be a check to see if this is needed?
> 
> David

I've considered whether to add a check here, since the user could invoke
'restore' through ioctl at any time.

If 'restore' is called without user daemon crashing. Then the req being
processed by the user daemon will be reset to CACHEFILES_REQ_NEW and
could be re-read and processed by the user daemon.

For OPEN req:  The user daemon will ignore this repeated req since the
related anonymous fd is the same.

For READ req: The user daemon will read the same part of the data again
and write it to fscache (this will not cause any error)

For CLOSE req: Actually the user daemon will close this anonymous fd,
but fortunately [PATCH 3/5] could handle this case by reopening it
automatically.

Thus "restore" could be called at any time without error, checks
might introduce extra race conditions.

Jia
> 

      reply	other threads:[~2023-04-14 15:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 14:01 [PATCH V5 0/5] Introduce daemon failover mechanism to recover from crashing Jia Zhu
2023-03-29 14:01 ` [PATCH V5 1/5] cachefiles: introduce object ondemand state Jia Zhu
2023-03-29 14:01 ` [PATCH V5 2/5] cachefiles: extract ondemand info field from cachefiles_object Jia Zhu
2023-03-29 14:01 ` [PATCH V5 3/5] cachefiles: resend an open request if the read request's object is closed Jia Zhu
2023-03-29 14:01 ` [PATCH V5 4/5] cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode Jia Zhu
2023-03-29 14:01 ` [PATCH V5 5/5] cachefiles: add restore command to recover inflight ondemand read requests Jia Zhu
2023-04-14 13:48 ` [PATCH V5 4/5] cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode David Howells
2023-04-14 14:13   ` Jia Zhu
2023-04-14 13:51 ` [PATCH V5 2/5] cachefiles: extract ondemand info field from cachefiles_object David Howells
2023-04-14 15:45   ` Jia Zhu
2023-04-14 13:53 ` [PATCH V5 5/5] cachefiles: add restore command to recover inflight ondemand read requests David Howells
2023-04-14 15:12   ` Jia Zhu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=65f424ca-d7cd-f53b-cefc-684ec0393bce@bytedance.com \
    --to=zhujia.zj@bytedance.com \
    --cc=dhowells@redhat.com \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yinxin.x@bytedance.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®