linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [bug report] f2fs: use rb_*_cached friends
Date: Fri, 11 Jan 2019 09:55:00 +0300	[thread overview]
Message-ID: <20190111065500.GK1718@kadam> (raw)
In-Reply-To: <20190110225119.GE149637@gmail.com>

There have been a couple of these where we pass uninitialized memory to
another function which doesn't use it.  It's kind of obvious in
retrospect, but it hadn't occured to me that UBSAN would generate the
warning at the call site.  This will make us more inclined to silence
those warnings.

Thanks!

regards,
dan carpenter

      parent reply	other threads:[~2019-01-11  6:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 12:23 [bug report] f2fs: use rb_*_cached friends Dan Carpenter
2018-10-12 14:00 ` Chao Yu
2018-10-12 14:18   ` Dan Carpenter
2018-10-12 14:31     ` Chao Yu
2019-01-10 22:51   ` Eric Biggers
2019-01-11  2:00     ` Chao Yu
2019-01-11  6:55     ` Dan Carpenter [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=20190111065500.GK1718@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=ebiggers@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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).