From: "Luís Henriques" <lhenriques@suse.de>
To: Xiubo Li <xiubli@redhat.com>
Cc: idryomov@gmail.com, ceph-devel@vger.kernel.org,
jlayton@kernel.org, vshankar@redhat.com, mchangir@redhat.com
Subject: Re: [PATCH v2 0/2] ceph: fix fscrypt_destroy_keyring use-after-free bug
Date: Wed, 07 Jun 2023 10:18:48 +0100 [thread overview]
Message-ID: <87h6rj8wav.fsf@suse.de> (raw)
In-Reply-To: <7ab9007b-763b-aacf-2297-62f1989e2efd@redhat.com> (Xiubo Li's message of "Tue, 6 Jun 2023 20:29:40 +0800")
Xiubo Li <xiubli@redhat.com> writes:
> On 6/6/23 17:53, Luís Henriques wrote:
>> xiubli@redhat.com writes:
>>
>>> From: Xiubo Li <xiubli@redhat.com>
>>>
>>> V2:
>>> - Improve the code by switching to wait_for_completion_killable_timeout()
>>> when umounting, at the same add one umount_timeout option.
>> Instead of adding yet another (undocumented!) mount option, why not re-use
>> the already existent 'mount_timeout' instead? It's already defined and
>> kept in 'struct ceph_options', and the default value is defined with the
>> same value you're using, in CEPH_MOUNT_TIMEOUT_DEFAULT.
>
> This is for mount purpose. Is that okay to use the in umount case ?
Yeah, you're probably right. It's just that adding yet another knob for a
corner case that probably will never be used and very few people will know
about is never a good thing (IMO). Anyway, I think that at least this new
mount option needs to be mentioned in 'Documentation/filesystems/ceph.rst'.
Cheers,
--
Luís
next prev parent reply other threads:[~2023-06-07 9:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 3:32 [PATCH v2 0/2] ceph: fix fscrypt_destroy_keyring use-after-free bug xiubli
2023-06-06 3:32 ` [PATCH v2 1/2] ceph: drop the messages from MDS when unmounting xiubli
2023-06-06 7:47 ` Milind Changire
2023-06-06 8:50 ` Xiubo Li
2023-06-06 3:32 ` [PATCH v2 2/2] ceph: just wait the osd requests' callbacks to finish " xiubli
2023-06-06 7:12 ` Milind Changire
2023-06-06 9:53 ` [PATCH v2 0/2] ceph: fix fscrypt_destroy_keyring use-after-free bug Luís Henriques
2023-06-06 12:29 ` Xiubo Li
2023-06-07 9:18 ` Luís Henriques [this message]
2023-06-07 10:00 ` Ilya Dryomov
2023-06-08 2:10 ` Xiubo Li
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=87h6rj8wav.fsf@suse.de \
--to=lhenriques@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=mchangir@redhat.com \
--cc=vshankar@redhat.com \
--cc=xiubli@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.