From: Al Viro <viro@ZenIV.linux.org.uk>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block_dev: Suppress bdev_cache_init() kmemleak warninig
Date: Mon, 9 Jan 2012 23:03:16 +0000 [thread overview]
Message-ID: <20120109230316.GZ23916@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20120109224436.GA3429@swordfish>
On Tue, Jan 10, 2012 at 01:44:36AM +0300, Sergey Senozhatsky wrote:
> due to attempt to mark pointer to `struct vfsmount' as a gray object, which
> is embedded into `struct mount' returned from alloc_vfsmnt(). Pass actual
> allocated `struct mount' pointer to kmemleak_not_leak() instead.
*snort*
how about turning bd_mnt into a static instead and to hell with messing with
annotations? It's not like one word of .bss was worth those convolutions...
next prev parent reply other threads:[~2012-01-09 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 22:44 [PATCH] block_dev: Suppress bdev_cache_init() kmemleak warninig Sergey Senozhatsky
2012-01-09 23:03 ` Al Viro [this message]
2012-01-09 23:43 ` [PATCH] block_dev: Suppress bdev_cache_init() kmemleak warninig V2 Sergey Senozhatsky
2012-01-10 0:07 ` [PATCH] block_dev: Remove kmemleak header include Sergey Senozhatsky
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=20120109230316.GZ23916@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky@gmail.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 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.