Konstantin Khlebnikov writes:
> On Wed, Apr 20, 2016 at 5:55 PM, Eric W. Biederman
> wrote:
>> Linus Torvalds writes:
>>
>>> On Tue, Apr 19, 2016 at 9:36 PM, Konstantin Khlebnikov
>>> wrote:
On
Konstantin Khlebnikov writes:
> On Wed, Apr 20, 2016 at 5:55 PM, Eric W. Biederman
> wrote:
>> Linus Torvalds writes:
>>
>>> On Tue, Apr 19, 2016 at 9:36 PM, Konstantin Khlebnikov
>>> wrote:
On Wed, Apr 20, 2016 at 6:04 AM, Eric W. Biederman
>
> The kernel.pty.reserve sysctl is
On Wed, Apr 20, 2016 at 5:55 PM, Eric W. Biederman
wrote:
> Linus Torvalds writes:
>
>> On Tue, Apr 19, 2016 at 9:36 PM, Konstantin Khlebnikov
>> wrote:
>>> On Wed, Apr 20, 2016 at 6:04 AM, Eric W. Biederman
The
On Wed, Apr 20, 2016 at 5:55 PM, Eric W. Biederman
wrote:
> Linus Torvalds writes:
>
>> On Tue, Apr 19, 2016 at 9:36 PM, Konstantin Khlebnikov
>> wrote:
>>> On Wed, Apr 20, 2016 at 6:04 AM, Eric W. Biederman
The kernel.pty.reserve sysctl is neutered with no way currently
Linus Torvalds writes:
> On Tue, Apr 19, 2016 at 9:36 PM, Konstantin Khlebnikov
> wrote:
>> On Wed, Apr 20, 2016 at 6:04 AM, Eric W. Biederman
>>>
>>> The kernel.pty.reserve sysctl is neutered with no way currently
>>> implemented to be able to
Linus Torvalds writes:
> On Tue, Apr 19, 2016 at 9:36 PM, Konstantin Khlebnikov
> wrote:
>> On Wed, Apr 20, 2016 at 6:04 AM, Eric W. Biederman
>>>
>>> The kernel.pty.reserve sysctl is neutered with no way currently
>>> implemented to be able to use the reserved ptys.
>>
>> I think we could
On Tue, Apr 19, 2016 at 9:36 PM, Konstantin Khlebnikov wrote:
> On Wed, Apr 20, 2016 at 6:04 AM, Eric W. Biederman
>>
>> The kernel.pty.reserve sysctl is neutered with no way currently
>> implemented to be able to use the reserved ptys.
>
> I think we could convert this into
On Tue, Apr 19, 2016 at 9:36 PM, Konstantin Khlebnikov wrote:
> On Wed, Apr 20, 2016 at 6:04 AM, Eric W. Biederman
>>
>> The kernel.pty.reserve sysctl is neutered with no way currently
>> implemented to be able to use the reserved ptys.
>
> I think we could convert this into reserve for init user
On Wed, Apr 20, 2016 at 6:04 AM, Eric W. Biederman
wrote:
>
> The /dev/ptmx device node is changed to lookup the directory entry
> "pts" in the same directory as the /dev/ptmx device node was opened
> in. If there is a "pts" entry and that entry is a devpts filesystem
>
On Wed, Apr 20, 2016 at 6:04 AM, Eric W. Biederman
wrote:
>
> The /dev/ptmx device node is changed to lookup the directory entry
> "pts" in the same directory as the /dev/ptmx device node was opened
> in. If there is a "pts" entry and that entry is a devpts filesystem
> /dev/ptmx uses that
Al Viro writes:
> On Tue, Apr 19, 2016 at 10:43:03PM -0500, Eric W. Biederman wrote:
>> >> + if (!d_can_lookup(parent))
>> >> + return -ENOENT;
>> >
>> > And how, pray tell, would a parent of anything fail to be a directory?
>>
>> It is to make that function be
Al Viro writes:
> On Tue, Apr 19, 2016 at 10:43:03PM -0500, Eric W. Biederman wrote:
>> >> + if (!d_can_lookup(parent))
>> >> + return -ENOENT;
>> >
>> > And how, pray tell, would a parent of anything fail to be a directory?
>>
>> It is to make that function be visually distinct from
On Tue, Apr 19, 2016 at 10:43:03PM -0500, Eric W. Biederman wrote:
> >> + if (!d_can_lookup(parent))
> >> + return -ENOENT;
> >
> > And how, pray tell, would a parent of anything fail to be a directory?
>
> It is to make that function be visually distinct from path_parentat
> which does
On Tue, Apr 19, 2016 at 10:43:03PM -0500, Eric W. Biederman wrote:
> >> + if (!d_can_lookup(parent))
> >> + return -ENOENT;
> >
> > And how, pray tell, would a parent of anything fail to be a directory?
>
> It is to make that function be visually distinct from path_parentat
> which does
Al Viro writes:
> On Tue, Apr 19, 2016 at 10:04:20PM -0500, Eric W. Biederman wrote:
>> +#ifdef CONFIG_UNIX98_PTYS
>> +int path_pts(struct path *path)
>> +{
>> +/* Find "pts" in the same directory as the input path */
>> +struct dentry *child, *parent;
>> +
Al Viro writes:
> On Tue, Apr 19, 2016 at 10:04:20PM -0500, Eric W. Biederman wrote:
>> +#ifdef CONFIG_UNIX98_PTYS
>> +int path_pts(struct path *path)
>> +{
>> +/* Find "pts" in the same directory as the input path */
>> +struct dentry *child, *parent;
>> +struct qstr this;
>> +
On Tue, Apr 19, 2016 at 10:04:20PM -0500, Eric W. Biederman wrote:
> +#ifdef CONFIG_UNIX98_PTYS
> +int path_pts(struct path *path)
> +{
> + /* Find "pts" in the same directory as the input path */
> + struct dentry *child, *parent;
> + struct qstr this;
> + int ret;
> +
> + ret
On Tue, Apr 19, 2016 at 10:04:20PM -0500, Eric W. Biederman wrote:
> +#ifdef CONFIG_UNIX98_PTYS
> +int path_pts(struct path *path)
> +{
> + /* Find "pts" in the same directory as the input path */
> + struct dentry *child, *parent;
> + struct qstr this;
> + int ret;
> +
> + ret
The /dev/ptmx device node is changed to lookup the directory entry
"pts" in the same directory as the /dev/ptmx device node was opened
in. If there is a "pts" entry and that entry is a devpts filesystem
/dev/ptmx uses that filesystem. Otherwise the open of /dev/ptmx
fails.
The
The /dev/ptmx device node is changed to lookup the directory entry
"pts" in the same directory as the /dev/ptmx device node was opened
in. If there is a "pts" entry and that entry is a devpts filesystem
/dev/ptmx uses that filesystem. Otherwise the open of /dev/ptmx
fails.
The
20 matches
Mail list logo