All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "sitsofe@gmail.com" <sitsofe@gmail.com>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: valgrind spews
Date: Thu, 22 Mar 2018 17:12:09 +0000	[thread overview]
Message-ID: <1521738727.2637.14.camel@sandisk.com> (raw)
In-Reply-To: <ed74b20d-cd3b-2b0a-89d1-188be58a5dae@kernel.dk>

On Thu, 2018-03-22 at 11:01 -0600, Jens Axboe wrote:
> Run it as a server:
> 
> $ valgrind ./fio --server
> $ ./fio --client=localhost null.fio
> 
> $ cat null.fio
> [null]
> bs=4k
> ioengine=null
> size=1g
> rw=read
> 
> The above was supposed to say "fio server", but apparently I missed
> putting that in...

If I run that test, Valgrind only reports the following on my laptop:

==17458== Conditional jump or move depends on uninitialised value(s)
==17458==    at 0x463FFD: __sk_out_drop (server.c:142)
==17458==    by 0x463FFD: handle_connection (server.c:1257)
==17458==    by 0x463FFD: accept_loop (server.c:1389)
==17458==    by 0x463FFD: fio_server (server.c:2468)
==17458==    by 0x464894: fio_start_server (server.c:2552)
==17458==    by 0x426F8E: parse_cmd_line (init.c:2880)
==17458==    by 0x427602: parse_options (init.c:2931)
==17458==    by 0x41134A: main (fio.c:42)
==17458== 
==17458== Conditional jump or move depends on uninitialised value(s)
==17458==    at 0x46400F: __sk_out_drop (server.c:146)
==17458==    by 0x46400F: handle_connection (server.c:1257)
==17458==    by 0x46400F: accept_loop (server.c:1389)
==17458==    by 0x46400F: fio_server (server.c:2468)
==17458==    by 0x464894: fio_start_server (server.c:2552)
==17458==    by 0x426F8E: parse_cmd_line (init.c:2880)
==17458==    by 0x427602: parse_options (init.c:2931)
==17458==    by 0x41134A: main (fio.c:42)

Where is the sk_out structure allocated? Can Valgrind know whether or not
that structure has been initialized?

Thanks,

Bart.



  reply	other threads:[~2018-03-22 17:12 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 [this message]
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
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=1521738727.2637.14.camel@sandisk.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 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.