From: Zefan Li <lizefan@huawei.com>
To: Wang Kai <morgan.wang@huawei.com>
Cc: <gregkh@linuxfoundation.org>, <viro@zeniv.linux.org.uk>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] get rid of s_files and files_lock
Date: Thu, 30 Apr 2015 11:24:38 +0800 [thread overview]
Message-ID: <5541A076.2000101@huawei.com> (raw)
In-Reply-To: <1430305255-55947-2-git-send-email-morgan.wang@huawei.com>
On 2015/4/29 19:00, Wang Kai wrote:
> From: Al Viro <viro@zeniv.linux.org.uk>
>
> commit eee5cc2702929fd41cce28058dc6d6717f723f87 upstream.
>
> The only thing we need it for is alt-sysrq-r (emergency remount r/o)
> and these days we can do just as well without going through the
> list of files.
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> [wangkai: backport to 3.10
> - address CVE-2014-8172
> - adjust context
> - leave fu.fu_list as still used in 3.10]
This doesn't sound right to me. We're removing operations on fu_list like
init/add/del, so how can it still be used?
next prev parent reply other threads:[~2015-04-30 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 11:00 [PATCH][request stable 3.10 inclusion] CVE-2014-8172 Wang Kai
2015-04-29 11:00 ` [PATCH] get rid of s_files and files_lock Wang Kai
2015-04-30 3:24 ` Zefan Li [this message]
2015-04-30 4:39 ` Wang Kai
2015-04-30 4:49 ` Zefan Li
2015-04-30 12:24 ` Wang Kai
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=5541A076.2000101@huawei.com \
--to=lizefan@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=morgan.wang@huawei.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.