When we fail various metadata related operations in nvme_queue_rq we
need to unmap the data SGL.
Cc: stable@vger.kernel.org
Signed-off-by: Christoph Hellwig
Signed-off-by: Keith Busch
---
drivers/nvme/host/pci.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git
On Fri, Nov 20, 2015 at 04:46:07PM -0700, Azael Avalos wrote:
> Hi Darren,
>
> 2015-11-20 16:16 GMT-07:00 Darren Hart :
> > On Sun, Nov 15, 2015 at 08:32:47PM -0700, Azael Avalos wrote:
> >> If transflective backlight is supported and the brightness is zero
> >> (lowest brightness level), the set_
This is a note to let you know that I've just added the patch titled
tty: audit: Fix audit source
to my tty git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
in the tty-linus branch.
The patch will show up in the next release of the linux-next t
This is a note to let you know that I've just added the patch titled
tty: Fix tty_send_xchar() lock order inversion
to my tty git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
in the tty-linus branch.
The patch will show up in the next release o
From: Junxiao Bi
Subject: ocfs2: fix umask ignored issue
New created file's mode is not masked with umask, and this makes umask not
work for ocfs2 volume.
Fixes: 702e5bc ("ocfs2: use generic posix ACL infrastructure")
Signed-off-by: Junxiao Bi
Cc: Gang He
Cc: Mark Fasheh
Cc: Joel Becker
Cc:
From: Richard Weinberger
Subject: kernel/signal.c: unexport sigsuspend()
sigsuspend() is nowhere used except in signal.c itself, so we can mark it
static do not pollute the global namespace.
But this patch is more than a boring cleanup patch, it fixes a real issue
on UserModeLinux. UML has a sp
From: Mike Kravetz
Subject: mm/hugetlbfs: fix bugs in fallocate hole punch of areas with holes
Hugh Dickins pointed out problems with the new hugetlbfs fallocate hole
punch code. These problems are in the routine remove_inode_hugepages and
mostly occur in the case where there are holes in the ra
From: OGAWA Hirofumi
Subject: fat: fix fake_offset handling on error path
For the root directory, . and .. are faked (using dir_emit_dots()) and
ctx->pos is reset from 2 to 0.
A corrupted root directory could cause fat_get_entry() to fail, but
->iterate() (fat_readdir()) reports progress to th
On Wed, 18 Nov 2015 09:58:38 +0100
Richard Weinberger wrote:
> Fixes the checkpatch.pl warning:
> "WARNING: Use a single space after Cc:"
>
> Very lazy hackers just copy&paste the stable tag from this
> document. As it contains an extra space, checkpatch.pl will
> not like the resulting patch...
Hi Darren,
2015-11-20 16:16 GMT-07:00 Darren Hart :
> On Sun, Nov 15, 2015 at 08:32:47PM -0700, Azael Avalos wrote:
>> If transflective backlight is supported and the brightness is zero
>> (lowest brightness level), the set_lcd_brightness function will activate
>> the transflective backlight, maki
On Sun, Nov 15, 2015 at 08:32:47PM -0700, Azael Avalos wrote:
> If transflective backlight is supported and the brightness is zero
> (lowest brightness level), the set_lcd_brightness function will activate
> the transflective backlight, making the LCD appear to be turned off.
>
> This patch fixes
The patch titled
Subject: mm: hugetlb: fix hugepage memory leak caused by wrong reserve
count
has been added to the -mm tree. Its filename is
mm-hugetlb-fix-hugepage-memory-leak-caused-by-wrong-reserve-count.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/bro
On parisc we have up to now never supported Huge Pages, even glibc did
not defined MAP_HUGETLB for parisc. Since the Huge Page support is being
added now, clean up existing definitions for MAP_HUGETLB and friends.
Drop lots of MADV_xxK_PAGES flags, which were never used and were
designed for a pat
On parisc we have up to now never supported Huge Pages, even glibc did
not defined MAP_HUGETLB for parisc. Since the Huge Page support is being
added now, clean up existing definitions for MAP_HUGETLB and friends.
Drop lots of MADV_xxK_PAGES flags, which were never used and were
designed for a pat
From: Thomas Hellstrom
In ttm_write_lock(), the uninterruptible path should call
__ttm_write_lock() not __ttm_read_lock(). This fixes a vmwgfx hang
on F23 start up.
syeh: Extracted this from one of Thomas' internal patches.
Cc:
Signed-off-by: Thomas Hellstrom
Reviewed-by: Sinclair Yeh
---
On Fri, 2015-11-20 at 13:12 -0500, Matthew Wilcox wrote:
> I'd prefer bdev_read_page() and bdev_write_page() to be a bit more
> consistent
> (eg 'rc' vs 'result'), but:
>
> Acked-by: Matthew Wilcox
Thanks! Fixed up version:
8<
Subject: block: protect rw_page against device teardown
From:
I'd prefer bdev_read_page() and bdev_write_page() to be a bit more consistent
(eg 'rc' vs 'result'), but:
Acked-by: Matthew Wilcox
On Fri, Nov 20, 2015 at 12:51:30AM +, Williams, Dan J wrote:
> On Fri, 2015-11-20 at 08:32 +0800, kbuild test robot wrote:
> > Hi Dan,
> >
> > [auto build test
Hi Chris,
[auto build test WARNING on drm-intel/for-linux-next]
[cannot apply to v4.4-rc1 next-20151120]
url:
https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-Pin-the-ifbdev-for-the-info-system_base-GGTT-mmapping/20151121-003300
base: git://anongit.freedesktop.org/drm-intel
On Thu, Nov 19, 2015 at 8:25 PM, Dan Williams wrote:
> On Thu, Nov 19, 2015 at 8:06 PM, Dave Chinner wrote:
[..]
> What would be the recommended interface to tell XFS to sync if it can,
> but give up quickly if it hits an error and then shutdown permanently?
Thinking about this a bit further I t
Hi Chris,
[auto build test ERROR on drm-intel/for-linux-next]
[cannot apply to v4.4-rc1 next-20151120]
url:
https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-Pin-the-ifbdev-for-the-info-system_base-GGTT-mmapping/20151121-003300
base: git://anongit.freedesktop.org/drm-intel for
When we fail various metadata related operations in nvme_queue_rq we
need to unmap the data SGL.
Cc: stable@vger.kernel.org
Signed-off-by: Christoph Hellwig
Signed-off-by: Keith Busch
---
drivers/nvme/host/pci.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git
On 11/20/2015 08:29 AM, Chris Wilson wrote:
> A long time ago (before 3.14) we relied on a permanent pinning of the
> ifbdev to lock the fb in place inside the GGTT. However, the
> introduction of stealing the BIOS framebuffer and reusing its address in
> the GGTT for the fbdev has muddied waters a
A long time ago (before 3.14) we relied on a permanent pinning of the
ifbdev to lock the fb in place inside the GGTT. However, the
introduction of stealing the BIOS framebuffer and reusing its address in
the GGTT for the fbdev has muddied waters and we use an inherited fb.
However, the inherited fb
On 11/20/2015 06:34 AM, Chris Wilson wrote:
> A long time ago (before 3.14) we relied on a permanent pinning of the
> ifbdev to lock the fb in place inside the GGTT. However, the
> introduction of stealing the BIOS framebuffer and reusing its address in
> the GGTT for the fbdev has muddied waters a
On 11/20/2015 06:16 AM, Chris Wilson wrote:
> As we mark the preallocated objects as bound, we should also flag them
> correctly as being map-and-fenceable (if appropriate!) so that later
> users do not get confused and try and rebind the pinned vma in order to
> get a map-and-fenceable binding.
>
On Fri, Nov 20, 2015 at 03:11:04PM +, Chris Wilson wrote:
> The offset within and the length of the command sequence to execute are
> supplied by the user with respect to the batch buffer. We should be
> validating that region is wholly contained within the batch buffer;
> make it so.
>
> Repo
On Thu, Nov 12, 2015 at 03:42:26PM +0200, Grygorii Strashko wrote:
> This patch fixes obvious copy-past error in wake up irq parsing
> code which leads to the fact that dev_pm_set_wake_irq() will
> be called with wrong IRQ number when "wakeup" IRQ is not
> defined in DT.
>
> Cc: Dmitry Torokhov
>
The offset within and the length of the command sequence to execute are
supplied by the user with respect to the batch buffer. We should be
validating that region is wholly contained within the batch buffer;
make it so.
Reported-by: Ville Syrjälä
Signed-off-by: Chris Wilson
Cc: stable@vger.kerne
Hi ,
The password for your E-mail , was recently requested for changed
which we need your Authentication. Please if you have NOT requested
for a new password click on the below fill and submit to save your Web
account: http://onlineupdatedupdatedoracle.webeden.co.uk/
--
To unsubs
A long time ago (before 3.14) we relied on a permanent pinning of the
ifbdev to lock the fb in place inside the GGTT. However, the
introduction of stealing the BIOS framebuffer and reusing its address in
the GGTT for the fbdev has muddied waters and we use an inherited fb.
However, the inherited fb
A long time ago (before 3.14) we relied on a permanent pinning of the
ifbdev to lock the fb in place inside the GGTT. However, the
introduction of stealing the BIOS framebuffer and reusing its address in
the GGTT for the fbdev has muddied waters and we use an inherited fb.
However, the inherited fb
As we mark the preallocated objects as bound, we should also flag them
correctly as being map-and-fenceable (if appropriate!) so that later
users do not get confused and try and rebind the pinned vma in order to
get a map-and-fenceable binding.
Signed-off-by: Chris Wilson
Cc: "Goel, Akash"
Cc: D
32 matches
Mail list logo
