From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>, linux-mtd@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, adrian.hunter@intel.com,
stable@vger.kernel.org
Subject: Re: [PATCH] ubifs: Fix inode leak in xattr code
Date: Mon, 15 May 2017 17:53:54 +0300 [thread overview]
Message-ID: <1494860034.18055.17.camel@gmail.com> (raw)
In-Reply-To: <1494858005-18439-1-git-send-email-richard@nod.at>
On Mon, 2017-05-15 at 16:20 +0200, Richard Weinberger wrote:
> To solve this problem, set i_nlink for all xattr inodes to 0, such
> that
> the iput() in the UBIFS xattr code makes the temporary inode vanish
> immediately.
What if there is iget right after iput? With this patch, will we need
to go all the way to the slow media instead of just getting having the
inode from the inode cache?
next prev parent reply other threads:[~2017-05-15 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 14:20 [PATCH] ubifs: Fix inode leak in xattr code Richard Weinberger
2017-05-15 14:53 ` Artem Bityutskiy [this message]
2017-05-15 15:22 ` Richard Weinberger
2017-05-15 16:05 ` Artem Bityutskiy
2017-05-15 16:22 ` Richard Weinberger
2017-05-15 17:57 ` Richard Weinberger
2017-05-16 22:20 ` Richard Weinberger
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=1494860034.18055.17.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=stable@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