All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	Linux Netdev List <netdev@vger.kernel.org>,
	Andre Naujoks <nautsch2@gmail.com>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [PATCH stable 3.11+] can: use private sk reference to detect originating socket
Date: Wed, 29 Jan 2014 22:25:44 +0100	[thread overview]
Message-ID: <52E971D8.8000701@hartkopp.net> (raw)
In-Reply-To: <1391029578.28432.64.camel@edumazet-glaptop2.roam.corp.google.com>

On 29.01.2014 22:06, Eric Dumazet wrote:
> On Wed, 2014-01-29 at 22:00 +0100, Oliver Hartkopp wrote:
>> So here we are:
>>
>> Introduced can_create_echo_skb() which creates a skb which is properly
>> owned to be send back (echo'ed) into the network stack. 
>>
>> Regards,
>> Oliver
> 
> This seems much better ;)
> 

Great!

I'll give it some more testing on my Laptop and will send the patch with a
proper description tomorrow morning.

Thanks for your support fixing this issue!

Regards,
Oliver


  reply	other threads:[~2014-01-29 21:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 13:44 [PATCH stable 3.11+] can: use private sk reference to detect originating socket Oliver Hartkopp
2014-01-29 14:38 ` Marc Kleine-Budde
2014-01-29 15:02 ` Eric Dumazet
2014-01-29 15:30   ` Eric Dumazet
2014-01-29 15:47     ` Eric Dumazet
2014-01-29 19:30       ` Oliver Hartkopp
2014-01-29 19:55         ` Eric Dumazet
2014-01-29 20:40           ` Oliver Hartkopp
2014-01-29 21:00             ` Oliver Hartkopp
2014-01-29 21:06               ` Eric Dumazet
2014-01-29 21:25                 ` Oliver Hartkopp [this message]
2014-01-30  8:32               ` Andre Naujoks
2014-01-29 16:12 ` Eric Dumazet

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=52E971D8.8000701@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=nautsch2@gmail.com \
    --cc=netdev@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
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.