mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "lilei24@kuaishou.com" <lilei24@kuaishou.com>
Cc: Alex Markuze <amarkuze@redhat.com>,
	"idryomov@gmail.com" <idryomov@gmail.com>,
	"sunzhao03@kuaishou.com" <sunzhao03@kuaishou.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re:  答复:  答复: 【外部邮件!】Re:  [PATCH v2] ceph: fix deadlock in ceph_readdir_prepopulate
Date: Wed, 7 Jan 2026 19:59:46 +0000	[thread overview]
Message-ID: <ebc291d2ae5cb3702f67831dd1da932d66177ae2.camel@ibm.com> (raw)
In-Reply-To: <df02fae47a2c45c284d5269a51a2ddd5@kuaishou.com>

On Wed, 2026-01-07 at 16:01 +0000, 李磊 wrote:
> Hi Slava,
> 
> This issue is very rare on our internal cephfs clusters. We had only encountered it for about three times.
> But we are working on same hacking methods to speed up the reproduction. I think it will take me one week
> if everything goes smoothly and I will share the methods here.
> 
> To be honest, this patch should be a revert patch of this one:
> 
> commit : bca9fc14c70fcbbebc84954cc39994e463fb9468
> ceph: when filling trace, call ceph_get_inode outside of mutexes
> 
> I'll resend this patch later.

Sounds good. If I remember correctly, the main issue with the initial patch was
the commit message that didn't have good explanation of the issue and why this
revert can fix the issue. So, if we have all of these details in the commit
message, then the patch should be in good shape.

Thanks,
Slava.


  reply	other threads:[~2026-01-07 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08  7:08 Zhao Sun
2025-08-11 19:43 ` Viacheslav Dubeyko
     [not found]   ` <409ca87f8add4a80a7927981059b3c5f@kuaishou.com>
2026-01-04  9:19     ` 答复: 【外部邮件!】Re: " 李磊
2026-01-05 19:55       ` Viacheslav Dubeyko
2026-01-07 16:01         ` 答复: " 李磊
2026-01-07 19:59           ` Viacheslav Dubeyko [this message]
2026-01-21  7:33             ` 答复: " 李磊
2026-01-21 20:24               ` Viacheslav Dubeyko
2026-01-23  3:08                 ` 李磊

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=ebc291d2ae5cb3702f67831dd1da932d66177ae2.camel@ibm.com \
    --to=slava.dubeyko@ibm.com \
    --cc=amarkuze@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.com \
    --cc=lilei24@kuaishou.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sunzhao03@kuaishou.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®