From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Kenneth <liguozhu@huawei.com>
Cc: kosaki.motohiro@jp.fujitsu.com, greg@kroah.com,
linux-kernel@vger.kernel.org,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Andi Kleen <andi@firstfloor.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: Problem with debugfs
Date: Tue, 21 Sep 2010 16:23:56 +0900 (JST) [thread overview]
Message-ID: <20100921162316.3C03.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20100921061310.GA11526@localhost>
> Hello, Mr. Greg,
>
> I'm sorry I had not checked the git before sending my last mail.
>
> For the problem I mention, consider this scenarios:
>
> 1. mm/hwpoinson-inject.c create a debugfs file with
> debugfs_create_u64("corrupt-filter-flags-mask", ...,
> &hwpoison_filter_flags_mask)
> 2. hwpoison_filter_flags_mask is supposed to be protected by filp->priv->mutex
> of this file when it is accessed from user space.
> 3. but when it is accessed from mm/memory-failure.c:hwpoison_filter_flags,
> there is no way for the function to protect the operation (so it simply
> ignore it). This may create a competition problem.
>
> It should be a problem.
>
> I'm sorry from my poor English skill.
I think your english is very clear :)
Let's cc hwpoison folks.
- kosaki
>
> Best Regards
> Kenneth Lee
>
> On Tue, Sep 21, 2010 at 10:21:12AM +0800, kenny wrote:
> > Hi, there,
> >
> > I do not know who is the maintainer for debugfs now. But I think there is
> > problem with its API: It uses filp->priv->mutex to protect the read/write (to
> > the file) for the value of its attribute, but the mutex is not exported to the
> > API user. Therefore, there is no way to protect its value when you directly
> > use the value in your module.
> >
> > Is my understanding correct?
> >
> > Thanks
> >
> >
> > Best Regards
> > Kenneth Lee
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2010-09-21 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100921022112.GA10336@localhost>
[not found] ` <20100921061310.GA11526@localhost>
2010-09-21 7:23 ` KOSAKI Motohiro [this message]
2010-09-21 7:31 ` Andi Kleen
2010-09-21 8:04 ` Wu Fengguang
2010-09-21 8:12 ` Andi Kleen
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=20100921162316.3C03.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=andi@firstfloor.org \
--cc=greg@kroah.com \
--cc=liguozhu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.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