From: David Woodhouse <dwmw2@infradead.org>
To: Yufen Yu <yuyufen@huawei.com>
Cc: Joakim.Tjernlund@infinera.com, viro@zeniv.linux.org.uk,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jffs2: safely remove obsolete dirent from the f->dents list
Date: Fri, 27 Apr 2018 23:22:42 +0100 [thread overview]
Message-ID: <1524867762.18504.89.camel@infradead.org> (raw)
In-Reply-To: <20180329120023.33169-1-yuyufen@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
This looks a lot better than the first iteration; thank you for getting
it to this point. One last thing, I hope...
On Thu, 2018-03-29 at 20:00 +0800, Yufen Yu wrote:
>
> --- a/fs/jffs2/jffs2_fs_i.h
> +++ b/fs/jffs2/jffs2_fs_i.h
> @@ -42,6 +42,12 @@ struct jffs2_inode_info {
> /* Directory entries */
> struct jffs2_full_dirent *dents;
>
> + /* Directory open refcount */
> + atomic_t nr_dir_opening;
> +
> + /* obsolete dirent count in the list of 'dents' */
> + unsigned int obsolete_count;
> +
> /* The target path if this is the inode of a symlink */
> unsigned char *target;
>
You've made JFFS2_INVALID_LIMIT 64, which is reasonable enough
(although it's a bit of a weird name and possibly wants to be more
specific — invalid *what*?).
So the maximum interesting value of ->obsolete_count is 64. Which means
it might as well be a uint8_t and sit in the padding after the
'usercompr' field.
It might be useful to look at putting the mutually exclusive fields in
struct jffs2_inode_info into a union, and then we don't need the
additional space of the atomic_t either; we'll never need that *and*
the fragtree at the same time... will we?
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]
next prev parent reply other threads:[~2018-04-27 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 12:00 Yufen Yu
2018-04-27 22:22 ` David Woodhouse [this message]
2018-05-04 8:06 ` yuyufen
2018-05-04 8:18 ` David Woodhouse
2018-05-04 9:27 ` yuyufen
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=1524867762.18504.89.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=Joakim.Tjernlund@infinera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yuyufen@huawei.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®