linux-kernel - Re: Killing the tty lock

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 2 May 2012 13:36:53 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Killing the tty lock

On Wed, May 02, 2012 at 11:45:15AM +0100, Alan Cox wrote:
> > It's mostly pretty "sane", but what is this:
> > 
> > > +/*
> > > + * Getting the big tty mutex for a pair of ttys with lock ordering
> > > + * On a non pty/tty pair tty2 can be NULL which is just fine.
> > > + */
> > > +void __lockfunc tty_lock_pair(struct tty_struct *tty,
> > > +					struct tty_struct *tty2)
> > > +{
> > > +	if (tty < tty2) {
> > > +		tty_lock(tty);
> > > +		tty_lock(tty2);
> > > +	} else {
> > > +		if (tty2 && tty2 != tty)
> > > +			tty_lock(tty2);
> > > +		tty_lock(tty);
> > > +	}
> > > +}
> > > +EXPORT_SYMBOL(tty_lock_pair);
> > > +
> > > +void __lockfunc tty_unlock_pair(struct tty_struct *tty,
> > > +						struct tty_struct *tty2)
> > > +{
> > > +	tty_unlock(tty);
> > > +	if (tty2 && tty2 != tty)
> > > +		tty_unlock(tty2);
> > > +}
> > > +EXPORT_SYMBOL(tty_unlock_pair);
> > 
> > for?
> 
> We need to take locks on a pair of tty devices at the same time in some
> cases (pty/tty pairs).

Ok.

> > And what's with the comparing of pointers as "<"?  How portable is that
> > really, and how are we supposed to control the memory location of these
> > structures?
> 
> You don't need to. The point is that we must lock any arbitrary pair of
> tty structs in a defined order. Pointer comparisons work just fine for
> this. The fs layer uses similar logic for inode locking. We only care
> that for any given pair of objects the lock ordering is consistent.

Ah, ok, that makes more sense, sorry, I didn't understand that.

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