From: Hou Tao <houtao1@huawei.com>
To: Richard Weinberger <richard.weinberger@gmail.com>,
<boris.brezillon@bootlin.com>
Cc: <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] jffs2: fix invocations of dbg_xattr() for dead jffs2_xattr_ref
Date: Sat, 15 Dec 2018 21:17:09 +0800 [thread overview]
Message-ID: <39d00539-7845-4f1e-d95c-d6f14cde3905@huawei.com> (raw)
In-Reply-To: <CAFLxGvyfM4tKH8hVoWDuYcojcHOQABvvDKZd1Mwbc8TMC5R5Jw@mail.gmail.com>
On 2018/12/14 5:53, Richard Weinberger wrote:
> On Sun, Dec 9, 2018 at 7:52 AM Boris Brezillon
> <boris.brezillon@bootlin.com> wrote:
>>
>> On Sat, 20 Oct 2018 19:07:53 +0800
>> Hou Tao <houtao1@huawei.com> wrote:
>>
>>> When jffs2_xattr_ref is dead, xref->ic or xref->xd will be invalid
>>> because these fields will be reused as xref->ino or xref->xid,
>>> so access xref->ic->ino or xref->xd->xid will lead to Oops.
>>>
>>> Fix the problem by checking whether or not it is a dead xref.
>>>
>>> Signed-off-by: Hou Tao <houtao1@huawei.com>
>>> ---
>>> fs/jffs2/xattr.c | 9 +++++++--
>>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/fs/jffs2/xattr.c b/fs/jffs2/xattr.c
>>> index 3d40fe02b003..0c4c7891556d 100644
>>> --- a/fs/jffs2/xattr.c
>>> +++ b/fs/jffs2/xattr.c
>>> @@ -550,7 +550,8 @@ static int save_xattr_ref(struct jffs2_sb_info *c, struct jffs2_xattr_ref *ref)
>>> ref->xseqno = xseqno;
>>> jffs2_add_physical_node_ref(c, phys_ofs | REF_PRISTINE, PAD(sizeof(rr)), (void *)ref);
>>>
>>> - dbg_xattr("success on saving xref (ino=%u, xid=%u)\n", ref->ic->ino, ref->xd->xid);
>>> + dbg_xattr("success on saving xref (ino=%u, xid=%u)\n",
>>> + je32_to_cpu(rr.ino), je32_to_cpu(rr.xid));
>>
>> Nit: align the second line on the open parens (same applies to the
>> other chunk).
Thanks for pointing it out, I will fix them.
>> Sorry, I can't comment on the actual change. I'll let Richard look
>> at it.
>>
>>>
>>> return 0;
>>> }
>>> @@ -1329,7 +1330,11 @@ int jffs2_garbage_collect_xattr_ref(struct jffs2_sb_info *c, struct jffs2_xattr_
>>> rc = save_xattr_ref(c, ref);
>>> if (!rc)
>>> dbg_xattr("xref (ino=%u, xid=%u) GC'ed from %#08x to %08x\n",
>>> - ref->ic->ino, ref->xd->xid, old_ofs, ref_offset(ref->node));
>>> + is_xattr_ref_dead(ref) ?
>>> + ref->ino : ref->ic->ino,
>>> + is_xattr_ref_dead(ref) ?
>>> + ref->xid : ref->xd->xid,
>>> + old_ofs, ref_offset(ref->node));
>>> out:
>>> if (!rc)
>>> jffs2_mark_node_obsolete(c, raw);
>>
>
> Since is_xattr_ref_dead() is cheap, can you please add two macros.
> Something like:
> static inline uint32_t xattr_ref_ino(struct jffs2_xattr_ref *ref) {
> if (is_xattr_ref_dead(ref))
> return ref>ino;
> else
> return ref->ic->ino;
> }
>
> Same for xid.
>
Yes, there would be better, will do that.
Thanks,
Tao
prev parent reply other threads:[~2018-12-15 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 11:07 Hou Tao
2018-12-09 6:34 ` Hou Tao
2018-12-09 6:52 ` Boris Brezillon
2018-12-13 21:53 ` Richard Weinberger
2018-12-15 13:17 ` Hou Tao [this message]
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=39d00539-7845-4f1e-d95c-d6f14cde3905@huawei.com \
--to=houtao1@huawei.com \
--cc=boris.brezillon@bootlin.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.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®