linux-kernel - Re: [PATCH] tty/tty_io.c: make a check before reuse cdev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53D0E7E9.5090608@intel.com>
Date:	Thu, 24 Jul 2014 19:03:05 +0800
From:	"xinhui.pan" <xinhuix.pan@...el.com>
To:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
CC:	Peter Hurley <peter@...leysoftware.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	mnipxh <mnipxh@...il.com>, jslaby@...e.cz,
	linux-kernel@...r.kernel.org, yanmin_zhang@...ux.intel.com
Subject: Re: [PATCH] tty/tty_io.c: make a check before reuse cdev

于 2014年07月24日 00:07, One Thousand Gnomes 写道:
>> Very nice solution. We will check if this can cause any risk, both to kernel and user space.
>> Using a new tty base to register with new cdevs may give us more chance to wait PROCESS quit/close.
>> when total 256 tty used up, what we should do is still in discuss.
> 
> At that point you may want to look at how fuser works and create some
> kind of policy manager needs to kill problem tasks owning a device.
> 
> Or in theory there is no reason nowdays we can't go above 256 devices -
> in theory 8)
> 

hi, Alan
	Thanks for your nice comments.
In theory it can go over 256 devices, In fact, it will waste more memories. :)
We really need a policy manager that works well.
FT guys may offer it one day. it's a little long time maybe. :(

When I was a student, I heard you left from kernel.
Welcome back to kernel, I didn't know that you are back. So sorry.

thanks,

xinhui

> Alan
> 
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/