From: Chen Gang <gang.chen@asianux.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: [Suggestion] fs/namespace.c: the direct cause of the warning for: "ida_remove called for id=0 which is not allocated" with mnt_release_group_id()
Date: Fri, 24 May 2013 09:26:47 +0800 [thread overview]
Message-ID: <519EC1D7.1000402@asianux.com> (raw)
In-Reply-To: <20130523161805.1faa0f8c59bfc8ee728d8c7f@linux-foundation.org>
On 05/24/2013 07:18 AM, Andrew Morton wrote:
> On Tue, 14 May 2013 17:06:30 +0800 Chen Gang <gang.chen@asianux.com> wrote:
>
>> > After call collect_mounts(), then call drop_collected_mounts(), it will
>> > report an warning: "ida_remove called for id=0 which is not allocated"
>> > (one sample is audit_add_tree_rule() in kernel/audit_tree.c).
>> >
>> > The direct cause (maybe also be the root cause):
>> > collect_mounts() passs 'CL_PRIVATE' to copy_tree() -> clone_mnt().
>> > it will set "mnt->mnt_group_id = 0" in clone_mnt().
>> > when drop_collected_mounts() -> mnt_release_group_id(), 'mnt->mnt_group_id == 0'.
> I expect this patch also addresses the bug. Can you please review and test it?
>
I am sure, after apply the patch below, it will be no warning again (fix
the direct cause).
Originally, I want to fix this bug just like the patch below, but I am
not quite sure whether it will hide the real root cause.
Thanks.
>
> From: Takashi Iwai <tiwai@suse.de>
> Subject: vfs: fix invalid ida_remove() call
>
> When the group id of a shared mount is not allocated, the umount still
> tries to call mnt_release_group_id(), which eventually hits a kernel
> warning at ida_remove() spewing a message like:
>
> ida_remove called for id=0 which is not allocated.
>
> This patch fixes the bug simply checking the group id in the caller.
>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> Reported-by: Cristian Rodr�guez <crrodriguez@opensuse.org>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> fs/pnode.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff -puN fs/pnode.c~vfs-fix-invalid-ida_remove-call fs/pnode.c
> --- a/fs/pnode.c~vfs-fix-invalid-ida_remove-call
> +++ a/fs/pnode.c
> @@ -83,7 +83,8 @@ static int do_make_slave(struct mount *m
> if (peer_mnt == mnt)
> peer_mnt = NULL;
> }
> - if (IS_MNT_SHARED(mnt) && list_empty(&mnt->mnt_share))
> + if (mnt->mnt_group_id && IS_MNT_SHARED(mnt) &&
> + list_empty(&mnt->mnt_share))
> mnt_release_group_id(mnt);
>
> list_del_init(&mnt->mnt_share);
> _
>
>
>
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2013-05-24 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 9:06 [Suggestion] fs/namespace.c: the direct cause of the warning for: "ida_remove called for id=0 which is not allocated" with mnt_release_group_id() Chen Gang
2013-05-23 23:18 ` Andrew Morton
2013-05-24 1:26 ` Chen Gang [this message]
2013-05-24 3:33 ` Chen Gang
2013-05-24 3:33 ` Chen Gang
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=519EC1D7.1000402@asianux.com \
--to=gang.chen@asianux.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--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.