From: Jan Kara <jack@suse.cz>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
Jan Kara <jack@suse.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] quota: Add QFMT_VFS_V1 -> quota_v2 entry to INIT_QUOTA_MODULE_NAMES
Date: Tue, 5 Feb 2013 12:29:45 +0100 [thread overview]
Message-ID: <20130205112945.GA5943@quack.suse.cz> (raw)
In-Reply-To: <51105AA8.70305@suse.com>
On Mon 04-02-13 20:04:40, Jeff Mahoney wrote:
> Commit 498c6015 (quota: Implement quota format with 64-bit space
> and inode limits) added the vfsv1 quota format but didn't add it
> to INIT_QUOTA_MODULE_NAMES.
>
> File systems using QFMT_VFS_V1 format quotas with CONFIG_QFMT_V1=m,
> will fail to enable quotas with ESRCH because the module won't be
> loaded.
>
> This patch adds it to the list.
>
> Cc: <stable@vger.kernel.org> [>=2.6.33]
> Cc: Jan Kara <jack@suse.com>
> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Thanks for the patch. Ted Tso actually found the problem few days ago as
well and is carrying the fix in his tree. So this should get fixed once the
next merge window opens.
Honza
> ---
> include/linux/quota.h | 1 +
> 1 file changed, 1 insertion(+)
>
> --- a/include/linux/quota.h
> +++ b/include/linux/quota.h
> @@ -405,6 +405,7 @@ struct quota_module_name {
> #define INIT_QUOTA_MODULE_NAMES {\
> {QFMT_VFS_OLD, "quota_v1"},\
> {QFMT_VFS_V0, "quota_v2"},\
> + {QFMT_VFS_V1, "quota_v2"},\
> {0, NULL}}
>
> #endif /* _QUOTA_ */
>
> --
> Jeff Mahoney
> SUSE Labs
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2013-02-05 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 1:04 [PATCH] quota: Add QFMT_VFS_V1 -> quota_v2 entry to INIT_QUOTA_MODULE_NAMES Jeff Mahoney
2013-02-05 11:29 ` Jan Kara [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=20130205112945.GA5943@quack.suse.cz \
--to=jack@suse.cz \
--cc=jack@suse.com \
--cc=jeffm@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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).