From: Theodore Ts'o <tytso@mit.edu>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>,
Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH RESEND] mbcache: initialize entry->e_referenced in mb_cache_entry_create()
Date: Sun, 7 Jan 2018 16:23:16 -0500 [thread overview]
Message-ID: <20180107212315.GC17380@thunk.org> (raw)
In-Reply-To: <20180106181038.7687-1-ebiggers3@gmail.com>
On Sat, Jan 06, 2018 at 10:10:38AM -0800, Eric Biggers wrote:
> From: Alexander Potapenko <glider@google.com>
>
> KMSAN reported use of uninitialized |entry->e_referenced| in a condition
> in mb_cache_shrink():
Thanks, applied.
- Ted
prev parent reply other threads:[~2018-01-07 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 18:10 [PATCH RESEND] mbcache: initialize entry->e_referenced in mb_cache_entry_create() Eric Biggers
2018-01-07 21:23 ` Theodore Ts'o [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=20180107212315.GC17380@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=glider@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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).