Linux-Trace-Devel Archive on lore.kernel.org
 help / color / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Bijan Tabatabai <bijan311@gmail.com>
Cc: linux-trace-devel@vger.kernel.org, Bijan Tabatabai <bijan311@yahoo.com>
Subject: Re: [PATCH v3] trace-cmd: Stop recording when processes traced with -P exit
Date: Wed, 13 May 2020 22:23:35 -0400
Message-ID: <20200513222335.1a4a1f5a@oasis.local.home> (raw)
In-Reply-To: <CAMvvPS5j1nGMiQKcayppfijkxjeyNQK0cUHq6LZAghVSLvA3mQ@mail.gmail.com>

On Wed, 13 May 2020 20:25:46 -0500
Bijan Tabatabai <bijan311@gmail.com> wrote:

> I just tried that and discovered an interesting problem.
> After the first sleep ended, my computer completely locked up, and
> after a few minutes I decided to reset my computer.
> Then after rebooting, I checked out the master branch, recompiled, and
> tried running the same set of commands again.
> This time, my computer locked up shortly after I pressed Ctrl+C after
> both sleeps exited.
> I am running Ubuntu 20.04 with Ubuntu's version of the 5.4 kernel.
> 
> Is this a bug that has been reported before? If not, what is the
> process for "officially" reporting it?
> 

It's a kernel bug, and we just hit it a couple of weeks ago. The fix is here:

 https://lore.kernel.org/r/20200507173929.118079761@goodmis.org

It has been already added to Linus's tree and is filtering into the
stable branches (should soon be in your Ubuntu kernel).

The discussion around it is here (with the first attempted fix).

 https://lore.kernel.org/r/20200507173929.118079761@goodmis.org

The above is really just a work around, and the real fix is being
proposed and discussed here.

 https://lore.kernel.org/r/20200513152137.32426-1-joro@8bytes.org

-- Steve

      reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 17:05 Bijan Tabatabai
2020-05-13 20:16 ` Steven Rostedt
2020-05-14  1:25   ` Bijan Tabatabai
2020-05-14  2:23     ` Steven Rostedt [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=20200513222335.1a4a1f5a@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=bijan311@gmail.com \
    --cc=bijan311@yahoo.com \
    --cc=linux-trace-devel@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

Linux-Trace-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-trace-devel/0 linux-trace-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-trace-devel linux-trace-devel/ https://lore.kernel.org/linux-trace-devel \
		linux-trace-devel@vger.kernel.org
	public-inbox-index linux-trace-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-trace-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git