From: zhuyj <zyjzyj2000@gmail.com>
To: miklos@szeredi.hu, linux-unionfs@vger.kernel.org
Subject: Re: [PATCH 1/1] overlayfs: restrict structs visible in current code module
Date: Mon, 4 Jan 2016 18:40:23 +0800 [thread overview]
Message-ID: <568A4C17.80703@gmail.com> (raw)
In-Reply-To: <1451900570-28233-1-git-send-email-zyjzyj2000@gmail.com>
Sorry. Please ignore this patch.
Zhu Yanjun
On 01/04/2016 05:42 PM, zyjzyj2000@gmail.com wrote:
> From: Zhu Yanjun <zyjzyj2000@gmail.com>
>
> The structs ovl_cache_entry, ovl_dir_cache and ovl_dir_file
> are only used in the file fs/overlayfs/readdir.c. As such,
> the static keyword is inserted to define that object to be
> only visible to the current code module during compilation.
>
> Signed-off-by: Zhu Yanjun <zyjzyj2000@gmail.com>
> ---
> fs/overlayfs/readdir.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/fs/overlayfs/readdir.c b/fs/overlayfs/readdir.c
> index 70e9af5..362bc1c 100644
> --- a/fs/overlayfs/readdir.c
> +++ b/fs/overlayfs/readdir.c
> @@ -17,7 +17,7 @@
> #include <linux/cred.h>
> #include "overlayfs.h"
>
> -struct ovl_cache_entry {
> +static struct ovl_cache_entry {
> unsigned int len;
> unsigned int type;
> u64 ino;
> @@ -28,13 +28,13 @@ struct ovl_cache_entry {
> char name[];
> };
>
> -struct ovl_dir_cache {
> +static struct ovl_dir_cache {
> long refcount;
> u64 version;
> struct list_head entries;
> };
>
> -struct ovl_readdir_data {
> +static struct ovl_readdir_data {
> struct dir_context ctx;
> bool is_merge;
> struct rb_root root;
> @@ -45,7 +45,7 @@ struct ovl_readdir_data {
> int err;
> };
>
> -struct ovl_dir_file {
> +static struct ovl_dir_file {
> bool is_real;
> bool is_upper;
> struct ovl_dir_cache *cache;
prev parent reply other threads:[~2016-01-04 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 9:42 [PATCH 1/1] overlayfs: restrict structs visible in current code module zyjzyj2000
2016-01-04 10:40 ` zhuyj [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=568A4C17.80703@gmail.com \
--to=zyjzyj2000@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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;
as well as URLs for NNTP newsgroup(s).