From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "sitsofe@gmail.com" <sitsofe@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: valgrind spews
Date: Fri, 23 Mar 2018 21:49:50 +0000 [thread overview]
Message-ID: <1521841789.2535.21.camel@wdc.com> (raw)
In-Reply-To: <CALjAwxiWMRznn==MR=NGRDVsa1LtiR1EWthKgXzsO1MBADYzOg@mail.gmail.com>
On Fri, 2018-03-23 at 21:43 +0000, Sitsofe Wheeler wrote:
> On 23 March 2018 at 15:15, Bart Van Assche <Bart.VanAssche@wdc.com> wrote:
> > On Fri, 2018-03-23 at 08:49 -0600, Jens Axboe wrote:
> > > Right, this is identical to what I reported. I get tons of these with
> > > the patch, not without.
> >
> > Since I can reproduce this I will have a look at what is going on.
>
> I wonder if the manner that fio allocates redzones is incompatible
> with valgrind's due to fio's redzone's potentially being smaller than
> the size of a pointer and the pre-redzone being partially inside the
> header structure. I'm attaching a patch I made but it still seems to
> generate valgrind warnings that aren't there when falling back to
> malloc/free without pools...
Hello Sitsofe,
Have you enabled github's feature to send an e-mail every time a pull request
is created or a comment is added? This issue should have been resolved by a
pull request I submitted this morning. That pull request has been accepted by
Jens.
Bart.
next prev parent reply other threads:[~2018-03-23 21:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 16:14 valgrind spews Jens Axboe
2018-03-22 16:53 ` Sitsofe Wheeler
2018-03-22 17:01 ` Jens Axboe
2018-03-22 17:12 ` Bart Van Assche
2018-03-22 17:23 ` Jens Axboe
2018-03-22 17:27 ` Bart Van Assche
2018-03-22 17:29 ` Jens Axboe
2018-03-23 14:39 ` Sitsofe Wheeler
2018-03-23 14:49 ` Jens Axboe
2018-03-23 15:15 ` Bart Van Assche
2018-03-23 21:43 ` Sitsofe Wheeler
2018-03-23 21:49 ` Bart Van Assche [this message]
2018-03-23 22:18 ` Sitsofe Wheeler
2018-03-23 22:53 ` Jens Axboe
2018-03-22 17:08 ` Bart Van Assche
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=1521841789.2535.21.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sitsofe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox