From: Koki Sanagi <sanagi.koki@jp•fujitsu.com>
To: David Miller <davem@davemloft•net>
Cc: rostedt@goodmis•org, linux-kernel@vger•kernel.org,
netdev@vger•kernel.org, nhorman@tuxdriver•com, mingo@elte•hu,
fweisbec@gmail•com, mathieu.desnoyers@efficios•com,
tglx@linutronix•de, kosaki.motohiro@jp•fujitsu.com,
izumi.taku@jp•fujitsu.com, kaneshige.kenji@jp•fujitsu.com
Subject: Re: [PATCH] ftrace: tracepoint of net_dev_xmit sees freed skb and causes panic
Date: Fri, 03 Jun 2011 14:03:51 +0900 [thread overview]
Message-ID: <4DE86B37.4070704@jp.fujitsu.com> (raw)
In-Reply-To: <20110602.140426.765650914977149734.davem@davemloft.net>
(2011/06/03 6:04), David Miller wrote:
> From: Steven Rostedt <rostedt@goodmis•org>
> Date: Thu, 02 Jun 2011 17:01:52 -0400
>
>> On Thu, 2011-06-02 at 13:59 -0700, David Miller wrote:
>>> From: Steven Rostedt <rostedt@goodmis•org>
>>> Date: Tue, 31 May 2011 11:14:27 -0400
>>>
>>>> Note, the subject should not be "ftrace:", but "net:" or maybe even
>>>> "net/tracing", as this really has nothing to do with ftrace code. The
>>>> tracepoints are more generic than ftrace.
>>>
>>> Do you guys mind if I take this in via the net-2.6 tree?
>>
>> I have no issue with that. Heck, I prefer it.
>
> Great, thanks!
O.K.
I will resubmit this patch with appropriate subject "net/tracing:"
Thanks,
Koki Sanagi
next prev parent reply other threads:[~2011-06-03 5:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 7:48 [PATCH] ftrace: tracepoint of net_dev_xmit sees freed skb and causes panic Koki Sanagi
2011-05-31 15:13 ` Steven Rostedt
2011-05-31 16:11 ` Neil Horman
2011-05-31 16:21 ` Steven Rostedt
2011-05-31 15:14 ` Steven Rostedt
2011-06-02 20:59 ` David Miller
2011-06-02 21:01 ` Steven Rostedt
2011-06-02 21:04 ` David Miller
2011-06-03 5:03 ` Koki Sanagi [this message]
2011-06-03 5:23 ` David Miller
2011-06-03 5:57 ` Koki Sanagi
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=4DE86B37.4070704@jp.fujitsu.com \
--to=sanagi.koki@jp$(echo .)fujitsu.com \
--cc=davem@davemloft$(echo .)net \
--cc=fweisbec@gmail$(echo .)com \
--cc=izumi.taku@jp$(echo .)fujitsu.com \
--cc=kaneshige.kenji@jp$(echo .)fujitsu.com \
--cc=kosaki.motohiro@jp$(echo .)fujitsu.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mathieu.desnoyers@efficios$(echo .)com \
--cc=mingo@elte$(echo .)hu \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nhorman@tuxdriver$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox