From: Deepanshu Kartikey <kartikey406@gmail.com>
To: jack@suse.cz
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] isofs: fix inode leak caused by disconnected dentries from exportfs
Date: Fri, 3 Oct 2025 04:53:41 +0530 [thread overview]
Message-ID: <20251002232341.2396110-1-kartikey406@gmail.com> (raw)
Thank you for debugging this properly and providing the correct analysis. I clearly missed the actual root cause.
I'll study your patch to understand what I got wrong.
Best regards,
Deepanshu
next reply other threads:[~2025-10-02 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 23:23 Deepanshu Kartikey [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-01 20:27 Deepanshu Kartikey
2025-10-02 16:08 ` Jan Kara
2025-10-01 12:56 Deepanshu Kartikey
2025-10-01 9:43 Deepanshu Kartikey
2025-10-01 12:26 ` Jan Kara
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=20251002232341.2396110-1-kartikey406@gmail.com \
--to=kartikey406@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®