With the current Linus git tree I get an occasional swiotlb allocation
error during network setup at boot-time:
ATL1E :02:00.0: swiotlb buffer is full (sz: 529461 bytes)
swiotlb: coherent allocation failed for device :02:00.0 size=529461
CPU: 0 PID: 200 Comm: ifconfig Not tainted 4.2.0-
Hi Paul,
--> http://www.linux-mips.org/archives/linux-mips/2015-09/msg00057.html
John
On 10/09/2015 20:03, Paul Burton wrote:
> Ralf: is there a reason you've only applied patch 1 of this series?
>
> v4.2 is broken because these didn't get in (despite being submitted well
> before the r
On Sat, 2015-09-12 at 11:19 +0530, Shraddha Barke wrote:
> This patch removes comparisons to true/false values on bool variables.
> Fixed using Coccinelle
Please do the "== false" and "!= false" cases at the same time
or in another patch.
> diff --git a/drivers/staging/rtl8723au/core/rtw_ap.c
>
Hello,
On Sat, 12 Sep 2015, Nicholas Krause wrote:
> This fixes locking requirements in the function ip_vs_unlink_service
> to properly use bottom half spinlocking around the call to the function
> __ip_vs_del_service in order to meet the locking that this paricular
> function requires
On 2015/9/11 16:18, Chen Feng wrote:
Add reset driver for hi6220-hikey board,this driver supply deassert
of IP. on hi6220 SoC.
Signed-off-by: Chen Feng
---
drivers/reset/Kconfig | 1 +
drivers/reset/Makefile | 1 +
drivers/reset/hisilicon/Kconfig
Add L_PTE_DIRTY to PTEs for memory range with (VM_PFNMAP|VM_PFNWRITE),
then we could avoid unneeded page protection fault in write access
first time due to L_PTE_RDONLY.
There are no valid struct pages behind VM_PFNMAP range, so it make no
sense to set L_PTE_DIRTY in page fault handler.
Signed-of
On Sat, 12 Sep 2015, Shraddha Barke wrote:
> This patch removes comparisons to true/false values on bool variables.
> Fix made using Coccinelle
>
> Signed-off-by: Shraddha Barke
> ---
> drivers/staging/vt6656/wcmd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dri
This patch removes comparisons to true/false values on bool variables.
Fix made using Coccinelle
Signed-off-by: Shraddha Barke
---
drivers/staging/rtl8712/rtl871x_ioctl_set.c | 4 --
drivers/staging/rtl8712/rtl871x_mlme.c | 3 +--
drivers/staging/rtl8712/rtl871x_recv.c | 4 +
This patch removes comparisons to true/false values on bool variables.
Fix made using Coccinelle
Signed-off-by: Shraddha Barke
---
drivers/staging/vt6656/wcmd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/vt6656/wcmd.c b/drivers/staging/vt6656/wcmd.c
index
This patch removes comparisons to true/false values on bool variables.
Fixed using Coccinelle
Signed-off-by: Shraddha Barke
---
drivers/staging/rtl8723au/core/rtw_ap.c | 4 ++--
drivers/staging/rtl8723au/core/rtw_mlme_ext.c | 2 +-
drivers/staging/rtl8723au/core/rtw_wlan_util.c
This patch removes comparisons to true/false values on bool variables.
Fix made using Coccinelle
Signed-off-by: Shraddha Barke
---
drivers/staging/rtl8188eu/core/rtw_cmd.c | 4 ++--
drivers/staging/rtl8188eu/core/rtw_ioctl_set.c | 6
drivers/staging/rtl8188eu/core/rtw_recv.c
On Fri, Sep 11, 2015 at 02:59:37PM -0700, Paul E. McKenney wrote:
>
> Queued for v4.4, thank you! Please see below for updated commit log,
> and please let me know if there are any problems with it.
>
Looks great to me! Thank you ;-)
Regards,
Boqun
> --
This patch introduces the use of the function usb_endpoint_is_bulk_in().
Signed-off-by: Shraddha Barke
---
drivers/staging/ft1000/ft1000-usb/ft1000_usb.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/ft1000/ft1000-usb/ft1000_usb.c
b/drivers/staging/
Hi all,
Please do not add material for v4.4 until after v4.3-rc1 is out.
Changes since 20150911:
Dropped tree: akpm-current (build conflict)
I used the h8300 tree from next-20150828 since the current tree has been
rebased onto something very old :-(
The drm-misc tree gained a conflict against
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 7c49b8616460ebb12ee56d80d1abfbc20b6f3cbb ("fs/notify: optimize
inotify/fsnotify code for unwatched files")
==
I really wish the commit message instead said:
"GTK+ is an initialism"
Can't I change the commit message any longer?
Diego
On Mon, Aug 31, 2015 at 3:35 AM, Jonathan Corbet wrote:
> The following changes since commit
> d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
>
> Linux 4.2-rc1 (2015-07-05 11
On Fri, Sep 11, 2015 at 2:43 PM, Mike Snitzer wrote:
> Ming, Jens, others:
>
> Please see this BZ comment that speaks to a 4.3 regression due to the
> late bio splitting changes:
> https://bugzilla.redhat.com/show_bug.cgi?id=1247382#c41
>
> But inlined here so we can continue on list:
> (In reply
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 2286c0205d1478d4bece6e733cbaf15535fba09d ("f2fs: fix to cover lock_op
for update_inode_page")
===
On 2015/09/11, 4:20 AM, "HPDD-discuss on behalf of Jeff Layton"
wrote:
>With NFSv3 nfsd will always attempt to send along WCC data to the
>client. This generally involves saving off the in-core inode information
>prior to doing the operation on the given filehandle, and then issuing a
>vfs_getatt
On Fri, Sep 11, 2015 at 09:25:02PM -0700, Guenter Roeck wrote:
> On 09/11/2015 06:00 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 4.1.7 release.
> >There are 78 patches in this series, all will be posted as a response
> >to this one. If anyone has any issue
On Fri, Sep 11, 2015 at 08:10:16PM -0600, Shuah Khan wrote:
> On 09/11/2015 07:00 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.1.7 release.
> > There are 78 patches in this series, all will be posted as a response
> > to this one. If anyone has any issue
On Fri, Sep 11, 2015 at 08:48:57PM +0530, Anjali Menon wrote:
> Added a space to fix the following coding style error detected by
> checkpatch:
>
> ERROR: spaces required around that ':' (ctx:VxE)
>
> Signed-off-by: Anjali Menon
> ---
> drivers/staging/lustre/lnet/klnds/socklnd/socklnd_cb.c | 2
On Thu, Sep 10, 2015 at 06:31:08PM +0530, Sudip Mukherjee wrote:
> On Thu, Sep 10, 2015 at 03:39:58PM +0300, Mike Rapoport wrote:
> > Hi Sudip,
> >
> > On Thu, Sep 10, 2015 at 10:10:19AM +0530, Sudip Mukherjee wrote:
> > > On Wed, Sep 09, 2015 at 01:07:04PM -0700, Greg Kroah-Hartman wrote:
> > > >
On Thu, Sep 10, 2015 at 01:27:53PM +0300, Mike Rapoport wrote:
> WILC_MALLOC(size) is wrapping a call to kmalloc(size, GFP_ATOMIC) with a
> check for 'size > 0', which kmalloc handles anyway
>
> The semantic patch that makes this change is as follows:
>
> @@
> expression v, s;
> type t;
> identif
On Thu, Sep 10, 2015 at 05:24:58PM +0530, Sudip Mukherjee wrote:
> The return pointer from dgap_getword() is used in strcmp() where it is
> dereferenced. But dgap_getword() can return NULL.
> Lets put a check there and return 0 as error.
>
> Signed-off-by: Sudip Mukherjee
> ---
> drivers/staging
On Thu, Sep 10, 2015 at 01:27:52PM +0300, Mike Rapoport wrote:
> The wilc_memory.[ch] provide wrappers to kmalloc that effectively boil down to
> calling to kmalloc with flags=GFP_ATOMIC. Replacing the calls to these
> wrappers
> with direct calls to kmalloc allows removal of the wilc_memory.[ch]
On Fri, Sep 11, 2015 at 06:06:34PM +0530, Aparna Karuthodi wrote:
> Used kstrtoul instead of simple_strtoul inorder to fix a warning
> detected by checkpatch.
> The warning is given below:
> drivers/staging/speakup/kobjects.c:156: WARNING: simple_strtoul is
> obsolete, use kstrtoul instead
>
> Sig
On Thu, Sep 10, 2015 at 06:52:22PM +0530, Sudip Mukherjee wrote:
> On Wed, Sep 09, 2015 at 11:31:37AM -0700, Greg Kroah-Hartman wrote:
> > On Fri, Sep 04, 2015 at 06:53:18PM +0530, Sudip Mukherjee wrote:
> > > These variables were only assigned some values but they were never used.
> > >
> > > Sig
On Fri, Sep 11, 2015 at 08:47:20PM +0530, Aparna Karuthodi wrote:
> Used kstrtoul instead of simple_strtoul to remove a warning detected by
> checkpatch.The warning is given below:
> drivers/staging/speakup/varhandlers.c:327: WARNING: simple_strtoul is
> obsolete, use kstrtoul instead
>
> Signed-o
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/mm.h:318:0,
from include/linux/highmem.h:7,
from include/linux/bio.h:23,
from include/linux/write
On 09/11/2015 06:00 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.1.7 release.
There are 78 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be mad
On 09/11/2015 03:49 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.52 release.
There are 18 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On 09/11/2015 03:48 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.88 release.
There are 11 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
Dne 11.9.2015 v 08:18 Robert Jarzmik napsal(a):
> Petr Cvek writes:
>
>>> Should have been posted to linux arm kernel mailing list, unless my mailer
>>> failed ...
>>>
>> Searching for:
>>
>> "ARM: pxa: add resources to pxaficp_ir"
>>
>> did not found anything, same was for "ficp" in the
>>
Good day,
I am contacting you concerning a project mutual benefits to us both. if
interested, you can reach me on my email below for more details and explanation
over the phone.
Email: ruizw...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
Hello there,
drivers/misc/mei/hbm.c:1212:46: warning: logical ‘and’ of mutually exclusive
tests is always false [-Wlogical-op]
Source code is
if (dev->hbm_state <= MEI_HBM_ENUM_CLIENTS &&
dev->hbm_state>= MEI_HBM_STOPPED) {
Maybe better code
if (dev->hbm_state <= M
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/drm_dp_helper.c
between commits:
79a2b161c12a ("drm/dp: Define AUX_RETRY_INTERVAL as 500 us")
4efa83c8c786 ("drm/dp: Adjust i2c-over-aux retry count based on message size
and i2c bus speed")
f36203
On Fri, Sep 11, 2015 at 7:15 PM, Chris Mason wrote:
>
> But flushing on schedule is a little different. It ends up calling
> blk_schedule_flush_plug() which will hand off work to kblockd through
> blk_run_queue_async()
I was more worried about some actual deadlock from the changes. And
blk_sche
Hello Linus,
Here are a few NTB bug and documentation fixes, new device IDs, and
performance improvements fixes for 4.3. Please consider pulling them.
Thanks,
Jon
The following changes since commit 64291f7db5bd8150a74ad2036f1037e6a0428df2:
Linux 4.2 (2015-08-30 11:34:09 -0700)
are availabl
On Fri, Sep 11, 2015 at 05:52:27PM -0700, Linus Torvalds wrote:
> On Fri, Sep 11, 2015 at 4:36 PM, Linus Torvalds
> wrote:
> >
> > Are we really ok with waiting synchronously for an inode while holding
> > the plug? No chance of deadlock (waiting for IO that we've plugged)?
> > That issue is true
On Fri, Sep 11, 2015 at 10:05:53AM -0700, bseg...@google.com wrote:
>
> SCHED_LOAD_RESOLUTION and the non-SLR part of SCHED_LOAD_SHIFT are not
> required to be the same value and should not be conflated.
> In particular, since cgroups are on the same timeline as tasks and their
> shares are not
On 09/11/2015 07:00 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.1.7 release.
> There are 78 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sho
On Fri, 11 Sep 2015, Kirill A. Shutemov wrote:
> On Thu, Sep 10, 2015 at 03:27:59PM +0200, Andrey Konovalov wrote:
> > Can a vma be shared among a few mm's?
>
> Define "shared".
>
> vma can belong only to one process (mm_struct), but it can be accessed
> from other process like in rmap case below
On Sat, Sep 12, 2015 at 01:28:27AM +0100, Pádraig Brady wrote:
> The open() succeeding is surprising. Is that allowed?
> The summary of the sequence in the kernel is:
>
> vfs_unlink() {
> mutex_lock(&(dentry->d_inode->i_mutex));
> security_inode_unlink(dir, dentry);
> try_break_dele
Alex,
> On Sep 11, 2015, at 11:16 AM, Alex Williamson
> wrote:
>
> RFC - Is this something we should do?
Superficially this looks pretty good. I need to think harder to be sure of the
details.
> Should we consider providing
> similar emulation through PCI sysfs to allow lspci to also make us
On Wed, Aug 12, 2015 at 04:14:50PM -0400, Roy Pledge wrote:
> +/* Lock/unlock frame queues, subject to the "LOCKED" flag. This is about
> + * inter-processor locking only. Note, FQLOCK() is always called either
> under a
> + * local_irq_save() or from interrupt context - hence there's no need for
On 09/11/2015 04:49 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.52 release.
> There are 18 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On 09/11/2015 04:48 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.88 release.
> There are 11 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
This is the start of the stable review cycle for the 4.1.7 release.
There are 78 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Mon Sep 14 00:57:37 UTC 2015.
Anything received
On Fri, Sep 11, 2015 at 06:16:01PM -0600, Shuah Khan wrote:
> On 09/11/2015 04:49 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.1.6 release.
> > There are 78 patches in this series, all will be posted as a response
> > to this one. If anyone has any issue
On Fri, Sep 11, 2015 at 11:16:30PM +, Holger Hoffstätte wrote:
> On Fri, 11 Sep 2015 15:49:01 -0700, Greg Kroah-Hartman wrote:
>
> > This is the start of the stable review cycle for the 4.1.6 release.
>
> You've been away for too long, this should be 4.1.7. ;)
Ugh, you are right, now fixed..
'syncrhronization' is wrong spell. 'synchronization' is correct.
Signed-off-by: Junesung Lee
---
drivers/staging/android/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/android/Kconfig b/drivers/staging/android/Kconfig
index 24d657b..0a9a7b3 100644
---
On Fri, Sep 11, 2015 at 4:36 PM, Linus Torvalds
wrote:
>
> Are we really ok with waiting synchronously for an inode while holding
> the plug? No chance of deadlock (waiting for IO that we've plugged)?
> That issue is true even of the current code, though, and I have _not_
> really thought that thr
On (09/11/15 15:21), Andrew Morton wrote:
> > From: Sergey SENOZHATSKY
> >
> > Constify `struct zpool' ->type.
> >
>
> I think I prefer Dan's patch, which deletes stuff:
Sure, agree. Somehow I overlooked it.
-ss
> From: Dan Streetman
> Subject: zpool: remove redundant zpool->type s
I know the error message says I can try using the "no_fwh_detect" option.
So, I am not asking how to fix this error. I am asking what it means,
and what the difference is if the module would load with the firmware
space not locked read only, versus it loading locked but with the
no_fwh_detect opt
Hi,
We're noticing a rare race here with open() in tail(1), where this happens:
tail --follow=name "file"
/* "file" is unlinked() by another process */
read(IN_ATTRIB from inotify); /* for st_nlink-- */
open("file") /* Done to check if deleted, but this succeeds! */
The open() succ
On 09/11/2015 04:49 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.1.6 release.
> There are 78 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sho
From: David Daney
The config space for external PCIe root complexes on some Cavium
ThunderX SoCs is very similar to CAM and ECAM, but differs in the
shift values that have to be applied to the bus and devfn numbers to
compose that address window offset. These root complexes also have
the interes
On 9/11/15 06:32, Andrew Morton wrote:
> On Thu, 3 Sep 2015 12:14:51 +0800 gang.chen.5...@gmail.com wrote:
>
> size(1) says this generates more object code. And that probably means
> slightly worse code. I didn't investigate, but probably the compiler
> is now preparing those five args at two d
在 2015/9/12 6:45, Heiko Stübner 写道:
Hi Shawn,
Am Freitag, 11. September 2015, 15:25:41 schrieb Shawn Lin:
Add cap-sd-highspeed and cap-mmc-highspeed for rk3066a
platform to make sd cards running faster.
Signed-off-by: Shawn Lin
---
arch/arm/boot/dts/rk3066a.dtsi | 2 ++
1 file changed, 2
Am Freitag, 11. September 2015, 13:40:35 schrieb Kevin Hilman:
> Caesar Wang writes:
> > Thank you all for providing inputs and comments on previous versions of
> > this patchset.
> > Especially thanks to the (Kevin, Heiko, Dmitry, Doug, ULF, Michael).
> >
> > Add power domain drivers based o
If a regmap is using fast_io, allocate the scratch buffer in
regmap_bulk_write() with GFP_ATOMIC instead of GFP_KERNEL.
Otherwise we may schedule while atomic.
Reported-by: Abhijeet Dharmapurikar
Signed-off-by: Stephen Boyd
---
Changes since v1:
* Only modify allocations in regmap_bulk_write()
On Fri, Sep 11, 2015 at 4:16 PM, Chris Mason wrote:
>
> For 4.3 timeframes, what runs do you want to see numbers for:
>
> 1) revert
> 2) my hack
> 3) plug over multiple sbs (on different devices)
> 4) ?
Just 2 or 3.
I don't think the plain revert is all that interesting, and I think
the "anythin
Hi Linus,
Could you please add this to 4.3 for merge window. Since this is a single patch
I'm not bothering with a pull request.
Thx,
-Vineet
Vineet Gupta (1):
ARCv2: [axs103_smp] Reduce clk for SMP FPGA configs
arch/arc/plat-axs10x/axs10x.c | 2 ++
1 file changed, 2 insertions(+)
--
1.9.1
Newer bitfiles needs the reduced clk even for SMP builds
Cc: #4.2
Signed-off-by: Vineet Gupta
---
arch/arc/plat-axs10x/axs10x.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arc/plat-axs10x/axs10x.c b/arch/arc/plat-axs10x/axs10x.c
index ad9825d4026a..0a77b19e1df8 100644
--- a/arch
On Fri 11 Sep 14:01 PDT 2015, Andy Gross wrote:
> This patch adds stubs for the SCM functions exposed in the QCOM SCM API.
>
> Signed-off-by: Andy Gross
> ---
> drivers/firmware/Kconfig |8 +
> drivers/firmware/Makefile |3 +-
> drivers/firmware/qcom_scm-64.c | 63
> ++
From: David Daney
The pci-host-generic driver keeps a global struct pci_ops which it
then patches with the .map_bus method appropriate for the bus device.
A problem arises when the driver is used for two different types of
bus devices, the .map_bus method for the last device probed clobbers
the m
From: David Daney
If the bus is being configured with a bus-range that does not start at
zero, pass that starting bus number to pci_scan_root_bus(). Passing
the incorrect value of zero causes attempted config accesses outside
of the supported range, which cascades to an OOPs spew and eventual
ke
From: David Daney
There are two problems with the bus_max calculation:
1) The u8 data type can overflow for large config space windows.
2) The calculation is incorrect for a bus range that doesn't start at
zero.
Since the configuration space is relative to bus zero, make bus_max
just be the
From: David Daney
Use pci_walk_bus() to restrict the fixup irq actions to only the bus
being created.
If we create multiple buses with pci-host-generic, or there are buses
created by other drivers, we don't want to call pci_fixup_irqs() which
operates on all devices, not just the devices on the
From: David Daney
While using the pci-host-generic driver to add PCI support for the
Cavium ThunderX processors, several bugs were discovered. We also
need the ability to specify a per-bus MSI controller, so support for
that was added.
David Daney (6):
PCI: Make global and export pdev_fixup_i
From: David Daney
If the device tree node for the bus has a "msi-parent" property, use
that as the default MSI controller for devices on the bus. Add device
tree binding documentation describing the new property.
This allows the pci-host-generic driver to be used in systems with
multiple MSI co
On Fri, 11 Sep 2015, Vinson Lee wrote:
Hi.
With the latest Linux 4.3-rc1, I am hitting this build error on CentOS 5.11.
HOSTCC scripts/sign-file
scripts/sign-file.c:23:25: fatal error: openssl/cms.h: No such file or directory
#include
fwiw/rant, I have run into kernel build issues recentl
From: David Daney
Follow-on patch will use pdev_fixup_irq(). So, make it visible and
export it.
Signed-off-by: David Daney
---
drivers/pci/setup-irq.c | 7 ---
include/linux/pci.h | 3 +++
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/pci/setup-irq.c b/drivers
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Manfred Spraul
commit 3ed1f8a99d70ea1cd1508910eb107d0edcae5009 upstream.
sem_lock() did not properly pair memory barriers:
!spin_is_locked() and spin_unlock_wait() are both only control barri
From: Alexey Khoroshilov
Date: Sat, 12 Sep 2015 00:34:48 +0300
> ali_ircc_sir_change_speed() is always called with self->lock held,
> so acquiring the lock inside it leads to unavoidable deadlock.
>
> Call graph:
> ali_ircc_sir_change_speed() is called from ali_ircc_change_speed()
> ali_ircc_f
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: "Herton R. Krzesinski"
commit 602b8593d2b4138c10e922eeaafe306f6b51817b upstream.
The current semaphore code allows a potential use after free: in
exit_sem we may free the task's sem_undo_list
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Wanpeng Li
commit 4f32be677b124a49459e2603321c7a5605ceb9f8 upstream.
After trying to drain pages from pagevec/pageset, we try to get reference
count of the page again, however, the reference c
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Thornber
commit 7f518ad0a212e2a6fd68630e176af1de395070a7 upstream.
The device details and mapping trees were just being decremented
before. Now btree_del() is called to do a deep delete.
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Richard Weinberger
commit c0ddc8c745b7f89c50385fd7aa03c78dc543fa7a upstream.
In kbuild it is allowed to define objects in files named "Makefile"
and "Kbuild".
Currently localmodconfig reads ob
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit fed66e2cdd4f127a43fd11b8d92a99bdd429528c upstream.
Vince reported that the fasync signal stuff doesn't work proper for
inherited events. So fix that.
Installing fasync a
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Horia Geant?
commit b310c178e6d897f82abb9da3af1cd7c02b09f592 upstream.
When doing pointer operation for accessing the HW S/G table,
a value representing number of entries (and not number of by
On Fri, Sep 11, 2015 at 03:06:18PM -0700, Linus Torvalds wrote:
> On Fri, Sep 11, 2015 at 2:04 PM, Linus Torvalds
> wrote:
> >
> > Of course, actual numbers would be the deciding factor if this really
> > is noticeable. But "cleaner code and saner locking" is definitely an
> > issue at least for m
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit 8f2777f53e3d5ad8ef2a176a4463a5c8e1a16431 upstream.
Since fc_fcp_cleanup_cmd() can sleep this function must not
be called while holding a spinlock. This patch avoids that
This is the start of the stable review cycle for the 3.10.88 release.
There are 11 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Sep 13 22:45:08 UTC 2015.
Anything receiv
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit e037239e5e7b61007763984aa35a8329596d8c88 upstream.
Signed-off-by: Alex Deucher
Signed-off-by: Greg Kroah-Hartman
---
include/drm/drm_pciids.h |1 +
1 file changed,
This is the start of the stable review cycle for the 3.14.52 release.
There are 18 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Sep 13 22:46:12 UTC 2015.
Anything receiv
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Wanpeng Li
commit 4f32be677b124a49459e2603321c7a5605ceb9f8 upstream.
After trying to drain pages from pagevec/pageset, we try to get reference
count of the page again, however, the reference c
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit fed66e2cdd4f127a43fd11b8d92a99bdd429528c upstream.
Vince reported that the fasync signal stuff doesn't work proper for
inherited events. So fix that.
Installing fasync a
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Manfred Spraul
commit 3ed1f8a99d70ea1cd1508910eb107d0edcae5009 upstream.
sem_lock() did not properly pair memory barriers:
!spin_is_locked() and spin_unlock_wait() are both only control barri
+ Joachim
On Wed, Aug 19, 2015 at 03:26:44PM +0530, Jagan Teki wrote:
> Since write enabling shall do with buf and len without
> need of exctra write_enable argument, hence removed the
> same from write_reg.
I rewrote this description a bit.
> Signed-off-by: Jagan Teki
> Cc: David Woodhouse
>
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Thornber
commit 7f518ad0a212e2a6fd68630e176af1de395070a7 upstream.
The device details and mapping trees were just being decremented
before. Now btree_del() is called to do a deep delete.
On Fri, 11 Sep 2015, Waiman Long wrote:
A sample of statistics counts after system bootup (with vCPU
overcommit) was:
hash_hops_count=9001
kick_latencies=138047878
kick_unlock_count=9001
kick_wait_count=9000
spurious_wakeup=3
wait_again_count=2
wait_head_count=10
wait_node_count=8994
wake_laten
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Richard Weinberger
commit c0ddc8c745b7f89c50385fd7aa03c78dc543fa7a upstream.
In kbuild it is allowed to define objects in files named "Makefile"
and "Kbuild".
Currently localmodconfig reads ob
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit c7999c6f3fed9e383d3131474588f282ae6d56b9 upstream.
I ran the perf fuzzer, which triggered some WARN()s which are due to
trying to stop/restart an event on the wrong CPU.
On Fri, Sep 11, 2015 at 4:06 PM, Chris Mason wrote:
>
> Originally I was worried about the latency impact of holding the
> plugs over more than one super with high end flash. I just didn't want
> to hold onto the IO for longer than we had to.
>
> But, since this isn't really latency sensitive any
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "Herton R. Krzesinski"
commit 602b8593d2b4138c10e922eeaafe306f6b51817b upstream.
The current semaphore code allows a potential use after free: in
exit_sem we may free the task's sem_undo_list
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Hellstrom
commit 3e04e2fe6d87807d27521ad6ebb9e7919d628f25 upstream.
This addresses two issues that cause problems with viewperf maya-03 in
situation with memory pressure.
The first iss
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit e037239e5e7b61007763984aa35a8329596d8c88 upstream.
Signed-off-by: Alex Deucher
Signed-off-by: Greg Kroah-Hartman
---
include/drm/drm_pciids.h |1 +
1 file changed,
This is the start of the stable review cycle for the 4.1.6 release.
There are 78 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Sep 13 22:45:29 UTC 2015.
Anything received
1 - 100 of 788 matches
Mail list logo
