Empty initial commit
Initial import of sm-t520 (T520XXUANAE)
Add .gitignore from caf/kk_3.5
Samsung warnings
drivers: gud: Delete a crazy nasty Makefile to avoid confusion

This Makefile globally changes the optimization levels as one
of the more egregious errors in it.

Just delete it so I never have to look at it again.
drivers: gud: Make the makefile sane and work with alt. output dir
picassowifi: defconfig: Rename our defconfig
picassowifi: firmware: Fix build (fixes touchscreen)
picassowifi: sec-reboot: Add "bootloader"

I type adb reboot bootloader too often for my own good, add this
as an alias for "download" to make my life easier.
picassowifi: Add some extra defines to make exynos5-insignal happy
picassowifi: Export additional include files needd by slsi
picassowifi: defconfig: Enable the Samsung MTP driver
Import Samsung source T520UEUAND1
picassowifi: defconfig: Set locale to usa
picassowifi: Add /sysfs support for scaling_available_frequencies
picassowifi: input: Switch SW_FLIP to SW_LID

This should support magnetic cases.
picassowifi: SW_LID needs the inverted state from SW_FLIP
picassowifi: defconfig: Fix derp turning off ANDROID_PARANOID_NETWORK

This broke bt (and maybe other shit).
picassowifi: consumerir: Do not defer driver init
n_tty: Fix n_tty_write crash when echoing in raw mode

The tty atomic_write_lock does not provide an exclusion guarantee for
the tty driver if the termios settings are LECHO & !OPOST.  And since
it is unexpected and not allowed to call TTY buffer helpers like
tty_insert_flip_string concurrently, this may lead to crashes when
concurrect writers call pty_write. In that case the following two
writers:
* the ECHOing from a workqueue and
* pty_write from the process
race and can overflow the corresponding TTY buffer like follows.
If we look into tty_insert_flip_string_fixed_flag, there is:
  int space = __tty_buffer_request_room(port, goal, flags);
  struct tty_buffer *tb = port->buf.tail;
  ...
  memcpy(char_buf_ptr(tb, tb->used), chars, space);
  ...
  tb->used += space;
so the race of the two can result in something like this:
              A                                B
__tty_buffer_request_room
                                  __tty_buffer_request_room
memcpy(buf(tb->used), ...)
tb->used += space;
                                  memcpy(buf(tb->used), ...) ->BOOM
B's memcpy is past the tty_buffer due to the previous A's tb->used
increment.
Since the N_TTY line discipline input processing can output
concurrently with a tty write, obtain the N_TTY ldisc output_lock to
serialize echo output with normal tty writes.  This ensures the tty
buffer helper tty_insert_flip_string is not called concurrently and
everything is fine.
Note that this is nicely reproducible by an ordinary user using
forkpty and some setup around that (raw termios + ECHO). And it is
present in kernels at least after commit
d945cb9cce20ac7143c2de8d88b187f62db99bdc (pty: Rework the pty layer to
use the normal buffering logic) in 2.6.31-rc3.
js: add more info to the commit log
js: switch to bool
js: lock unconditionally
js: lock only the tty->ops->write call
Change-Id: Ie0b03989fa8cfd6ffe40d1f770044fe7447dda05
References: CVE-2014-0196
Reported-and-tested-by: Jiri Slaby <jslaby@suse.cz>
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[bwh: Backported to 3.4: output_lock is a member of struct tty_struct]