From: Greg KH <gregkh@linuxfoundation.org>
To: Pierre Paul MINGOT <mingot.pierre@gmail.com>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
jslaby@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add possibility to set /dev/tty number
Date: Tue, 5 Jan 2016 07:25:47 -0800 [thread overview]
Message-ID: <20160105152547.GC7251@kroah.com> (raw)
In-Reply-To: <CAGU20-p87f2wKj0cuey6YPeSFiQmYwg-1J0cR1-rH=+APQLfaA@mail.gmail.com>
On Tue, Jan 05, 2016 at 09:51:14AM +0100, Pierre Paul MINGOT wrote:
> In industrial sector, for obvious security and safety reasons we want
> configure our system and have a full control of the devices within it.
> So unused or dummy devices are not wanted , not nice to have.
> One way to achieve this goal is to have a full picture of the devices
> in our system and then identified which type of applications can run
> and then safety or security potential risks. Base on this analysis we
> can put in place mandatory actions to fix the risks.
> An other interest for reduce dummy /dev devices is hot-plug device
> creation detection through inotify or udev. Indeed, we can configure
> udev or inotify for monitoring the /dev directory and notify watched
> dedicated events. lesser the devices in /dev is better the response
> is. This aspect is crucial for RTOS with very high time constraint
> near of microseconds. It's the case for example for a system with
> Linux RT Patch or Xenomai.
I don't understand how reducing the number of vt devices makes anything
more or less secure, or better yet, more responsive. Please provide
specific details showing how this happens.
thanks,
greg k-h
next prev parent reply other threads:[~2016-01-05 15:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 15:34 Pierre Paul MINGOT
2016-01-04 15:43 ` Greg KH
2016-01-04 16:57 ` Austin S. Hemmelgarn
2016-01-04 17:11 ` Greg KH
2016-01-04 18:41 ` Austin S. Hemmelgarn
2016-01-04 22:55 ` One Thousand Gnomes
2016-01-05 13:16 ` Austin S. Hemmelgarn
2016-01-05 15:24 ` Greg KH
2016-01-05 15:33 ` Austin S. Hemmelgarn
2016-01-05 16:11 ` Theodore Ts'o
2016-01-05 16:22 ` Austin S. Hemmelgarn
2016-01-05 8:51 ` Pierre Paul MINGOT
2016-01-05 13:02 ` Austin S. Hemmelgarn
2016-01-05 15:25 ` Greg KH [this message]
2016-01-05 15:43 ` Austin S. Hemmelgarn
2016-01-05 16:03 ` Greg KH
2016-01-05 18:38 ` Austin S. Hemmelgarn
2016-01-05 20:47 ` One Thousand Gnomes
2016-01-06 12:42 ` Austin S. Hemmelgarn
2016-01-06 13:54 ` One Thousand Gnomes
2016-01-06 14:07 ` Austin S. Hemmelgarn
2016-01-06 13:39 ` Austin S. Hemmelgarn
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=20160105152547.GC7251@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ahferroin7@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingot.pierre@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome