UBUNTU: Start new release

Ignore: yes
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
drm/i915: Make data/link N value power of two

BugLink: http://bugs.launchpad.net/bugs/1212376

The BIOS uses power of two values for the data/link N value.

Follow suit to make the Zotac DP to dual-HDMI dongle work.

v2: Clean up the magic numbers and defines
    Change the N clamping to be a bit easier on the eye
    Rename intel_reduce_ratio to intel_reduce_m_n_ratio

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=49402
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=59810
Tested-by:  Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
[Haitao Zhang: backport to 3.8 from commit a65851af59387146a28a928c3e7bb17dabc5db72 upstream]
Signed-off-by: Haitao Zhang <haitao.zhang@canonical.com>
Signed-off-by: Kamal Mostafa <kamal@canonical.com>
Signed-off-by: Brad Figg <brad.figg@canonical.com>

(cherry picked from commit b92ae13bf2b9610bef48c1b64c0b4dcdf47a4053 ubuntu-raring)
Cc: Timo Aaltonen <timo.aaltonen@canonical.com>
Signed-off-by: Adam Lee <adam.lee@canonical.com>
Acked-by: Tim Gardner <tim.gardner@canonical.com>
Acked-by: Andy Whitcroft <apw@canonical.com>
Signed-off-by: Andy Whitcroft <apw@canonical.com>
isofs: Refuse RW mount of the filesystem instead of making it RO

BugLink: http://bugs.launchpad.net/bugs/1228751

Refuse RW mount of isofs filesystem. So far we just silently changed it
to RO mount but when the media is writeable, block layer won't notice
this change and thus will think device is used RW and will block eject
button of the drive. That is unexpected by users because for
non-writeable media eject button works just fine.

Userspace mount(8) command handles this just fine and retries mounting
with MS_RDONLY set so userspace shouldn't see any regression.  Plus any
tool mounting isofs is likely confronted with the case of read-only
media where block layer already refuses to mount the filesystem without
MS_RDONLY set so our behavior shouldn't be anything new for it.

Reported-by: Hui Wang <hui.wang@canonical.com>
Signed-off-by: Jan Kara <jack@suse.cz>
(cherry picked from commit 17b7f7cf58926844e1dd40f5eb5348d481deca6a)
Signed-off-by: Hui Wang <hui.wang@canonical.com>
Acked-by: Tim Gardner <tim.gardner@canonical.com>
Acked-by: Andy Whitcroft <apw@canonical.com>
Signed-off-by: Andy Whitcroft <apw@canonical.com>
udf: Standardize return values in mount sequence

BugLink: http://bugs.launchpad.net/bugs/1228751

Change all function used in filesystem discovery during mount to user
standard kernel return values - -errno on error, 0 on success instead
of 1 on failure and 0 on success. This allows us to pass error number
(not just failure / success) so we can abort device scanning earlier
in case of errors like EIO or ENOMEM . Also we will be able to return
EROFS in case writeable mount is requested but writing isn't supported.

Signed-off-by: Jan Kara <jack@suse.cz>
(back ported from commit d759bfa4e7919b89357de50a2e23817079889195)

Conflicts:
	fs/udf/super.c
Signed-off-by: Hui Wang <hui.wang@canonical.com>
Acked-by: Tim Gardner <tim.gardner@canonical.com>
Acked-by: Andy Whitcroft <apw@canonical.com>
Signed-off-by: Andy Whitcroft <apw@canonical.com>
udf: Refuse RW mount of the filesystem instead of making it RO

BugLink: http://bugs.launchpad.net/bugs/1228751

Refuse RW mount of udf filesystem. So far we just silently changed it
to RO mount but when the media is writeable, block layer won't notice
this change and thus will think device is used RW and will block eject
button of the drive. That is unexpected by users because for
non-writeable media eject button works just fine.

Userspace mount(8) command handles this just fine and retries mounting
with MS_RDONLY set so userspace shouldn't see any regression.  Plus any
tool mounting udf is likely confronted with the case of read-only
media where block layer already refuses to mount the filesystem without
MS_RDONLY set so our behavior shouldn't be anything new for it.

Reported-by: Hui Wang <hui.wang@canonical.com>
Signed-off-by: Jan Kara <jack@suse.cz>
(cherry picked from commit e729eac6f65e11c5f03b09adcc84bd5bcb230467)
Signed-off-by: Hui Wang <hui.wang@canonical.com>
Acked-by: Tim Gardner <tim.gardner@canonical.com>
Acked-by: Andy Whitcroft <apw@canonical.com>
Signed-off-by: Andy Whitcroft <apw@canonical.com>
cciss: fix info leak in cciss_ioctl32_passthru()

BugLink: http://bugs.launchpad.net/bugs/1188355

CVE-2013-2147

The arg64 struct has a hole after ->buf_size which isn't cleared.  Or if
any of the calls to copy_from_user() fail then that would cause an
information leak as well.

This was assigned CVE-2013-2147.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Mike Miller <mike.miller@hp.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
(cherry picked from commit 58f09e00ae095e46ef9edfcf3a5fd9ccdfad065e)
Signed-off-by: Luis Henriques <luis.henriques@canonical.com>
Acked-by: Andy Whitcroft <andy.whitcroft@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
cpqarray: fix info leak in ida_locked_ioctl()

BugLink: http://bugs.launchpad.net/bugs/1188355

CVE-2013-2147

The pciinfo struct has a two byte hole after ->dev_fn so stack
information could be leaked to the user.

This was assigned CVE-2013-2147.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Mike Miller <mike.miller@hp.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
(cherry picked from commit 627aad1c01da6f881e7f98d71fd928ca0c316b1a)
Signed-off-by: Luis Henriques <luis.henriques@canonical.com>
Acked-by: Andy Whitcroft <andy.whitcroft@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
UBUNTU: Ubuntu-3.5.0-42.65

Signed-off-by: Brad Figg <brad.figg@canonical.com>
UBUNTU: [Config] add the lowlatency flavours

Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: SAUCE: Made kernel irq-threaded by default

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: Look for releases marked Lowlatency instead of Ubuntu

The printchanges target needs to look for Lowlatency instead of Ubuntu
when searching for changes to print since the last release.

Signed-off-by: Luke Yelavich <themuso@ubuntu.com>
Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: Lowlatency-3.5.0-1.1

Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: hooks -- should use :: to maintain unordered hooks

Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: Start new release

Ignore: yes
UBUNTU: rebase to Ubuntu-3.5.0-2.2

Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: Bump ABI

Ignore: yes

Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: [Config] update Vcs-git: to point to current home

Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: [Config] drop last references to lowlatency-pae

This no longer exists in the all PAE world.

Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: Lowlatency-3.5.0-2.2

Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: [Config] drop -pae from d-i configuration.

Grrr.  This somehow evaded the previous eradication.

Signed-off-by: Andy Whitcroft <apw@canonical.com>