Re: [PATCH v5 0/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

On Tue, Apr 25, 2017 at 11:21 PM, One Thousand Gnomes wrote: >> Really? By "pty", are you referring to the master? If so, as far as I know, >> to go from the slave to the master, you need one of: >> >> - ptrace access to a process that already has an FD to the master, via >>ptrace() or so (/p

Re: [PATCH v5 0/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

> Really? By "pty", are you referring to the master? If so, as far as I know, > to go from the slave to the master, you need one of: > > - ptrace access to a process that already has an FD to the master, via >ptrace() or so (/proc/$pid/fd/$fd won't work) > - for a BSD PTY (which AFAIK isn't

Re: [PATCH v5 0/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

On Tue, Apr 25, 2017 at 9:30 PM, One Thousand Gnomes wrote: > On Tue, 25 Apr 2017 15:56:32 +0200 > Jann Horn wrote: > >> On Tue, Apr 25, 2017 at 3:47 PM, Alan Cox wrote: >> >> There could be a few user programs that would be effected by this >> >> change. >> >> See:

Re: [PATCH v5 0/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

On Tue, 25 Apr 2017 15:56:32 +0200 Jann Horn wrote: > On Tue, Apr 25, 2017 at 3:47 PM, Alan Cox wrote: > >> There could be a few user programs that would be effected by this > >> change. > >> See: > >> notable programs are: agetty, cs

Re: [PATCH v6] Documentation: Input: Add uinput documentation

On Sun, Apr 23, 2017 at 03:40:50PM -0300, Marcos Paulo de Souza wrote: > Signed-off-by: Marcos Paulo de Souza > --- I adjusted wording a bit here and there and applied, thank you. > > v5 -> v6: > Resend v5, but now include a change into input_uapi.rst (added by Dmitry and > Mauro) to include

Re: [PATCH v14 00/11] mux controller abstraction and iio/i2c muxes

On Tue, 2017-04-25 at 16:55 +0200, Peter Rosin wrote: > On 2017-04-25 16:16, Peter Rosin wrote: > > On 2017-04-24 16:59, Philipp Zabel wrote: > >> On Mon, 2017-04-24 at 16:36 +0200, Peter Rosin wrote: > >> [...] > How about an atomic use_count on the mux_control, a bool shared that is > o

Re: [PATCH v14 00/11] mux controller abstraction and iio/i2c muxes

On 2017-04-25 16:16, Peter Rosin wrote: > On 2017-04-24 16:59, Philipp Zabel wrote: >> On Mon, 2017-04-24 at 16:36 +0200, Peter Rosin wrote: >> [...] How about an atomic use_count on the mux_control, a bool shared that is only set by the first consumer, and controls whether selecting lock

Re: [PATCH v4 1/2] tiocsti-restrict : Add owner user namespace to tty_struct

On Mon, 24 Apr 2017 01:15:11 -0400 Matt Brown wrote: > This patch adds struct user_namespace *owner_user_ns to the tty_struct. > Then it is set to current_user_ns() in the alloc_tty_struct function. > > This is done to facilitate capability checks against the original user > namespace that alloc

Re: [PATCH v5 0/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

> There could be a few user programs that would be effected by this > change. > See: > notable programs are: agetty, csh, xemacs and tcsh > > However, I still believe that this change is worth it given that the > Kconfig defaults to n.

Re: [PATCH v14 00/11] mux controller abstraction and iio/i2c muxes

On 2017-04-24 16:59, Philipp Zabel wrote: > On Mon, 2017-04-24 at 16:36 +0200, Peter Rosin wrote: > [...] >>> How about an atomic use_count on the mux_control, a bool shared that is >>> only set by the first consumer, and controls whether selecting locks? >> >> That has the drawback that it is hard

Re: [PATCH v5 0/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

On Tue, Apr 25, 2017 at 3:47 PM, Alan Cox wrote: >> There could be a few user programs that would be effected by this >> change. >> See: >> notable programs are: agetty, csh, xemacs and tcsh >> >> However, I still believe that this chan

[PATCH] [RFC] em28xx: allow setting the eeprom bus at cards struct

Right now, all devices use bus 0 for eeprom. However, it seems that newer versions of Terratec H6 uses a different buffer for eeprom. So, add support to use a different I2C address for eeprom and add a new card ID for the board described at: http://forum.kodi.tv/showthread.php?tid=312902