From: Eric Biggers <ebiggers3@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Alexander Potapenko <glider@google.com>,
dvyukov@google.com, kcc@google.com, viro@zeniv.linux.org.uk,
ebiggers@google.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] mbcache: initialize entry->e_referenced in mb_cache_entry_create()
Date: Fri, 15 Sep 2017 20:57:11 -0700 [thread overview]
Message-ID: <20170916035711.GB6901@zzz.localdomain> (raw)
In-Reply-To: <20170706182725.39194-1-glider@google.com>
On Thu, Jul 06, 2017 at 08:27:25PM +0200, Alexander Potapenko wrote:
> KMSAN reported use of uninitialized |entry->e_referenced| in a condition
> in mb_cache_shrink():
>
This still hasn't been fixed yet. I think mbcache patches usually go in through
the ext4 tree --- Ted, can you take this patch through the ext4 tree sometime?
Eric
prev parent reply other threads:[~2017-09-16 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 18:27 [PATCH] mbcache: initialize entry->e_referenced in mb_cache_entry_create() Alexander Potapenko
2017-07-06 22:24 ` Eric Biggers
2017-09-16 3:57 ` Eric Biggers [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=20170916035711.GB6901@zzz.localdomain \
--to=ebiggers3@gmail.com \
--cc=dvyukov@google.com \
--cc=ebiggers@google.com \
--cc=glider@google.com \
--cc=kcc@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--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 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).