All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Ernberg <john.ernberg@actia.se>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Cc: "Adam Engström" <adam.engstrom@actia.se>
Subject: Re: Raw CAN socket support in LXC?
Date: Fri, 8 May 2015 08:45:02 +0000	[thread overview]
Message-ID: <554C7790.1000302@actia.se> (raw)
In-Reply-To: <554C73C8.5070705@pengutronix.de>

On 2015-05-08 10:28, Marc Kleine-Budde wrote:
> On 05/08/2015 10:12 AM, John Ernberg wrote:
>> We're working on an embedded system where we're planning on wrapping our
>> applications in containers as a resource control safety measurement.
>>   From our understanding Raw CAN sockets are not yet supported in LXC,
>> and now we're wondering why.
> I don't know - I've never tried to do so. LXC make heavy use of network
> namespaces, I think netfilter (NAT, filter) is used to grant access to
> the containers.
>
> Can you elaborate your use case in more detail. Do you want to limit the
> sending of CAN frames from the containers to the outside? Do you want to
> filter on CAN-id or even the contents? What about the receiving side? Do
> you want to limit the reception to certain CAN-ids, too?
>
>> Is there any reasoning we should be aware of as to why support has not
>> been added? Except possibly "We have not seen the need" or "No one has
>> taken the time to".
> I think all of the above.
>
> regards,
> Marc
>
Hi Marc

Thank you for your reply.

Our main use-case is to prevent a possible misbehaving application to 
bring down the entire system through memory leaks, crashes etc.
At this time we have not considered any filtering or blocking of directions.

Best regards // John Ernberg

  reply	other threads:[~2015-05-08  8:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  8:12 Raw CAN socket support in LXC? John Ernberg
2015-05-08  8:28 ` Marc Kleine-Budde
2015-05-08  8:45   ` John Ernberg [this message]
2015-05-08  8:54     ` Marc Kleine-Budde
2015-05-08 11:17       ` John Ernberg
2015-05-08 11:54         ` Marc Kleine-Budde
2015-05-08 12:24           ` John Ernberg
2015-05-08 12:31             ` Marc Kleine-Budde
2015-05-08 12:40               ` John Ernberg
2015-05-11 11:45         ` Pavel Pisa
2015-05-11 13:06           ` John Ernberg
2015-05-12 18:09             ` Oliver Hartkopp

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=554C7790.1000302@actia.se \
    --to=john.ernberg@actia.se \
    --cc=adam.engstrom@actia.se \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    /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.