linux-kernel - Re: [git pull] drm intel + exynos fixes

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CA+55aFx7vAePGw7TGkXT34CohaJ5C+1kmUoQVE9h1Ek4U_Jdrg@mail.gmail.com>
Date:	Fri, 8 Jun 2012 16:37:49 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Chris Wilson <chris@...is-wilson.co.uk>
Cc:	Dave Airlie <airlied@...ux.ie>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] drm intel + exynos fixes

On Fri, Jun 8, 2012 at 3:52 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
>
> And that was my point. You were blaming the patch for making you aware
> of existing behaviour that results in utter confusion, for as Alex
> points out there is no sane way for userspace to handle the unknown
> connection status from the detection routine.

Ahh. Yes, then I agree with you. The current behavior is clearly
insane in the presense of an unknown connector status.

So if the higher levels are eventually fixed to say "if one input is
'unknown' and another is 'connected', we'll assume 'unknown' means
'not connected'", then we can re-apply that patch.

As it is, it's apparently a disaster to reply 'unknown' in this situation.

                Linus
--
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/