From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: <dedekind1@gmail.com>, <richard.weinberger@gmail.com>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v4] ubifs: make ubifs_[get|set]xattr atomic
Date: Sat, 7 Nov 2015 12:36:08 +0800 [thread overview]
Message-ID: <563D7FB8.60600@cn.fujitsu.com> (raw)
In-Reply-To: <1439887431.31419.110.camel@gmail.com>
On 08/18/2015 04:43 PM, Artem Bityutskiy wrote:
> On Tue, 2015-08-18 at 12:38 +0800, Dongsheng Yang wrote:
>> This commit make the ubifs_[get|set]xattr protected by ui_mutex.
>>
>> Originally, there is a possibility that ubifs_getxattr to get
>> a wrong value.
>>
>> P1 P2
>> ---------- ----------
>> ubifs_getxattr ubifs_setxattr
>> - kfree()
>> - memcpy()
>> - kmemdup()
>>
>> Then ubifs_getxattr() would get a non-sense data. To solve this
>> problem, this commit make the xattr of ubifs_inode updated in
>> atomic.
>
> Picked this one, thanks!
Hi Artem and Richard,
I did not find this one in linux-ubifs.git, is that
planed for 4.4?
Yang
> .
>
next prev parent reply other threads:[~2015-11-07 4:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 4:38 [PATCH v4] ubifs: make ubifs_[get|set]xattr atomic Dongsheng Yang
2015-08-18 8:43 ` Artem Bityutskiy
2015-11-07 4:36 ` Dongsheng Yang [this message]
2015-11-07 10:34 ` 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=563D7FB8.60600@cn.fujitsu.com \
--to=yangds.fnst@cn.fujitsu.com \
--cc=dedekind1@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.