If a seccomp filter program is installed, older static binaries and
distributions with older libc implementations (glibc 2.13 and earlier)
that rely on vsyscall use will be terminated regardless of the filter
program policy when executing time, gettimeofday, or getcpu. This is
only the case when
Hey Thomas,
Since you're offline next week, I wanted to send you my updated
queue for the 3.6 merge window.
These are mostly the same changes I sent you with my earlier 3.6 pull
request mid-last month, but reordered and trimmed down to focus on
cleanups (no new features).
There is one
Ingo noted that using a u32 instead of int for shift values
would be better to make sure the compiler doesn't unnecessarily
use complex signed arithmetic.
CC: Ingo Molnar mi...@kernel.org
CC: Peter Zijlstra a.p.zijls...@chello.nl
CC: Richard Cochran richardcoch...@gmail.com
CC: Prarit Bhargava
From: John Stultz johns...@us.ibm.com
In commit 6b43ae8a619d17c4935c3320d2ef9e92bdeed05d, I
introduced a bug that kept the STA_INS or STA_DEL bit
from being cleared from time_status via adjtimex()
without forcing STA_PLL first.
Usually once the STA_INS is set, it isn't cleared
until the leap
Ingo noted a number of places where there is inconsistent
use of whitespace. This patch tries to address the main
culprits.
CC: Ingo Molnar mi...@kernel.org
CC: Peter Zijlstra a.p.zijls...@chello.nl
CC: Richard Cochran richardcoch...@gmail.com
CC: Prarit Bhargava pra...@redhat.com
CC: Thomas
As part of cleaning up the timekeeping code, this patch converts
a number of internal functions to takei a timekeeper ptr as an
argument, so that the internal functions don't access the global
timekeeper structure directly. This allows for further optimizations
to reduce lock hold time later.
Since we call arch_gettimeoffset() in all the accessor
functions, move arch_gettimeoffset() calls into
timekeeping_get_ns() and timekeeping_get_ns_raw() to simplify
the code.
This also makes the code easier to maintain as we don't have to
worry about forgetting the arch_gettimeoffset() as has
We do the exact same logic moving nsecs to secs in the
timekeeper in multiple places, so condense this into a
single function.
CC: Ingo Molnar mi...@kernel.org
CC: Peter Zijlstra a.p.zijls...@chello.nl
CC: Richard Cochran richardcoch...@gmail.com
CC: Prarit Bhargava pra...@redhat.com
CC: Thomas
The timekeeper struct has a xtime_nsec, which keeps the
sub-nanosecond remainder. This ends up being somewhat
duplicative of the timekeeper.xtime.tv_nsec value, and we
have to do extra work to keep them apart, copying the full
nsec portion out and back in over and over.
This patch simplifies
When we make adjustments speeding up the clock, its possible
for xtime_nsec to underflow. We already handle this properly,
but we do so from update_wall_time() instead of the more logical
timekeeping_adjust(), where the possible underflow actually
occurs.
Thus, move the correction logic to the
On 07/12/2012 11:27 PM, Simon Glass wrote
I agree the type strings are a problem in the current form - if we could get
constants in the device tree, that would be much better. Your way of
representing the sequences is interesting though, if we can solve the type
issue (and also evaluate its cost
net-next commit ad7eee98be (etherdevice: introduce eth_broadcast_addr)
added a new style API. Rename random_ether_addr to eth_random_addr to
create some API symmetry.
Joe Perches (8):
etherdevice: Rename random_ether_addr to eth_random_addr
ethernet: Use eth_random_addr
net: usb: Use
Add some API symmetry to eth_broadcast_addr and
add a #define to the old name for backward compatibility.
Signed-off-by: Joe Perches j...@perches.com
---
include/linux/etherdevice.h | 14 --
1 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/include/linux/etherdevice.h
Convert the existing uses of random_ether_addr to
the new eth_random_addr.
Signed-off-by: Joe Perches j...@perches.com
---
drivers/net/ethernet/atheros/atl1c/atl1c_hw.c |2 +-
drivers/net/ethernet/atheros/atlx/atl1.c |2 +-
drivers/net/ethernet/atheros/atlx/atl2.c |
Convert the existing uses of random_ether_addr to
the new eth_random_addr.
Signed-off-by: Joe Perches j...@perches.com
---
drivers/net/usb/smsc75xx.c |2 +-
drivers/net/usb/smsc95xx.c |2 +-
drivers/net/usb/usbnet.c |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff
Convert the existing uses of random_ether_addr to
the new eth_random_addr.
Signed-off-by: Joe Perches j...@perches.com
---
drivers/net/wireless/adm8211.c |2 +-
drivers/net/wireless/p54/eeprom.c |2 +-
drivers/net/wireless/rt2x00/rt2400pci.c|2 +-
Convert the existing uses of random_ether_addr to
the new eth_random_addr.
Signed-off-by: Joe Perches j...@perches.com
---
drivers/net/tun.c |2 +-
drivers/net/wimax/i2400m/driver.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/tun.c
Convert the existing uses of random_ether_addr to
the new eth_random_addr.
Signed-off-by: Joe Perches j...@perches.com
---
drivers/s390/net/qeth_l2_main.c |2 +-
drivers/s390/net/qeth_l3_main.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Convert the existing uses of random_ether_addr to
the new eth_random_addr.
Signed-off-by: Joe Perches j...@perches.com
---
drivers/usb/atm/xusbatm.c|4 ++--
drivers/usb/gadget/u_ether.c |2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/atm/xusbatm.c
Convert the existing uses of random_ether_addr to
the new eth_random_addr.
Signed-off-by: Joe Perches j...@perches.com
---
arch/blackfin/mach-bf537/boards/stamp.c |2 +-
arch/c6x/kernel/soc.c |2 +-
arch/mips/ar7/platform.c|4 ++--
δΊ 2012-07-12 22:55, David Vrabel ει:
On 04/07/12 07:49, zhenzhong.duan wrote:
When populate pages across a mem boundary at bootup, the page count
populated isn't correct. This is due to mem populated to non-mem
region and ignored.
Pfn range is also wrongly aligned when mem boundary isn't
On Thu, 2012-07-12 at 15:58 -0700, Andrew Morton wrote:
Just fix them up as you go - the code is already a mixture of right
and wrong (a consequence of a lot of it being wrong) - we might as
well tip it further in the right direction.
Yeah, but I'd say 80% of it has its own wrong coding
On Fri, 13 Jul 2012 08:34:44 +0300 Artem Bityutskiy dedeki...@gmail.com wrote:
On Thu, 2012-07-12 at 15:58 -0700, Andrew Morton wrote:
Just fix them up as you go - the code is already a mixture of right
and wrong (a consequence of a lot of it being wrong) - we might as
well tip it further
Hi Mark,
On Thu, Jul 12, 2012 at 22:58:37, Mark Brown wrote:
On Tue, Jul 10, 2012 at 04:39:42PM +0530, AnilKumar Ch wrote:
This commit adds device tree support for tps65217 pmic. And usage
details are added to device tree documentation. Driver is tested
by using kernel module with
On Friday 13 July 2012 08:45 AM, Vinod Koul wrote:
On Mon, 2012-07-02 at 10:02 -0600, Stephen Warren wrote:
On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
In cyclic mode of DMA, the byte transferred can be more
than the requested size and in this case, calculating
residuals based on the
On Thu, 2012-07-12 at 16:09 -0700, Andrew Morton wrote:
I really do dislike dropping patches and replacing them. For a whole
bunch of reasons. One of which is that a wholesale replacement
requires a full re-review. Another is that wholesale replacement makes
it hard to see what was changed.
On 07/12/2012 07:54 PM, R, Durgadoss wrote:
We are working on a notification API from any generic sensor driver to
the thermal framework.
Please have a look at the 'notify_thermal_framework' API in the patch here:
http://www.spinics.net/lists/linux-acpi/msg36049.html
At first sight these
Hi all,
Changes since 20120712:
The ext4 tree still has its build failure so I used the version from
next-20120709.
The tty tree gained a build failure, so I used the version from
next-20120712.
I have still reverted 3 commits from the signal tree at the request of the
arm maintainer.
The arm
On Thu, 2012-07-12 at 22:45 -0700, Andrew Morton wrote:
checkpatch does not report on context lines - only on added lines.
Hmm, I think I saw it ding this in the past. Anyway, I have no problems
cleaning at lease white-spaces in UFS globally separately.
--
Best Regards,
Artem Bityutskiy
--- On Fri, 13/7/12, Joe Perches j...@perches.com wrote:
From: Joe Perches j...@perches.com
Subject: [PATCH net-next 4/8] wireless: Use eth_random_addr
To: David Miller da...@davemloft.net, John W. Linville
linvi...@tuxdriver.com, Christian Lamparter chunk...@googlemail.com,
Ivo van Doorn
-Original Message-
From: Alex Courbot [mailto:acour...@nvidia.com]
Sent: Friday, July 13, 2012 11:19 AM
To: R, Durgadoss
Cc: Wei Ni; Zhang, Rui; Brown, Len; a...@linux-foundation.org; khali@linux-
fr.org; j...@perches.com; linux-kernel@vger.kernel.org; linux-
te...@ger.kernel.org
* John Stultz john.stu...@linaro.org wrote:
We do the exact same logic moving nsecs to secs in the
timekeeper in multiple places, so condense this into a
single function.
CC: Ingo Molnar mi...@kernel.org
CC: Peter Zijlstra a.p.zijls...@chello.nl
CC: Richard Cochran
* John Stultz john.stu...@linaro.org wrote:
From: John Stultz johns...@us.ibm.com
In commit 6b43ae8a619d17c4935c3320d2ef9e92bdeed05d, I
introduced a bug that kept the STA_INS or STA_DEL bit
from being cleared from time_status via adjtimex()
without forcing STA_PLL first.
Usually once
* Oleg Nesterov o...@redhat.com [2012-07-08 22:30:01]:
The bug was introduced by me in 449d0d7c uprobes: Simplify the
usage of uprobe-pending_list.
Yes, we do not care about uprobe-pending_list after return and
nobody can remove the current list entry, but put_uprobe(uprobe)
can actually
This patchset add support EXTCON Subsystem in which charger-manager identify
the type of external connector and enable/disable charger(regulator) according
to the state of charger cable(external connector).
First patch control charger(regulator) of charger-manager when external
connector is
Hi all,
Changes since 20120710:
New tree: spi-mb
The ext4 tree still has its build failure so I used the version from
next-20120709.
The pci tree lost its conflicts.
The v4l-dvb tree lost its build failure after I applied a supplied merge
fix patch.
The scsi tree gained a conflict against
This patch support that charger-manager use EXTCON(External Connector)
Subsystem to detect the state of charger cables for enabling or disabling
charger(regulator) and select the charger cable for charging among
a number of external cable according to policy of H/W board.
Signed-off-by: Chanwoo
This patch support the protection of host device from over current.
The Charger-manager set proper current limit of charger(regulator) for
charging according to type of charger cable when external connector
is attached.
Signed-off-by: Chanwoo Choi cw00.c...@samsung.com
Signed-off-by: Myungjoo Ham
On Thursday 12 July 2012 12:51 AM, Rafael J. Wysocki wrote:
[7/7] i2c-tegra: Use struct dev_pm_ops for power management
I did not get the 7/7 on my inbox and hence responding here.
Looked change from link
https://lkml.org/lkml/2012/7/11/467
This is same as which I sent some days ago:
using a wrapper around SET_ETHTOOL_OPS macro is not actually required,
remove and use SET_ETHTOOL_OPS directly.
Signed-off-by: Devendra Naga devendra.a...@gmail.com
---
drivers/staging/et131x/et131x.c |8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git
TCB has kcalloc' ed so no need to call memset again on it.
Signed-off-by: Devendra Naga devendra.a...@gmail.com
---
drivers/staging/et131x/et131x.c |2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/et131x/et131x.c b/drivers/staging/et131x/et131x.c
index 227fca9..5010894
return the error of filp_open rather returning -ENOENT.
Signed-off-by: Devendra Naga devendra.a...@gmail.com
---
drivers/staging/gdm72xx/usb_boot.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/gdm72xx/usb_boot.c
b/drivers/staging/gdm72xx/usb_boot.c
This patch add basic Renesas R-Car thermal sensor support.
It was tested on R-Car H1 Marzen board.
Signed-off-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
---
v1 - v2
- used spin_lock
- added explain of udelay(300)
- used a single space before =
drivers/thermal/Kconfig|
we are doing kmalloc and memset, can be done using kzalloc itself.
Signed-off-by: Devendra Naga devendra.a...@gmail.com
---
drivers/staging/gdm72xx/gdm_usb.c |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/gdm72xx/gdm_usb.c
the event sock check is done at the netlink_init itself.
Signed-off-by: Devendra Naga devendra.a...@gmail.com
---
drivers/staging/gdm72xx/gdm_wimax.c |8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/gdm72xx/gdm_wimax.c
On 07/12/2012 01:58 PM, HAYASAKA Mitsuo wrote:
Hi Yuan and Han-Wen,
Thank you for your comments.
(2012/07/06 22:58), Han-Wen Nienhuys wrote:
On Fri, Jul 6, 2012 at 2:53 AM, Liu Yuannamei.u...@gmail.com wrote:
On 07/05/2012 06:50 PM, Mitsuo Hayasaka wrote:
One of the ways to solve this
in sdio probe function we are doing kmalloc which can be done using kzalloc.
Signed-off-by: Devendra Naga devendra.a...@gmail.com
---
drivers/staging/gdm72xx/gdm_sdio.c |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/gdm72xx/gdm_sdio.c
following warnings were fixed
drivers/staging/gdm72xx/gdm_qos.c:198: ERROR: foo* bar should be foo *bar
drivers/staging/gdm72xx/gdm_qos.c:198: ERROR: foo* bar should be foo *bar
drivers/staging/gdm72xx/gdm_qos.c:244: WARNING: quoted string split across lines
Signed-off-by: Devendra Naga
On Wed, 11 Jul 2012 11:53:35 +0100, Catalin Marinas catalin.mari...@arm.com
wrote:
Hi Rusty,
Hi Catalin,
This is fun!
On Wed, Jul 11, 2012 at 06:26:49AM +0100, Rusty Russell wrote:
I know it's a crazy idea, but why don't we try some actual analysis?
This kind of analysis is not
On 07/12/12 13:57, Dave, Tushar N wrote:
-Original Message-
From: Joe Jin [mailto:joe@oracle.com]
Sent: Wednesday, July 11, 2012 8:13 PM
To: Dave, Tushar N
Cc: e1000-de...@lists.sf.net; net...@vger.kernel.org; linux-
ker...@vger.kernel.org
Subject: Re: 82571EB: Detected Hardware
On Wed, Jul 11, 2012 at 5:10 AM, Kevin Hilman khil...@ti.com wrote:
If platform_get_resource_by_name() fails, driver probe is aborted an
should return an error so the driver is not bound to the device.
However, in the current error path of platform_get_resource_by_name(),
probe returns zero
Hi Alex,
On Thu, 12 Jul 2012 07:56:46 +0200 Alexander Graf ag...@suse.de wrote:
On 12.07.2012, at 05:57, Stephen Rothwell wrote:
Today's linux-next merge of the kvm-ppc tree got a conflict in
arch/powerpc/kvm/booke_interrupts.S between commit c75df6f96c59
(powerpc: Fix usage of register
Ryan-san, Joe-san,
Thanks for your advice.
I will try re-create the patch again.
On Thu, Jul 12, 2012 at 2:43 PM, Joe Perches j...@perches.com wrote:
On Thu, 2012-07-12 at 15:22 +1000, Ryan Mallon wrote:
On 12/07/12 12:35, Toshiaki Yamane wrote:
This change is inspired by checkpatch.
Your
This is a rebase onto current linux-next due to a minor collision with
some NFS changes.
Changelog since V14
o Rebase to linux-next 20120710
Changelog since V13
o Rebase to linux-next 20120629
Changelog since V12
o Rebase to linux-next-20120622
o Do not alter coalesce handling in the
__GFP_MEMALLOC will allow the allocation to disregard the watermarks,
much like PF_MEMALLOC. It allows one to pass along the memalloc state
in object related allocation flags as opposed to task related flags,
such as sk-sk_allocation. This removes the need for ALLOC_PFMEMALLOC
as callers using
__alloc_pages_slowpath() is called when the number of free pages is below
the low watermark. If the caller is entitled to use ALLOC_NO_WATERMARKS
then the page will be marked page-pfmemalloc. This protects more pages
than are strictly necessary as we only need to protect pages allocated
below the
Under significant pressure when writing back to network-backed storage,
direct reclaimers may get throttled. This is expected to be a
short-lived event and the processes get woken up again but processes do
get stalled. This patch counts how many times such stalling occurs. It's
up to the
Replace all relevant occurences of page-index and page-mapping in
the NFS client with the new page_file_index() and page_file_mapping()
functions.
Signed-off-by: Peter Zijlstra a.p.zijls...@chello.nl
Signed-off-by: Mel Gorman mgor...@suse.de
Acked-by: Rik van Riel r...@redhat.com
---
On 07/12/12 13:57, Dave, Tushar N wrote:
-Original Message-
From: Joe Jin [mailto:joe@oracle.com]
Sent: Wednesday, July 11, 2012 8:13 PM
To: Dave, Tushar N
Cc: e1000-de...@lists.sf.net; net...@vger.kernel.org; linux-
ker...@vger.kernel.org
Subject: Re: 82571EB: Detected Hardware
The VM does not like PG_private set on PG_swapcache pages. As suggested
by Trond in http://lkml.org/lkml/2006/8/25/348, this patch disables
NFS data cache revalidation on swap files. as it does not make
sense to have other clients change the file while it is being used as
swap. This avoids
Commit [b3a27d: swap: Add swap slot free callback to
block_device_operations] dereferences p-bdev-bd_disk but this is a
NULL dereference if using swap-over-NFS. This patch checks SWP_BLKDEV
on the swap_info_struct before dereferencing.
With reference to this callback, Christoph Hellwig stated
The skb-pfmemalloc flag gets set to true iff during the slab
allocation of data in __alloc_skb that the the PFMEMALLOC reserves
were used. If page splitting is used, it is possible that pages will
be allocated from the PFMEMALLOC reserve without propagating this
information to the skb. This patch
In order to make sure pfmemalloc packets receive all memory
needed to proceed, ensure processing of pfmemalloc SKBs happens
under PF_MEMALLOC. This is limited to a subset of protocols that
are expected to be used for writing to swap. Taps are not allowed to
use PF_MEMALLOC as these are expected to
Changelog since V8
o Rebase to linux-next 20120710
Changelog since V7
o Rebase to linux-next 20120629
o bi-page_dma instead of bi-page in intel driver
o Build fix for !CONFIG_NET (sebastian)
o Restore PF_MEMALLOC flags correctly in all cases
In order to teach filesystems to handle swap cache pages, three new
page functions are introduced:
pgoff_t page_file_index(struct page *);
loff_t page_file_offset(struct page *);
struct address_space *page_file_mapping(struct page *);
page_file_index() - gives the offset of this page in
GFP_NOFS is _more_ permissive than GFP_NOIO in that it will initiate
IO, just not of any filesystem data.
The problem is that previously NOFS was correct because that avoids
recursion into the NFS code. With swap-over-NFS, it is no longer
correct as swap IO can lead to this recursion.
Implement the new swapfile a_ops for NFS and hook up -direct_IO. This
will set the NFS socket to SOCK_MEMALLOC and run socket reconnect
under PF_MEMALLOC as well as reset SOCK_MEMALLOC before engaging the
protocol -connect() method.
PF_MEMALLOC should allow the allocation of struct socket and
The patch mm: Add support for a filesystem to activate swap files and
use direct_IO for writing swap pages added support for using direct_IO
to write swap pages but it is insufficient for highmem pages.
To support highmem pages, this patch kmaps() the page before calling the
direct_IO() handler.
This patch adds two new APIs get_kernel_pages() and get_kernel_page()
that may be used to pin a vector of kernel addresses for IO. The initial
user is expected to be NFS for allowing pages to be written to swap
using aops-direct_IO(). Strictly speaking, swap-over-NFS only needs
to pin one page for
The version of swap_activate introduced is sufficient for swap-over-NFS
but would not provide enough information to implement a generic handler.
This patch shuffles things slightly to ensure the same information is
available for aops-swap_activate() as is available to the core.
No functionality
Failing to allocate a cache entry will only harm performance not
correctness. Do not consume valuable reserve pages for something
like that.
Signed-off-by: Peter Zijlstra a.p.zijls...@chello.nl
Signed-off-by: Mel Gorman mgor...@suse.de
Acked-by: Eric Paris epa...@redhat.com
Acked-by: Rik van
It could happen that all !SOCK_MEMALLOC sockets have buffered so
much data that we're over the global rmem limit. This will prevent
SOCK_MEMALLOC buffers from receiving data, which will prevent userspace
from running, which is needed to reduce the buffered data.
Fix this by exempting the
Currently swapfiles are managed entirely by the core VM by using -bmap
to allocate space and write to the blocks directly. This effectively
ensures that the underlying blocks are allocated and avoids the need
for the swap subsystem to locate what physical blocks store offsets
within a file.
If
If swap is backed by network storage such as NBD, there is a risk
that a large number of reclaimers can hang the system by consuming
all PF_MEMALLOC reserves. To avoid these hangs, the administrator
must tune min_free_kbytes in advance which is a bit fragile.
This patch throttles direct
Set SOCK_MEMALLOC on the NBD socket to allow access to PFMEMALLOC
reserves so pages backed by NBD, particularly if swap related, can
be cleaned to prevent the machine being deadlocked. It is still
possible that the PFMEMALLOC reserves get depleted resulting in
deadlock but this can be resolved by
The reserve is proportionally distributed over all !highmem zones
in the system. So we need to allow an emergency allocation access to
all zones. In order to do that we need to break out of any mempolicy
boundaries we might have.
In my opinion that does not break mempolicies as those are user
Getting and putting objects in SLAB currently requires a function call
but the bulk of the work is related to PFMEMALLOC reserves which are
only consumed when network-backed storage is critical. Use an inline
function to determine if the function call is required.
Signed-off-by: Mel Gorman
For type 1 the parent_offset member in struct isofs_fid gets copied
uninitialized to userland. Fix this by initializing it to 0.
Signed-off-by: Mathias Krause mini...@googlemail.com
---
fs/isofs/export.c |1 +
1 file changed, 1 insertion(+)
diff --git a/fs/isofs/export.c b/fs/isofs/export.c
Al, Jan,
this patch set fixes info leaks in isofs and udf. Both file systems fail to
initialize all bytes of the f_handle byte array when creating a handle for a
path pointing to a directory. This memory gets copied to userland and that for
is a leak of uninitialized heap data to userland that
For type 0x51 the udf.parent_partref member in struct fid gets copied
uninitialized to userland. Fix this by initializing it to 0.
Signed-off-by: Mathias Krause mini...@googlemail.com
---
fs/udf/namei.c |1 +
1 file changed, 1 insertion(+)
diff --git a/fs/udf/namei.c b/fs/udf/namei.c
index
The skb-pfmemalloc flag gets set to true iff during the slab
allocation of data in __alloc_skb that the the PFMEMALLOC reserves
were used. If the packet is fragmented, it is possible that pages
will be allocated from the PFMEMALLOC reserve without propagating
this information to the skb. This
Introduce sk_gfp_atomic(), this function allows to inject sock specific
flags to each sock related allocation. It is only used on allocation
paths that may be required for writing pages back to network storage.
[da...@davemloft.net: Use sk_gfp_atomic only when necessary]
Signed-off-by: Peter
Change the skb allocation API to indicate RX usage and use this to fall
back to the PFMEMALLOC reserve when needed. SKBs allocated from the
reserve are tagged in skb-pfmemalloc. If an SKB is allocated from
the reserve and the socket is later found to be unrelated to page
reclaim, the packet is
This is needed to allow network softirq packet processing to make
use of PF_MEMALLOC.
Currently softirq context cannot use PF_MEMALLOC due to it not being
associated with a task, and therefore not having task flags to fiddle
with - thus the gfp to alloc flag mapping ignores the task flags when
in
Allow specific sockets to be tagged SOCK_MEMALLOC and use
__GFP_MEMALLOC for their allocations. These sockets will be able to go
below watermarks and allocate from the emergency reserve. Such sockets
are to be used to service the VM (iow. to swap over). They must be
handled kernel side, exposing
From: Christoph Lameter c...@linux.com
This patch removes the check for pfmemalloc from the alloc hotpath and
puts the logic after the election of a new per cpu slab. For a pfmemalloc
page we do not use the fast path but force the use of the slow path which
is also used for the debug case.
This
Allocations of pages below the min watermark run a risk of the
machine hanging due to a lack of memory. To prevent this, only
callers who have PF_MEMALLOC or TIF_MEMDIE set and are not processing
an interrupt are allowed to allocate with ALLOC_NO_WATERMARKS. Once
they are allocated to a slab
Delete redudant spaces between type name and data name or
operators.
Signed-off-by: Ying Xue ying.x...@gmail.com
---
kernel/sched/cpupri.c | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/cpupri.c b/kernel/sched/cpupri.c
index d72586f..23aa789 100644
On Wed 11-07-12 18:57:43, Hugh Dickins wrote:
Hi Michal,
Hi,
On Wed, 20 Jun 2012, Michal Hocko wrote:
Hi Andrew,
here is an updated version if it is easier for you to drop the previous
one.
changes since v1
* added Mel's Reviewed-by
* updated changelog as per Andrew
* updated
Commit 9778b696 (powerpc: Use CURRENT_THREAD_INFO instead of open
coded assembly) got a rejected merge file iommu.c.rej committed with
it.
Signed-off-by: Gerard Snitselaar d...@snitselaar.org
---
arch/powerpc/kernel/iommu.c.rej | 22 --
1 file changed, 22 deletions(-)
delete
On Tue, 10 Jul 2012, Christoph Lameter wrote:
Here is the patch:
Subject: slob: Undo slob hunk
Commit fd3142a59af2012a7c5dc72ec97a4935ff1c5fc6 broke
slob since a piece of a change for a later patch slipped into
it.
Signed-off-by: Christoph Lameter c...@linux.com
---
mm/slob.c |
As Rob's clock binding support patch is now up on clk-next, I'd like to
draw attention on this patch again.
--
This patch adds support for using clock gates (clk-gate) from DT based
on Rob Herrings DT clk binding support for 3.6.
It adds a helper function to clk-gate to allocate all resources
Hello,
I'm doing experiments with the Userspace IO driver (UIO_PCI_GENERIC) and
a set of PCIe cards. The kernel version is 3.4.4, CPU is a Marvell
MV78200 (ARMv5te). Example with an Intel ethernet card:
This makes /dev/uio0 appear
echo -n 8086 10d3 /sys/bus/pci/drivers/uio_pci_generic/new_id
Bump. There has been no discussion on this patch nor on patch 2/2. Is there
anybody out there willing to test and confirm these patches?
--
The sdio controller on dove doesn't have a bit to indicate
high-speed. With the quirk set it fixes accessing high-speed
sdcards.
Signed-off-by: Sebastian
Hi Masatake,
On Wed, Jul 11, 2012 at 09:19:06PM +0900, Masatake YAMATO wrote:
I've tested the patch and it creates entries in /proc/net
Thanks.
BTW: Shall lsof be able to identify l2cap protocol?
for l2test it prints: can't identify protocol
No. I'll work on lsof side after the
On 07/11/2012 06:47 PM, John Stultz wrote:
I'll see if my worry is unfounded, but it might be a bit too clever for rare
events.
Full ACK.
There is an unfortunate history of critical-to-moderately-serious bugs in
the leap second handling, so I submit that what is needed is a simple,
there are some out of bound accesses in netprio cgroup.
now before accessing the dev-priomap.priomap array,we only check
if the dev-priomap exist.and because we don't want to see
additional bound checkings in fast path, so we should make sure
that dev-priomap is null or array size of
From: Michael Wang wang...@linux.vnet.ibm.com
with this patch, ld_env will have a pointer of load balance cpumask,
and we don't need to pass cpus anymore.
Signed-off-by: Michael Wang wang...@linux.vnet.ibm.com
---
kernel/sched/fair.c | 34 --
1 files changed,
On 07/12/2012 08:11 AM, Raghavendra K T wrote:
Ah, I thouht you objected to the CONFIG var. Maybe call it
cpu_relax_intercepted since that's the linuxy name for the instruction.
Ok, just to be on same page. 'll have :
1. cpu_relax_intercepted instead of pause_loop_exited.
2.
On 07/12/2012 05:17 AM, Benjamin Herrenschmidt wrote:
ARM doesn't have an instruction for cpu_relax(), so it can't intercept
it. Given ppc's dislike of overcommit, and the way it implements
cpu_relax() by adjusting hw thread priority, I'm guessing it doesn't
intercept those either, but I'm
901 - 1000 of 1654 matches
Mail list logo
