All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Cc: srikar@linux.vnet.ibm.com, rostedt@goodmis.org,
	mhiramat@kernel.org, peterz@infradead.org, mingo@redhat.com,
	acme@kernel.org, alexander.shishkin@linux.intel.com,
	jolsa@redhat.com, namhyung@kernel.org,
	linux-kernel@vger.kernel.org, corbet@lwn.net,
	linux-doc@vger.kernel.org, ananth@linux.vnet.ibm.com,
	alexis.berlemont@gmail.com, naveen.n.rao@linux.vnet.ibm.com
Subject: Re: [PATCH 0/7] Uprobes: Support SDT markers having reference count (semaphore)
Date: Fri, 8 Jun 2018 18:36:01 +0200	[thread overview]
Message-ID: <20180608163600.GA9030@redhat.com> (raw)
In-Reply-To: <20180606083344.31320-1-ravi.bangoria@linux.ibm.com>

Hello,

I am travelling till the end of the next week, can't read this version
until I return. Just one question,

On 06/06, Ravi Bangoria wrote:
>
>  1. One of the major reason was the deadlock between uprobe_lock and
>  mm->mmap inside trace_uprobe_mmap(). That deadlock was not easy to fix

Could you remind what exactly was wrong?

I can't find your previous email about this problem, but iirc you didn't
explain the deadlock in details, just copied some traces from lockdep...

Oleg.

WARNING: multiple messages have this Message-ID (diff)
From: Oleg Nesterov <oleg@redhat.com>
To: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Cc: srikar@linux.vnet.ibm.com, rostedt@goodmis.org,
	mhiramat@kernel.org, peterz@infradead.org, mingo@redhat.com,
	acme@kernel.org, alexander.shishkin@linux.intel.com,
	jolsa@redhat.com, namhyung@kernel.org,
	linux-kernel@vger.kernel.org, corbet@lwn.net,
	linux-doc@vger.kernel.org, ananth@linux.vnet.ibm.com,
	alexis.berlemont@gmail.com, naveen.n.rao@linux.vnet.ibm.com
Subject: Re: [PATCH 0/7] Uprobes: Support SDT markers having reference count (semaphore)
Date: Fri, 8 Jun 2018 18:36:01 +0200	[thread overview]
Message-ID: <20180608163600.GA9030@redhat.com> (raw)
In-Reply-To: <20180606083344.31320-1-ravi.bangoria@linux.ibm.com>

Hello,

I am travelling till the end of the next week, can't read this version
until I return. Just one question,

On 06/06, Ravi Bangoria wrote:
>
>  1. One of the major reason was the deadlock between uprobe_lock and
>  mm->mmap inside trace_uprobe_mmap(). That deadlock was not easy to fix

Could you remind what exactly was wrong?

I can't find your previous email about this problem, but iirc you didn't
explain the deadlock in details, just copied some traces from lockdep...

Oleg.

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2018-06-08 16:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06  8:33 [PATCH 0/7] Uprobes: Support SDT markers having reference count (semaphore) Ravi Bangoria
2018-06-06  8:33 ` Ravi Bangoria
2018-06-06  8:33 ` [PATCH 1/7] Uprobes: Simplify uprobe_register() body Ravi Bangoria
2018-06-06  8:33   ` Ravi Bangoria
2018-06-06  8:33 ` [PATCH 2/7] Uprobes: Support SDT markers having reference count (semaphore) Ravi Bangoria
2018-06-06  8:33   ` Ravi Bangoria
2018-06-06  8:33 ` [PATCH 3/7] Uprobes/sdt: Fix multiple update of same reference counter Ravi Bangoria
2018-06-06  8:33   ` Ravi Bangoria
2018-06-06  8:33 ` [PATCH 4/7] trace_uprobe/sdt: Prevent multiple reference counter for same uprobe Ravi Bangoria
2018-06-06  8:33   ` Ravi Bangoria
2018-06-06  8:33 ` [PATCH 5/7] Uprobes/sdt: " Ravi Bangoria
2018-06-06  8:33   ` Ravi Bangoria
2018-06-06  8:33 ` [PATCH 6/7] Uprobes/sdt: Document about reference counter Ravi Bangoria
2018-06-06  8:33   ` Ravi Bangoria
2018-06-06  8:33 ` [PATCH 7/7] perf probe: Support SDT markers having reference counter (semaphore) Ravi Bangoria
2018-06-06  8:33   ` Ravi Bangoria
2018-06-06  8:35 ` [PATCH 0/7] Uprobes: Support SDT markers having reference count (semaphore) Ravi Bangoria
2018-06-06  8:35   ` Ravi Bangoria
2018-06-08  1:10 ` Masami Hiramatsu
2018-06-08  1:10   ` Masami Hiramatsu
2018-06-08  2:29   ` Ravi Bangoria
2018-06-08  2:29     ` Ravi Bangoria
2018-06-08  5:14     ` Masami Hiramatsu
2018-06-08  5:14       ` Masami Hiramatsu
2018-06-08  6:34       ` Ravi Bangoria
2018-06-08  6:34         ` Ravi Bangoria
2018-06-08 15:45         ` Masami Hiramatsu
2018-06-08 15:45           ` Masami Hiramatsu
2018-06-11  4:31           ` Ravi Bangoria
2018-06-11  4:31             ` Ravi Bangoria
2018-06-16 13:50             ` Masami Hiramatsu
2018-06-16 13:50               ` Masami Hiramatsu
2018-06-16 15:07               ` Ravi Bangoria
2018-06-16 15:07                 ` Ravi Bangoria
2018-06-08 16:36 ` Oleg Nesterov [this message]
2018-06-08 16:36   ` Oleg Nesterov
2018-06-11  4:13   ` Ravi Bangoria
2018-06-11  4:13     ` Ravi Bangoria
2018-06-20 16:37 ` Steven Rostedt
2018-06-20 16:37   ` Steven Rostedt
2018-06-21  2:35   ` Ravi Bangoria
2018-06-21  2:35     ` Ravi Bangoria

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=20180608163600.GA9030@redhat.com \
    --to=oleg@redhat.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexis.berlemont@gmail.com \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=corbet@lwn.net \
    --cc=jolsa@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.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.