From: Oleg Nesterov <oleg@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Guo Ren <guoren@kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Jann Horn <jannh@google.com>,
Al Viro <viro@zeniv.linux.org.uk>, Jens Axboe <axboe@kernel.dk>,
Security Officers <security@kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Naveen Rao <naveen.n.rao@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uprobes: ensure that uprobe->offset and ->ref_ctr_offset are properly aligned
Date: Wed, 6 May 2020 19:16:43 +0200 [thread overview]
Message-ID: <20200506171642.GA5678@redhat.com> (raw)
In-Reply-To: <20200506085141.723673f1@gandalf.local.home>
On 05/06, Steven Rostedt wrote:
>
> As this is in the kernel/events/ directory, I'm guessing it should be taken
> through the tip tree?
this would be great, thanks Steven.
Oleg.
next prev parent reply other threads:[~2020-05-06 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=whQt69ApMkZF8b2Q2idMDgPpPETZeeOuZg59CrOO4025w@mail.gmail.com>
[not found] ` <20200428091149.GB19958@linux.vnet.ibm.com>
[not found] ` <20200428123914.GA27920@redhat.com>
2020-05-04 16:47 ` [PATCH] uprobes: ensure that uprobe->offset and ->ref_ctr_offset are properly aligned Oleg Nesterov
2020-05-04 18:40 ` Christian Borntraeger
2020-05-05 6:49 ` Sven Schnelle
2020-06-10 2:53 ` Guo Ren
2020-05-06 5:29 ` Srikar Dronamraju
2020-05-06 12:51 ` Steven Rostedt
2020-05-06 17:16 ` Oleg Nesterov [this message]
2020-06-09 15:30 ` Oleg Nesterov
2020-06-09 16:48 ` Linus Torvalds
2020-06-09 17:43 ` Steven Rostedt
2020-06-10 2:54 ` Guo Ren
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=20200506171642.GA5678@redhat.com \
--to=oleg@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=guoren@kernel.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=security@kernel.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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.