linux-kernel - Re: [PATCH] tty: fix data race in tty_buffer

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: <20150917125155.GA16085@kroah.com>
Date:	Thu, 17 Sep 2015 05:51:55 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Dmitry Vyukov <dvyukov@...gle.com>
Cc:	Peter Hurley <peter@...leysoftware.com>,
	Jiri Slaby <jslaby@...e.com>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Jiri Slaby <jslaby@...e.cz>,
	Andrey Konovalov <andreyknvl@...gle.com>,
	Kostya Serebryany <kcc@...gle.com>,
	Alexander Potapenko <glider@...gle.com>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	Hans Boehm <hboehm@...gle.com>
Subject: Re: [PATCH] tty: fix data race in tty_buffer_flush

On Thu, Sep 17, 2015 at 12:28:11PM +0200, Dmitry Vyukov wrote:
> One stupid question. There is a number of branches:
>   remotes/origin/master
>   remotes/origin/tty-linus
>   remotes/origin/tty-next
>   remotes/origin/tty-testing
> 
> What branch should I base my patches on? I used master.

Right now, if you look, they all point to the same thing, so it doesn't
matter :)

tty-linus is for patches to go to Linus this kernel release.
tty-next is for patches to go to Linus the next kernel release.

Both tty-linus and tty-next show up in linux-next and are never rebased.

tty-testing is for patches that are being considered for tty-next, it
does not show up in linux-next and sometimes is rebased if things go
wrong with the patches.

Hope this helps,

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/