[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgPBx9xPWY7obK60=RTnOF3Ln0j9XkhYbekML=Fi3bFXg@mail.gmail.com>
Date: Thu, 25 Apr 2019 11:02:54 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ilya Dryomov <idryomov@...il.com>, Jeff Layton <jlayton@...nel.org>
Cc: ceph-devel@...r.kernel.org,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Ceph fixes for 5.1-rc7
On Thu, Apr 25, 2019 at 10:48 AM Ilya Dryomov <idryomov@...il.com> wrote:
>
> dentry name handling fixes from Jeff and a memory leak fix from Zheng.
> Both are old issues, marked for stable.
Hmm. You probably should have talked to Al about the dentry name
issue, because he'd most likely have pointed you towards our helper
function for exactly this thing:
struct name_snapshot stable;
take_dentry_name_snapshot(&stable, dentry);
... use stable.name ..
release_dentry_name_snapshot(&stable);
which doesn't need any extra memory allocation outside of some fairly
limited stack allocation for the 'name_snapshot' itself, because it
knows about the dentry name rules, and
- for inline names, it copies it under the d_lock into the fixed
DNAME_INLINE_LEN-sized buffer
- for out-of-line names, it knows that the name allocation is stable
and ref-counted, and just increments the refcount and uses the
existing name pointer.
now, maybe you need to always do that name allocation anyway (looking
at the diff it looks like you often do that for other cases), so maybe
the name snapshot capability isn't all that useful for you and the
above wouldn't have helped, but I suspect you might not even have
realized that there was an option like this.
I've pulled this, but maybe Jeff wants to look at whether that
snapshotting model could have helped.
Linus
Powered by blists - more mailing lists