From: Jiri Olsa <jolsa@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: acme@kernel.org, linux-kernel@vger.kernel.org,
namhyung@kernel.org, jolsa@kernel.org
Subject: Re: [PATCH RFC] hist lookups
Date: Tue, 6 Nov 2018 12:54:36 +0100 [thread overview]
Message-ID: <20181106115436.GE3164@krava> (raw)
In-Reply-To: <20181105.205342.1568518551892125916.davem@davemloft.net>
On Mon, Nov 05, 2018 at 08:53:42PM -0800, David Miller wrote:
>
> Jiri,
>
> Because you now run queued_events__queue() lockless with that condvar
> trick, it is possible for top->qe.in to be seen as one past the data[]
> array, this is because the rotate_queues() code goes:
>
> if (++top->qe.in > &top->qe.data[1])
> top->qe.in = &top->qe.data[0];
>
> So for a brief moment top->qe.in is out of range and thus
> perf_top__mmap_read_idx() can try to enqueue to top->qe.data[2]
>
> We can just do:
>
> if (top->qe.in == &top->qe.data[1])
> top->qe.in = &top->qe.data[0];
> else
> top->qe.in = &top->qe.data[1];
>
> Or, make top->qe.in an index, and simply go:
>
> top->qe.in ^= 1;
>
> Either way will fix the bug.
ah right.. I had originaly full mutex around that,
then I switched it off in the last patch and did
not realize this implication.. nice ;-)
does it fix the crash you reported earlier?
thanks,
jirka
next prev parent reply other threads:[~2018-11-06 11:54 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 5:03 [PATCH RFC] hist lookups David Miller
2018-10-31 12:43 ` Arnaldo Carvalho de Melo
2018-10-31 15:39 ` Jiri Olsa
2018-10-31 16:08 ` David Miller
2018-11-03 6:30 ` David Miller
2018-11-04 20:18 ` Jiri Olsa
2018-11-05 0:50 ` David Miller
2018-11-05 20:34 ` Jiri Olsa
2018-11-05 22:52 ` David Miller
2018-11-06 3:45 ` David Miller
2018-11-06 4:03 ` David Miller
2018-11-06 4:53 ` David Miller
2018-11-06 11:54 ` Jiri Olsa [this message]
2018-11-19 5:26 ` Namhyung Kim
2018-11-19 9:12 ` Jiri Olsa
2018-11-20 1:13 ` Namhyung Kim
2018-11-06 20:42 ` Jiri Olsa
2018-11-07 6:13 ` David Miller
2018-11-07 8:32 ` Jiri Olsa
2018-11-07 19:43 ` Jiri Olsa
2018-11-07 20:01 ` David Miller
2018-11-07 20:28 ` Arnaldo Carvalho de Melo
2018-11-08 6:04 ` David Miller
2018-11-08 7:13 ` Jiri Olsa
2018-11-09 1:07 ` David Miller
2018-11-11 19:41 ` Jiri Olsa
2018-11-11 19:41 ` Jiri Olsa
2018-11-11 22:32 ` David Miller
2018-11-11 22:43 ` Jiri Olsa
2018-11-11 22:58 ` David Miller
2018-11-11 23:08 ` David Miller
2018-11-11 23:26 ` Jiri Olsa
2018-11-11 23:32 ` David Miller
2018-11-13 10:40 ` Jiri Olsa
2018-11-19 4:52 ` David Miller
2018-11-19 6:28 ` Namhyung Kim
2018-11-19 6:33 ` David Miller
2018-11-19 7:16 ` Namhyung Kim
2018-11-19 9:14 ` Jiri Olsa
2018-11-06 11:51 ` Jiri Olsa
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=20181106115436.GE3164@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=davem@davemloft.net \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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 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.