linux-kernel - Re: [PATCH v2] TTY: pty, fix pty counting in "/proc/sys/kernel/pty/nr"

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: <20111027123742.GB7910@kroah.com>
Date:	Thu, 27 Oct 2011 14:37:42 +0200
From:	Greg KH <greg@...ah.com>
To:	Ilya Zykov <ilya@...x.ru>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] TTY: pty, fix pty counting in
 "/proc/sys/kernel/pty/nr"

On Thu, Oct 27, 2011 at 01:48:35PM +0400, Ilya Zykov wrote:
> Regression for commit: 24d406a6bf736f7aebdc8fa0f0ec86e0890c6d24
> Commit: 24d406a6b accepted in Linux 3.1.
> Disscussed on linux-kernel@...r.kernel.org "subject: [PATCH] TTY: pty, fix pty counting"
> and not accepted.
> Although, I think it's clear.

Ilya, is there some reason you are ignoring the tty maintainer and
sending these to Linus directly?  These patches need to be tested in
linux-next, so at the earliest, they can be merged into Linus's tree for
3.3, they are NOT 3.2 material, especially given that they are not even
accepted by the current tty developers.

So please work with us, and don't try to circumvent the existing
process, it is not the way we work here.

Especially as this specific patch was already rejected, for very good
reasons, why are you ignoring those reasons?

thanks,

greg k-h
--
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/