From: Eric Paris <eparis@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: viro@ZenIV.linux.org.uk, linux-kernel@vger.kernel.org,
mszeredi@suse.cz, stable@vger.kernel.org
Subject: Re: [PATCH 2/3] audit: fix refcounting in audit-tree
Date: Fri, 06 Jul 2012 13:52:53 -0400 [thread overview]
Message-ID: <1341597173.5347.5.camel@localhost> (raw)
In-Reply-To: <1340646378-5169-3-git-send-email-miklos@szeredi.hu>
On Mon, 2012-06-25 at 19:46 +0200, Miklos Szeredi wrote:
> From: Miklos Szeredi <mszeredi@suse.cz>
>
> Refcounting of fsnotify_mark in audit tree is broken. E.g:
>
> refcount
> create_chunk
> alloc_chunk 1
> fsnotify_add_mark 2
>
> untag_chunk
> fsnotify_get_mark 3
> fsnotify_destroy_mark
> audit_tree_freeing_mark 2
> fsnotify_put_mark 1
> fsnotify_put_mark 0
> via destroy_list
> fsnotify_mark_destroy -1
>
> This was reported by various people as triggering Oops when stopping auditd.
>
> We could just remove the put_mark from audit_tree_freeing_mark() but that would
> break freeing via inode destruction. So this patch simply omits a put_mark
> after calling destroy_mark (or adds a get_mark before).
>
> Next patch will clean up the remaining mess.
>
> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
> CC: stable@vger.kernel.org
Agreed this is needed. My changelog was:
audit: fix ref count problems in audit trees
Before the switch from in kernel inotify to fsnotify for audit trees the
code regularly did:
inotify_evict_watch(&chunk->watch);
put_inotify_watch(&chunk->watch);
I translated this in fsnotify_speak into:
fsnotify_destroy_mark_by_entry(chunk_entry);
fsnotify_put_mark(chunk_entry);
The problem is that the inotify_evict_watch function actually took a
reference on chunk->watch, which is what was being dropped by
put_inotify_watch(). The fsnotify code does not take such a reference
during fsnotify_destroy_mark_by_entry(). Thus we are dropping reference
counts prematurely and eventually we hit a use after free! Whoops!
Fix these call sites to not drop the extra reference.
Reported-by: Valentin Avram <aval13@gmail.com>
Reported-by: Peter Moody <pmoody@google.com>
Partial-patch-by: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
Signed-off-by: Eric Paris <eparis@redhat.com>
Maybe you can use some of that changelog in your next post? (If you do
one?) The only reason you would repost is because I don't understand
why you took a ref in some places instead of just not dropping it
everywhere...
> ---
> kernel/audit_tree.c | 5 ++---
> 1 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/audit_tree.c b/kernel/audit_tree.c
> index d52d247..31fdc48 100644
> --- a/kernel/audit_tree.c
> +++ b/kernel/audit_tree.c
> @@ -250,7 +250,6 @@ static void untag_chunk(struct node *p)
> spin_unlock(&hash_lock);
> spin_unlock(&entry->lock);
> fsnotify_destroy_mark(entry);
> - fsnotify_put_mark(entry);
> goto out;
> }
>
> @@ -293,7 +292,6 @@ static void untag_chunk(struct node *p)
> spin_unlock(&hash_lock);
> spin_unlock(&entry->lock);
> fsnotify_destroy_mark(entry);
> - fsnotify_put_mark(entry);
> goto out;
>
> Fallback:
> @@ -332,6 +330,7 @@ static int create_chunk(struct inode *inode, struct audit_tree *tree)
> spin_unlock(&hash_lock);
> chunk->dead = 1;
> spin_unlock(&entry->lock);
> + fsnotify_get_mark(entry);
> fsnotify_destroy_mark(entry);
> fsnotify_put_mark(entry);
> return 0;
Like here? Why not just avoid the atomic op altogether?
> @@ -412,6 +411,7 @@ static int tag_chunk(struct inode *inode, struct audit_tree *tree)
> spin_unlock(&chunk_entry->lock);
> spin_unlock(&old_entry->lock);
>
> + fsnotify_get_mark(chunk_entry);
> fsnotify_destroy_mark(chunk_entry);
>
> fsnotify_put_mark(chunk_entry);
> @@ -445,7 +445,6 @@ static int tag_chunk(struct inode *inode, struct audit_tree *tree)
> spin_unlock(&old_entry->lock);
> fsnotify_destroy_mark(old_entry);
> fsnotify_put_mark(old_entry); /* pair to fsnotify_find mark_entry */
> - fsnotify_put_mark(old_entry); /* and kill it */
> return 0;
> }
>
next prev parent reply other threads:[~2012-07-06 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 17:46 [PATCH 0/3] audit-tree fixes Miklos Szeredi
2012-06-25 17:46 ` [PATCH 1/3] audit: don't free_chunk() after fsnotify_add_mark() Miklos Szeredi
2012-07-06 17:43 ` Eric Paris
2012-06-25 17:46 ` [PATCH 2/3] audit: fix refcounting in audit-tree Miklos Szeredi
2012-07-06 17:52 ` Eric Paris [this message]
2012-07-11 22:24 ` Miklos Szeredi
2012-06-25 17:46 ` [PATCH 3/3] audit: clean up " Miklos Szeredi
2012-07-06 17:51 ` Eric Paris
2012-07-11 22:25 ` Miklos Szeredi
2012-07-03 11:15 ` [PATCH 0/3] audit-tree fixes Miklos Szeredi
-- strict thread matches above, loose matches on Subject: below --
2012-08-15 13:49 [PATCH 0/3] audit-tree fixes (resend) Miklos Szeredi
2012-08-15 13:49 ` [PATCH 2/3] audit: fix refcounting in audit-tree Miklos Szeredi
2012-08-21 19:03 [PATCH 0/3] audit-tree fixes Miklos Szeredi
2012-08-21 19:03 ` [PATCH 2/3] audit: fix refcounting in audit-tree Miklos Szeredi
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=1341597173.5347.5.camel@localhost \
--to=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@suse.cz \
--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.