From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Jan Kara <jack@suse.cz>, linux-fsdevel@vger.kernel.org
Cc: Dave Kleikamp <shaggy@kernel.org>,
jfs-discussion@lists.sourceforge.net, tytso@mit.edu,
Jeff Mahoney <jeffm@suse.de>, Mark Fasheh <mfasheh@suse.com>,
Dave Chinner <david@fromorbit.com>,
reiserfs-devel@vger.kernel.org, xfs@oss.sgi.com,
cluster-devel@redhat.com, linux-ext4@vger.kernel.org,
Steven Whitehouse <swhiteho@redhat.com>,
ocfs2-devel@oss.oracle.com, viro@zeniv.linux.org.uk
Subject: Re: [PATCH 11/12] jfs: Convert to private i_dquot field
Date: Fri, 10 Oct 2014 10:33:02 -0500 [thread overview]
Message-ID: <5437FC2E.6020000@oracle.com> (raw)
In-Reply-To: <1412952910-7142-12-git-send-email-jack@suse.cz>
On 10/10/2014 09:55 AM, Jan Kara wrote:
> CC: Dave Kleikamp <shaggy@kernel.org>
> CC: jfs-discussion@lists.sourceforge.net
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/jfs/jfs_incore.h | 3 +++
> fs/jfs/super.c | 13 +++++++++++++
> 2 files changed, 16 insertions(+)
>
> diff --git a/fs/jfs/jfs_incore.h b/fs/jfs/jfs_incore.h
> index cf47f09e8ac8..fa7e795bd8ae 100644
> --- a/fs/jfs/jfs_incore.h
> +++ b/fs/jfs/jfs_incore.h
> @@ -94,6 +94,9 @@ struct jfs_inode_info {
> unchar _inline_ea[128]; /* 128: inline extended attr */
> } link;
> } u;
> +#ifdef CONFIG_QUOTA
> + struct dquot *i_dquot[MAXQUOTAS];
> +#endif
> u32 dev; /* will die when we get wide dev_t */
> struct inode vfs_inode;
> };
> diff --git a/fs/jfs/super.c b/fs/jfs/super.c
> index adf8cb045b9e..a13727dd3826 100644
> --- a/fs/jfs/super.c
> +++ b/fs/jfs/super.c
> @@ -54,6 +54,7 @@ static struct kmem_cache *jfs_inode_cachep;
>
> static const struct super_operations jfs_super_operations;
> static const struct export_operations jfs_export_operations;
> +static const int jfs_inode_fields[IF_FIELD_NR];
see below
> static struct file_system_type jfs_fs_type;
>
> #define MAX_COMMIT_THREADS 64
> @@ -117,6 +118,9 @@ static struct inode *jfs_alloc_inode(struct super_block *sb)
> jfs_inode = kmem_cache_alloc(jfs_inode_cachep, GFP_NOFS);
> if (!jfs_inode)
> return NULL;
> +#ifdef CONFIG_QUOTA
> + memset(&jfs_inode->i_dquot, 0, sizeof(jfs_inode->i_dquot));
> +#endif
> return &jfs_inode->vfs_inode;
> }
>
> @@ -537,7 +541,9 @@ static int jfs_fill_super(struct super_block *sb, void *data, int silent)
> #ifdef CONFIG_QUOTA
> sb->dq_op = &dquot_operations;
> sb->s_qcop = &dquot_quotactl_ops;
> + sb_dqopt(sb)->allowed_types = QTYPE_MASK_USR | QTYPE_MASK_GRP;
> #endif
> + sb_init_inode_fields(sb, jfs_inode_fields);
>
> /*
> * Initialize direct-mapping inode/address-space
> @@ -857,6 +863,13 @@ static const struct super_operations jfs_super_operations = {
> #endif
> };
>
> +static const int jfs_inode_fields[IF_FIELD_NR] = {
> +#ifdef CONFIG_QUOTA
> + [IF_DQUOTS] = (int)offsetof(struct jfs_inode_info, i_dquot) -
> + (int)offsetof(struct jfs_inode_info, vfs_inode),
> +#endif
> +};
Why isn't the initialization done up above where jfs_inode_fields is
first defined?
> +
> static const struct export_operations jfs_export_operations = {
> .fh_to_dentry = jfs_fh_to_dentry,
> .fh_to_parent = jfs_fh_to_parent,
>
next prev parent reply other threads:[~2014-10-10 15:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 14:54 [PATCH 0/12 v2] Moving i_dquot out of struct inode Jan Kara
2014-10-10 14:54 ` [PATCH 01/12] quota: Allow each filesystem to specify which quota types it supports Jan Kara
2014-10-10 15:26 ` Dave Kleikamp
2014-10-10 15:37 ` Jan Kara
2014-10-10 14:55 ` [PATCH 02/12] gfs2: Set allowed quota types Jan Kara
2014-10-10 14:55 ` [PATCH 03/12] xfs: " Jan Kara
2014-10-10 14:55 ` [PATCH 04/12] fs: Generic infrastructure for optional inode fields Jan Kara
2014-10-10 14:55 ` [PATCH 05/12] quota: Use optional inode field for i_dquot pointers Jan Kara
2014-10-10 14:55 ` [PATCH 06/12] ext2: Convert to private i_dquot field Jan Kara
2014-10-10 14:55 ` [PATCH 07/12] ext3: " Jan Kara
2014-10-10 14:55 ` [PATCH 08/12] ext4: " Jan Kara
2014-10-10 14:55 ` [PATCH 09/12] ocfs2: " Jan Kara
2014-10-10 14:55 ` [PATCH 10/12] reiserfs: " Jan Kara
2014-10-10 14:55 ` [PATCH 11/12] jfs: " Jan Kara
2014-10-10 15:33 ` Dave Kleikamp [this message]
2014-10-10 15:40 ` Jan Kara
2014-10-10 15:43 ` Dave Kleikamp
2014-10-10 14:55 ` [PATCH 12/12] vfs: Remove i_dquot field from inode Jan Kara
2014-10-11 13:34 ` [PATCH 0/12 v2] Moving i_dquot out of struct inode Christoph Hellwig
2014-10-12 18:53 ` Al Viro
2014-10-17 19:24 ` Jan Kara
2014-10-18 15:17 ` Christoph Hellwig
2014-10-18 19:26 ` Jan Kara
2014-10-19 14:16 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2014-11-04 11:19 [PATCH 0/12 v4] " Jan Kara
2014-11-04 11:19 ` [PATCH 11/12] jfs: Convert to private i_dquot field Jan Kara
2014-11-04 14:17 ` Dave Kleikamp
2014-10-21 14:38 [PATCH 0/12 v3] Moving i_dquot out of struct inode Jan Kara
2014-10-21 14:38 ` [PATCH 11/12] jfs: Convert to private i_dquot field Jan Kara
2014-10-01 19:31 [PATCH 0/12 RFC] Moving i_dquot out of struct inode Jan Kara
2014-10-01 19:31 ` [PATCH 11/12] jfs: Convert to private i_dquot field Jan Kara
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=5437FC2E.6020000@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=cluster-devel@redhat.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=jeffm@suse.de \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=swhiteho@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).