From: Xiubo Li <xiubli@redhat.com>
To: "Luís Henriques" <lhenriques@suse.de>
Cc: jlayton@kernel.org, idryomov@gmail.com, vshankar@redhat.com,
ukernel@gmail.com, ceph-devel@vger.kernel.org
Subject: Re: [PATCH v2] ceph: do not update snapshot context when there is no new snapshot
Date: Sat, 19 Feb 2022 10:35:38 +0800 [thread overview]
Message-ID: <2d694ae4-5e06-7729-3dd5-063b5ab76ffd@redhat.com> (raw)
In-Reply-To: <877d9si0b1.fsf@brahms.olymp>
On 2/19/22 12:53 AM, Luís Henriques wrote:
> Hi!
>
> I'm seeing the BUG below when running a simple fsstress on an encrypted
> directory. Reverting this commit seems to make it go away, but I'm not
> yet 100% sure this is the culprit (I just wanted to report it before going
> offline for the weekend.)
BTW, were you using the 'testing' branch ? It seems Jeff has not
included the fscrypt patches yet in it.
- Xiubo
>
> I stared at this code for a bit, but no light so far.
>
> Cheers,
next prev parent reply other threads:[~2022-02-19 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 2:47 [PATCH v2] ceph: do not update snapshot context when there is no new snapshot xiubli
2022-02-18 14:17 ` Jeff Layton
2022-02-18 16:53 ` Luís Henriques
2022-02-19 2:35 ` Xiubo Li [this message]
2022-02-19 13:00 ` Jeff Layton
2022-02-19 6:30 ` Xiubo Li
2022-02-21 9:54 ` Luís Henriques
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=2d694ae4-5e06-7729-3dd5-063b5ab76ffd@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=lhenriques@suse.de \
--cc=ukernel@gmail.com \
--cc=vshankar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox