Re: [GIT PULL] Detaching mounts on unlink for 3.15

On Sat, Apr 19, 2014 at 03:16:46AM +0100, Al Viro wrote: > On Sat, Apr 19, 2014 at 02:35:26AM +0100, Al Viro wrote: > > > My apologies for confusion - I have not looked at your last commit. > > I *really* don't like that solution, but it probably does close that > > particular problem. Consider t

Re: [PATCH] ipc/shm: Increase the defaults for SHMALL, SHMMAX to infinity

On Sat, Apr 19, 2014 at 8:55 AM, Davidlohr Bueso wrote: > On Fri, 2014-04-18 at 11:18 +0200, Manfred Spraul wrote: >> System V shared memory >> >> a) can be abused to trigger out-of-memory conditions and the standard >>measures against out-of-memory do not work: >> >> - it is not possible

Re: [PATCHv3 1/8] extcon: Add resource-managed extcon register function

Hi Sangjung, On Fri, Apr 18, 2014 at 9:32 AM, Sangjung Woo wrote: > Add resource-managed extcon device register function for convenience. > For example, if a extcon device is attached with new > devm_extcon_dev_register(), that extcon device is automatically > unregistered on driver detach. > > S

[git pull] drm fixes

Hi Linus, Unfortunately this contains no easter eggs, its a bit larger than I'd like, but I included a patch that just moves code from one file to another and I'd like to avoid merge conflicts with that later, so it makes it seem worse than it is, Otherwise, radeon fixes to use new microcode

[PATCH] tracing:Do not profile dumpstack utilities to fix stack trace output

When function_graph tracer is enabled, we get stack trace like this: DepthSize Location(88 entries) - 0) 3232 0 update_curr+0xe/0x1e0 1) 3232 0 dump_trace+0xb5/0x1b0 2) 3232 0 ftrace_ops_list_func+0xe6/

Re: [PATCH] Staging: crystalhd: Mark local functions as static

On Sat, Apr 19, 2014 at 1:23 AM, Greg KH wrote: > On Fri, Apr 18, 2014 at 07:57:51PM +0200, Bojan Prtvar wrote: >> This fixes the following sparse warnings: >> drivers/staging/crystalhd/crystalhd_lnx.c:631:5: warning: symbol >> 'chd_dec_pci_suspend' was not declared. Should it be static? >> drive

Re: [sched,rcu] b84c4e08143: +3.1% will-it-scale.per_thread_ops

On Thu, Apr 17, 2014 at 06:55:03AM -0700, Paul E. McKenney wrote: > On Thu, Apr 17, 2014 at 12:03:53PM +0800, Fengguang Wu wrote: > > Hi Paul, > > > > FYI, this improves will-it-scale/open1 throughput. > > Cool! Not a planned benefit, but I will take it. ;-) > > > git://git.kernel.org/pub/scm/

[rcu] 10a94227ba2: -2.0% will-it-scale.per_process_ops

Paul, FYI, we noticed the below changes on git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git next.2014.04.16b commit 10a94227ba229f1b05672754dc318a8fe7982c95 ("rcu: Update cpu_needs_another_gp() for futures from non-NOCB CPUs") test case: nhm4/micro/will-it-scale/lseek1 11ba

Re: [PATCH] Staging: crystalhd: Mark local functions as static

On Sat, Apr 19, 2014 at 9:58 AM, bojan prtvar wrote: > On Sat, Apr 19, 2014 at 1:23 AM, Greg KH wrote: >> On Fri, Apr 18, 2014 at 07:57:51PM +0200, Bojan Prtvar wrote: >>> This fixes the following sparse warnings: >>> drivers/staging/crystalhd/crystalhd_lnx.c:631:5: warning: symbol >>> 'chd_dec_

Re: [PATCH 0/2] memcg: mm_update_next_owner() should skip kthreads

Hi! > > Hmm. I seem to see a bug in this function, it can be fulled by use_mm, > > but I am not sure this can explain the problem. I'll send a patch. > > Untested, please review. But it really looks "obviously wrong", and note > that unuse_mm() doesn't do mm_update_next_owner(). (just in case, do

Re: [PATCH] ipc/shm: Increase the defaults for SHMALL, SHMMAX to infinity

On 04/19/2014 08:55 AM, Davidlohr Bueso wrote: On Fri, 2014-04-18 at 11:18 +0200, Manfred Spraul wrote: - ULONG_MAX is not really infinity, but 18 Exabyte segment size and 75 Zettabyte total size. This should be enough for the next few weeks. (assuming a 64-bit system with 4k pages) Note:

Re: [PATCH] ipc/shm: Increase the defaults for SHMALL, SHMMAX to infinity

On 04/19/2014 09:10 AM, Michael Kerrisk (man-pages) wrote: On Sat, Apr 19, 2014 at 8:55 AM, Davidlohr Bueso wrote: On Fri, 2014-04-18 at 11:18 +0200, Manfred Spraul wrote: Risks: - The patch breaks installations that use "take current value and increase it a bit". [seems to exist, http://ma

[PATCH 1/1] fs/bio.c: remove nr_segs (unused function parameter)

nr_segs is no longer used in bio_alloc_map_data since c8db444820a1e3 ("block: Don't save/copy bvec array anymore") Cc: Alexander Viro Cc: Andrew Morton Signed-off-by: Fabian Frederick --- fs/bio.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/fs/bio.c b/fs/bio.c ind

Re: [PATCH 11/11] ext4: add cross rename support

Hi Miklos, > The code changes are pushed to the git tree and the updated man page is below. Now that renameat2() is in 3.15, I've taken these changes. This had to be manually does, because I'd done some major reworking on the pages since you originally wrote your text. So, I may have injected s

[PATCH 1/1] FS: Remove bs parameter in biovec_create_pool

bs is no longer used in biovec_create_pool since 9f060e2231ca96 ("block: Convert integrity to bvec_alloc_bs()") Cc: Alexander Viro Cc: Andrew Morton Signed-off-by: Fabian Frederick --- fs/bio-integrity.c | 2 +- fs/bio.c| 4 ++-- include/linux/bio.h | 2 +- 3 files changed, 4 inse

Re: [PATCH] ipc/shm: Increase the defaults for SHMALL, SHMMAX to infinity

On 04/19/2014 10:45 AM, Manfred Spraul wrote: > On 04/19/2014 09:10 AM, Michael Kerrisk (man-pages) wrote: >> On Sat, Apr 19, 2014 at 8:55 AM, Davidlohr Bueso wrote: >>> On Fri, 2014-04-18 at 11:18 +0200, Manfred Spraul wrote: Risks: - The patch breaks installations that use "take curren

Re: [PATCH] ipc/shm: Increase the defaults for SHMALL, SHMMAX to infinity

On 04/19/2014 10:37 AM, Manfred Spraul wrote: > On 04/19/2014 08:55 AM, Davidlohr Bueso wrote: >> On Fri, 2014-04-18 at 11:18 +0200, Manfred Spraul wrote: >>> - ULONG_MAX is not really infinity, but 18 Exabyte segment size and >>>75 Zettabyte total size. This should be enough for the next few w

Re: [PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS

* Waiman Long wrote: > On 04/18/2014 03:46 AM, Ingo Molnar wrote: > >* Waiman Long wrote: > > > >>On 04/17/2014 11:58 AM, Peter Zijlstra wrote: > >>>On Thu, Apr 17, 2014 at 11:03:57AM -0400, Waiman Long wrote: > +static __always_inline void > +clear_pending_set_locked(struct qspinlock *

Re: [PATCHv3 1/8] extcon: Add resource-managed extcon register function

Hi Chanwoo. Thanks for your comments. I also add my opinion too. On 04/19/2014 04:13 PM, Chanwoo Choi wrote: Hi Sangjung, On Fri, Apr 18, 2014 at 9:32 AM, Sangjung Woo wrote: Add resource-managed extcon device register function for convenience. For example, if a extcon device is attached wi

[PATCH v1 next 3/4] blk-mq: user (1 << order) to implement order_to_size()

Cc: Jörg-Volker Peetz Cc: Max Filippov Signed-off-by: Ming Lei --- block/blk-mq.c |7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/block/blk-mq.c b/block/blk-mq.c index c277797..3a560a4 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c @@ -1130,12 +1130,7 @@ static vo

[PATCH v1 next 4/4] blk-mq: initialize req->q in allocation

The patch basically reverts the patch of(blk-mq: initialize request on allocation) in Jens's tree(already in -next), and only initialize req->q in allocation for two reasons: - presumed cache hotness on completion - blk_rq_tagged(rq) depends on reset of req->mq_ctx Signed-off-by:

[PATCH v1 next 1/4] blk-mq: free hctx->ctx_map when init failed

Avoid memory leak in the failure path. Reviewed-by: Christoph Hellwig Signed-off-by: Ming Lei --- block/blk-mq.c |1 + 1 file changed, 1 insertion(+) diff --git a/block/blk-mq.c b/block/blk-mq.c index ee225cc..5fbbb22 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c @@ -1289,6 +1289,7 @@ s

[PATCH v1 next 2/4] blk-mq: fix allocation of set->tags

type of set->tags is struct blk_mq_tags **. Reviewed-by: Christoph Hellwig Signed-off-by: Ming Lei --- block/blk-mq.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/block/blk-mq.c b/block/blk-mq.c index 5fbbb22..c277797 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c

[PATCH v1 next 0/4] blk-mq: misc changes

Hi, Three of them are fixes, another one is cleanup. V1: - line break(2/4) - use explicit cast(3/4) Thanks, -- Ming Lei -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http:/

[GIT PULL] EFI changes for v3.16

Hi folks, Please pull the following changes for v3.16. I'd like to get these in early so that they've got plenty of time to bake in linux-next. In particular, the ARM folks have had a hard time getting the generic EFI cleanups/improvements picked up via other trees. Obviously by taking these thro

Re: [PATCH] cdrom.c: Only read a cdrom_msf0 struct from userspace.

Reimar Döffinger gmx.de> writes: > ping > Having one piece of documentation that is clearly utter nonsense and then a > second piece of documentation that adds a note that the first documentation > is wrong sure isn't the way to keep things. ping2 -- To unsubscribe from this list: send the line

Re: [PATCH 6/8] idr: avoid ping-pong

On 04/19/2014 01:17 AM, Tejun Heo wrote: > On Fri, Apr 18, 2014 at 08:49:53PM +0800, Lai Jiangshan wrote: >> The ida callers always calls ida_pre_get() before ida_get_new*(). >> ida_pre_get() will do layer allocation, and ida_get_new*() will do layer >> removal. >> >> It causes an unneeded ping-po

[GIT PULL] perf fixes

Linus, Please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus # HEAD: 24223657806a0ebd0ae5c9caaf7b021091889cf2 perf/x86/intel: Use rdmsrl_safe() when initializing RAPL PMU Two kernel side fixes: - an

[GIT PULL] scheduler fixes

Linus, Please pull the latest sched-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-urgent-for-linus # HEAD: a1d9a3231eac4117cadaf4b6bba5b2902c15a33e sched: Check for stop task appearance when balancing happens Two fixes: - a SCHED_DEADL

[GIT PULL] x86 fix

Linus, Please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus # HEAD: ea431643d6c38728195e2c456801c3ef66bb9991 x86/mce: Fix CMCI preemption bugs This fixes the preemption-count imbalance crash reported by

Re: [PATCH v2 05/13] extcon: extcon-class: improve extcon client API

Hi, On Mon, Apr 14, 2014 at 01:46:16PM +0200, Robert Baldyga wrote: > dev_info(&pdev->dev, > - "OMAP USB OTG controller rev %d.%d (%s, id=%d, vbus=%d)\n", > - (rev >> 4) & 0xf, rev & 0xf, config->extcon, otg_dev->id, > + "OMAP USB OTG controller rev %d.

Estimado E-mail del usuario;

Estimado E-mail del usuario; Se ha superado 23.432 Repositorio para el conjunto buzón Servicios Web / Administrador, y habrás problemas al enviar y recepción de correo, mientras que volver a verificar. Debe actualizar haciendo clic en enlace de abajo y complete la información para verificar su cu

Re: [PATCH v2 1/5] x86/PCI: Add support for generic AMD hostbridges

On Fri, Apr 18, 2014 at 08:53:16PM -0600, Myron Stowe wrote: > From: Suravee Suthikulpanit > > AMD hostbridges gnenerally show up as PCI device 0:18.0. This patch adds > logic to automatically probe the device at this location and check PCI > device class code. > > This patch supports platforms

Re: [PATCH 4/8] tty/serial: add generic serial earlycon

On Thursday 17 April 2014, Rob Herring wrote: > On Mon, Mar 24, 2014 at 10:42 AM, Arnd Bergmann wrote: > > On Monday 24 March 2014 08:36:46 Rob Herring wrote: > >> On Mon, Mar 24, 2014 at 6:29 AM, Arnd Bergmann wrote: > >> > On Monday 24 March 2014 11:22:03 Catalin Marinas wrote: > >> >> On Fri,

[PATCH 0/9 V2] idr: fix & cleanup

Patch1 fix a bug caused by overflow. Patch2,3 add checks for unallocated_id. Patch4 changes to returned error code Patch5-9 cleanup. Lai Jiangshan (9): idr: fix overflow bug during maximum ID calculation at maximum height idr: fix unexpected ID-removal when idr_remove(unallocated_id) **^^also

[PATCH 2/9 V2] idr: fix unexpected ID-removal when idr_remove(unallocated_id)

If unallocated_id = (ANY * idr_max(idp->layers) + existing_id) is passed to idr_remove(). The existing_id will be removed unexpectedly. The following test shows this unexpected id-removal: static void test4(void) { int id; DEFINE_IDR(test_idr); printk(KERN_INFO "Start tes

[PATCH 9/9 V2] idr: remove useless C-PreProcessor branch

"#ifndef TEST" can't work for user space test now, just remove it. Signed-off-by: Lai Jiangshan --- lib/idr.c |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/lib/idr.c b/lib/idr.c index e3c1da0..d77cdca 100644 --- a/lib/idr.c +++ b/lib/idr.c @@ -20,11 +20,9 @@ * that

[PATCH 7/9 V2] idr: don't need to shink the free list when idr_remove()

After idr subsystem is changed to RCU-awared, the free layer will not go to the free list. The free list will not be filled up when idr_remove(). So we don't need to shink it too. Signed-off-by: Lai Jiangshan Acked-by: Tejun Heo --- lib/idr.c | 16 1 files changed, 0 insertio

[PATCH 8/9 V2] idr: reduce the unneeded check in free_layer()

If "idr->hint == p" is true, it also implies "idr->hint" is true(not NULL). Signed-off-by: Lai Jiangshan Acked-by: Tejun Heo --- lib/idr.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/idr.c b/lib/idr.c index 4a11c5d..e3c1da0 100644 --- a/lib/idr.c +++ b/lib/idr.

[PATCH 5/9 V2] idr: covert BUG_ON() to WARN_ON_ONCE() if the argument is invalid.

When the arguments passed by the caller are invalid, WARN_ON_ONCE() is proper than BUG_ON() which may crash the kernel. The invalid-checking for ida_simple_remove() is moved into ida_remove(). idr_remove() also adds this WARN_ON_ONCE(). And when "end < start" in ida_simple_get(), it returns -ENOS

Estimado E-mail del usuario;

Estimado E-mail del usuario; Se ha superado 23.432 Repositorio para el conjunto buzón Servicios Web / Administrador, y habrás problemas al enviar y recepción de correo, mientras que volver a verificar. Debe actualizar haciendo clic en enlace de abajo y complete la información para verificar su cu

[PATCH 6/9 V2] idr: avoid ping-pong

The ida callers always calls ida_pre_get() before ida_get_new*(). ida_pre_get() will always do layer allocation, which means the layer removal in ida_get_new*() is helpless. ida_get_new*() frees and the ida_pre_get() for the next ida_get_new*() allocates. It causes an unneeded ping-pong. The aim "

[PATCH 4/9 V2] idr: fix idr_replace()'s returned error code

When the smaller id is not found, idr_replace() returns -ENOENT. But when the id is bigger enough, idr_replace() returns -EINVAL, actually there is no difference between these two kinds of ids. These are all unallocated id, the return values of the idr_replace() for these ids should be the same: -

[PATCH 1/9 V2] idr: fix overflow bug during maximum ID calculation at maximum height

idr_replace() open-codes the logic to calculate the maximum valid ID given the height of the idr tree; unfortunately, the open-coded logic doesn't account for the fact that the top layer may have unused slots and over-shifts the limit to zero when the tree is at its maximum height. The following t

[PATCH 3/9 V2] idr: fix NULL pointer dereference when ida_remove(unallocated_id)

If the ida has at least one existing id, and when an unallocated ID which meets a certain condition is passed to the ida_remove(), the system will crash because it hits NULL pointer dereference. The condition is that the unallocated ID shares the same lowest idr layer with the existing ID, but the

[PATCH v3 0/2] DaVinci: VPIF: upgrade with v4l helpers

From: "Lad, Prabhakar" Hi All, This patch series upgrades the vpif capture & display driver with the all the helpers provided by v4l, this makes the driver much simpler and cleaner. This also includes few checkpatch issues. Sending them as single patch one for capture and another for display, s

[PATCH 4/4] ipc/shm.c: Increase the defaults for SHMALL, SHMMAX.

System V shared memory a) can be abused to trigger out-of-memory conditions and the standard measures against out-of-memory do not work: - it is not possible to use setrlimit to limit the size of shm segments. - segments can exist without association with any processes, thus the

[PATCH 0/4] ipc/shm.c: increase the limits for SHMMAX, SHMALL

Hi all, the increase of SHMMAX/SHMALL is now a 4 patch series, and still not ready for merging (see at the end, TASK_SIZE and s390). If we increase the default limits for SHMMAX and SHMALL, integer overflows could happen: SHMMAX: - shmmem_file_setup places a hard limit on the segment size:

[PATCH 2/4] ipc/shm.c: check for overflows of shm_tot

shm_tot counts the total number of pages used by shm segments. If SHMALL is ULONG_MAX (or nearly ULONG_MAX), then the number can overflow. Subsequent calls to shmctl(,SHM_INFO,) would return wrong values for shm_tot. The patch adds a detection for overflows. Signed-off-by: Manfred Spraul ---

[PATCH 3/4] ipc/shm.c: check for integer overflow during shmget.

SHMMAX is the upper limit of a shared memory segment, counted in bytes. The actual allocation is that size, rounded up to the next full page. Add a check that prevents the creation of segments where the rounded up size causes an integer overflow. Signed-off-by: Manfred Spraul --- ipc/shm.c | 3 +

[PATCH 1/4] ipc/shm.c: check for ulong overflows in shmat

find_vma_intersection does not work properly if addr+size overflows. The patch adds a manual check before the call to find_vma_intersection. Signed-off-by: Manfred Spraul --- ipc/shm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ipc/shm.c b/ipc/shm.c index 7645961..382e2fb 100644 ---

Re: [PATCH v4 00/21] ARM: support for ICP DAS LP-8x4x (with dts)

On Thursday 17 April 2014, Daniel Mack wrote: > On 04/17/2014 02:12 PM, Sergei Ianovich wrote: > > On Thu, 2014-04-17 at 12:38 +0200, Daniel Mack wrote > > I have all the > > reasons to believe, that LP-8x4x support would already have be merged, > > if I didn't try to use DT. > > That might be, bu

Re: [PATCH 11/11] ext4: add cross rename support

Michael Kerrisk (man-pages) wrote: > Now that renameat2() is in 3.15, I've taken these changes. What!? I didn't know renameat2() goes to 3.15. But I assume that renameat2() is not accessible in 3.15, for I can see "asmlinkage long sys_renameat2(" but don't see "#define __NR_renameat2". $ grep

Re: [PATCH v2 0/4] introduce devm_mdiobus_alloc/free and clean up davinci mdio

Hi Grygorii, Thanks for the patches! On Fri, Apr 18, 2014 at 10:54 PM, Grygorii Strashko wrote: > Introduce a resource managed devm_mdiobus_alloc()/devm_mdiobus_free() > to automatically clean up MDIO bus alocations made by MDIO drivers, > thus leading to simplified MDIO drivers code. > > Clean

Re: [PATCH] cgroup:cgroup_mount: Fix uninitialized warning

On Sat, Apr 19, 2014 at 09:52:14PM +0900, Takeshi Misawa wrote: > This patch fixes the following warning. > > kernel/cgroup.c: In function ‘cgroup_mount’: > kernel/cgroup.c:1609:13: warning: ‘root’ may be used uninitialized in this > function Which compiler are you using? This is a spurious warn

Re: [PATCH 6/8] idr: avoid ping-pong

Hello, On Sat, Apr 19, 2014 at 06:43:41PM +0800, Lai Jiangshan wrote: > On 04/19/2014 01:17 AM, Tejun Heo wrote: > It only frees one layer. And the ida_pre_get() for the next ida_get_new*() > will allocation it back again. The aim "Throw away extra resources one by one" > can't be achieved. It can

Re: [PATCH 5/9 V2] idr: covert BUG_ON() to WARN_ON_ONCE() if the argument is invalid.

On Sat, Apr 19, 2014 at 07:38:12PM +0800, Lai Jiangshan wrote: > @@ -559,7 +559,7 @@ void idr_remove(struct idr *idp, int id) > struct idr_layer *p; > struct idr_layer *to_free; > > - if (id < 0) > + if (WARN_ON_ONCE(id < 0)) > return; ISTR callers which call in

Re: [PATCHv3 1/8] extcon: Add resource-managed extcon register function

Hi, On Sat, Apr 19, 2014 at 6:50 PM, Sangjung wrote: > Hi Chanwoo. > > Thanks for your comments. I also add my opinion too. > > > > On 04/19/2014 04:13 PM, Chanwoo Choi wrote: >> >> Hi Sangjung, >> >> On Fri, Apr 18, 2014 at 9:32 AM, Sangjung Woo >> wrote: >>> >>> Add resource-managed extcon dev

Re: in kernel 2.6.x, tun/tap nic supports vlan packets

On 04/17/2014 01:02 PM, Willy Tarreau wrote: Hi Zhu, On Thu, Apr 17, 2014 at 11:35:58AM +0800, zhuyj wrote: Hi, all In kernel 2.6.x, linux depends on nic vlan hardware acceleration to insert/extract vlan tag. In this scene, in kernel 2.6.x _ A

Re: [PATCH 0/2] Support cpufreq driver for Exynos3250

Hi Sachin, On Fri, Apr 18, 2014 at 5:14 PM, Sachin Kamat wrote: > Hi Chanwoo, > > On 18 April 2014 07:50, Chanwoo Choi wrote: >> This patchset support cpufreq driver for Exynos3250 which uses the Cortex-A7 >> dual cores and has a target speed of 1.0 GHz and code clean using >> dev_err/info >> i

Re: [PATCH 0/2] Support cpufreq driver for Exynos3250

Hi Chanwoo, Sachin, On 19.04.2014 15:43, Chanwoo Choi wrote: Hi Sachin, On Fri, Apr 18, 2014 at 5:14 PM, Sachin Kamat wrote: Hi Chanwoo, On 18 April 2014 07:50, Chanwoo Choi wrote: This patchset support cpufreq driver for Exynos3250 which uses the Cortex-A7 dual cores and has a target spee

Re: [PATCH v2 2/5] x86/PCI: Support additional MMIO range capabilities

On Fri, Apr 18, 2014 at 08:53:23PM -0600, Myron Stowe wrote: > From: Suravee Suthikulpanit > > This patch adds supports for additional MMIO ranges (16 ranges). Also, > each MMIO base/limit can now support up to 48-bit MMIO addresses. > However, this requires initializing the ECS sooner since the

[PATCH] tracing: Correct braces usage in if-else statement

There are some incorrect braces usages in kernerl/trace/trace.c, including: 1. Missing braces in 'if' or 'else' branch. 2. Unnecessary braces in 'if' statement. Fix them according to kernel CodeStyle. Signed-off-by: Lin Yongting --- kernel/trace/trace.c | 39 +++---

Re: [PATCH 5/9 V2] idr: covert BUG_ON() to WARN_ON_ONCE() if the argument is invalid.

On Sat, Apr 19, 2014 at 9:07 PM, Tejun Heo wrote: > On Sat, Apr 19, 2014 at 07:38:12PM +0800, Lai Jiangshan wrote: >> @@ -559,7 +559,7 @@ void idr_remove(struct idr *idp, int id) >> struct idr_layer *p; >> struct idr_layer *to_free; >> >> - if (id < 0) >> + if (WARN_ON_ONCE(id

Re: [PATCH 2/8] Consolidate all .h lines at front of intel-iommu.c file

Hi Bill, Could you rebase on latest linus's kernel tree, since there are several changes in intel-iommu.c. This patch can't be applied because of below commits. I think patch need be reabsed on latest linus's tree before post, people will apply your patch without conflict. commit b94e4117f8c4ffb5

Re: [PATCH 6/8] idr: avoid ping-pong

On Sat, Apr 19, 2014 at 9:01 PM, Tejun Heo wrote: > Hello, > > On Sat, Apr 19, 2014 at 06:43:41PM +0800, Lai Jiangshan wrote: >> On 04/19/2014 01:17 AM, Tejun Heo wrote: >> It only frees one layer. And the ida_pre_get() for the next ida_get_new*() >> will allocation it back again. The aim "Throw a

Re: [PATCHv3 1/8] extcon: Add resource-managed extcon register function

Hi, On Sat, Apr 19, 2014 at 10:36 PM, Chanwoo Choi wrote: > Hi, > > On Sat, Apr 19, 2014 at 6:50 PM, Sangjung wrote: >> Hi Chanwoo. >> >> Thanks for your comments. I also add my opinion too. >> >> >> >> On 04/19/2014 04:13 PM, Chanwoo Choi wrote: >>> >>> Hi Sangjung, >>> >>> On Fri, Apr 18, 2014

[PATCH v2 7/7] ARM: mm: use phys_addr_t in __dma_page_[cpu_to_dev/dev_to_cpu]

On a 32 bit ARM architecture with LPAE extension physical addresses cannot fit into unsigned long variable. So fix it by using phys_addr_t instead of unsigned long. Signed-off-by: Santosh Shilimkar --- arch/arm/mm/dma-mapping.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH v2 3/7] of: introduce of_dma_is_coherent() helper

The of_dma_is_coherent() helper parses the given DT device node to see if the "dma-coherent" property is supported and returns true or false accordingly. If the arch is always coherent or always noncoherent, then the default DMA ops has to be specified accordingly. Cc: Greg Kroah-Hartman Cc: Rus

[PATCH v2 5/7] ARM: dma: Use dma_pfn_offset for dma address translation

From: Grygorii Strashko In most of cases DMA addresses can be performed using offset value of Bus address space relatively to physical address space as following: PFN->DMA: __pfn_to_phys(pfn + [-]dma_pfn_offset) DMA->PFN: __phys_to_pfn(dma_addr) + [-]dma_pfn_offset Cc: Greg Kroah-Hartman C

Re: [PATCH 0/2] Support cpufreq driver for Exynos3250

Hi Tomasz, On 19 April 2014 19:21, Tomasz Figa wrote: > Hi Chanwoo, Sachin, > > > On 19.04.2014 15:43, Chanwoo Choi wrote: >> >> Hi Sachin, >> >> On Fri, Apr 18, 2014 at 5:14 PM, Sachin Kamat >> wrote: >>> >>> Hi Chanwoo, >>> >>> On 18 April 2014 07:50, Chanwoo Choi wrote: This patch

[PATCH v2 4/7] of: configure the platform device dma parameters

Retrieve DMA configuration from DT and setup platform device's DMA parameters. The DMA configuration in DT has to be specified using "dma-ranges" and "dma-coherent" properties if supported. We setup dma_pfn_offset using "dma-ranges" and dma_coherent_ops using "dma-coherent" device tree properties.

[PATCH v2 6/7] ARM: dma: implement set_arch_dma_coherent_ops()

Implement the set_arch_dma_coherent_ops() for ARM architecture. Cc: Greg Kroah-Hartman Cc: Russell King Cc: Arnd Bergmann Cc: Olof Johansson Cc: Grant Likely Cc: Rob Herring Cc: Catalin Marinas Cc: Linus Walleij Signed-off-by: Grygorii Strashko Signed-off-by: Santosh Shilimkar --- arch/

[PATCH v2 1/7] device: introduce per device dma_pfn_offset

On few architectures, there are few restrictions on DMAble area of system RAM. That also means that devices needs to know about this restrictions so that the dma_masks can be updated accordingly and dma address translation helpers can add/subtract the dma offset. In most of cases DMA addresses can

[PATCH v2 2/7] of: introduce of_dma_get_range() helper

From: Grygorii Strashko The of_dma_get_range() allows to find "dma-range" property for the specified device and parse it. dma-ranges format: DMA addr (dma_addr) : naddr cells CPU addr (phys_addr_t) : pna cells size : nsize cells Cc: Greg Kroah-Har

Re: [PATCH 0/2] Support cpufreq driver for Exynos3250

On 19.04.2014 16:35, Sachin Kamat wrote: Hi Tomasz, On 19 April 2014 19:21, Tomasz Figa wrote: Hi Chanwoo, Sachin, On 19.04.2014 15:43, Chanwoo Choi wrote: Hi Sachin, On Fri, Apr 18, 2014 at 5:14 PM, Sachin Kamat wrote: Hi Chanwoo, On 18 April 2014 07:50, Chanwoo Choi wrote: Thi

[PATCH v2 0/7] of: setup dma parameters using dma-ranges and dma-coherent

Here is an updated version of [2] based on discussion. Series introduces support for setting up dma parameters based on device tree properties like 'dma-ranges' and 'dma-coherent' and also update to ARM 32 bit port. Earlier version of the same series is here [1]. The 'dma-ranges' helps to take car

aes-x86_64 seems slower than the generic implementation

Hi! When comparing the x86_64 assembly implementation (module aes-x86_64) against the generic AES implementation, I found that the generic implementation was consistenly faster. Test setup #1: * cryptsetup 1.6.4 * Linux v3.15-rc1-356-gebfc45e, https://github.com/Lekensteyn/aur/blob/1d1950

Re: [ANNOUNCE] 3.14-rt1

Hi Sebastian, On Fri, 2014-04-11 at 20:57 +0200, Sebastian Andrzej Siewior wrote: > Dear RT folks! > > I'm pleased to announce the v3.14-rt1 patch set. This hunk in hotplug-light-get-online-cpus.patch looks like a bug. @@ -333,7 +449,7 @@ static int __ref _cpu_down(unsigned int

Fw: serial console does not wake from S3 suspend

"Valerio Vanni" ha scritto nel messaggio news:lg9etc$9fl$1...@ger.gmane.org When resuming from S3 suspend, serial console starts sending garbage on the serial port. Not continuously, it sends garbage only when in local console prints a text. It stops only when the (sending) machine is shut down,

[PATCH] ARM: dts: twl4030: Add twl4030-madc node

Add madc node to twl4030 so DT boards can use it. Signed-off-by: Marek Belisko --- arch/arm/boot/dts/twl4030.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi index 86cfc7d..36ae916 100644 --- a/arch/arm/boot/dts/twl403

[PATCH] perf test x86: Fit memory leak in sample_ustack()

buf is not freed, when kernel failed to get stack map and return. Signed-off-by: Masanari Iida --- tools/perf/arch/x86/tests/dwarf-unwind.c | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/arch/x86/tests/dwarf-unwind.c b/tools/perf/arch/x86/tests/dwarf-unwind.c index b602ad9..68f2

Re: [PATCH] tracing:Do not profile dumpstack utilities to fix stack trace output

On Sat, 19 Apr 2014 15:45:46 +0800 Jiaxing Wang wrote: > When function_graph tracer is enabled, we get stack trace like this: > > DepthSize Location(88 entries) > - >0) 3232 0 update_curr+0xe/0x1e0 >1) 3232 0 dump

Re: [PATCH] tracing: Correct braces usage in if-else statement

On Sat, 19 Apr 2014 21:58:23 +0800 Lin Yongting wrote: > There are some incorrect braces usages in kernerl/trace/trace.c, including: > 1. Missing braces in 'if' or 'else' branch. > 2. Unnecessary braces in 'if' statement. > > Fix them according to kernel CodeStyle. I understand that this is par

Re: [PATCH 00/28] nios2 Linux kernel port

On Friday 18 April 2014, H. Peter Anvin wrote: > On 04/18/2014 05:26 AM, Ley Foon Tan wrote: > > This patchset adds the Linux kernel port for Nios II processor from Altera. > > The nios2 Linux port follows the guidance for new architecture ports using > > generic headers (including unistd.h). > >

[PATCH 4/4] mm: zpool: update zswap to use zpool

Change zswap to use the zpool api instead of directly using zbud. Add a boot-time param to allow selecting which zpool implementation to use, with zbud as the default. Signed-off-by: Dan Streetman --- mm/zswap.c | 70 ++ 1 file changed,

[PATCH 0/4] mm: zpool: add common api for zswap to use zbud/zsmalloc

In order to allow zswap users to choose between zbud and zsmalloc for the compressed storage pool, this patch set adds a new api "zpool" that provides an interface to both zbud and zsmalloc. Only a minor change to zbud's interface was needed, as detailed in the first patch; zsmalloc required shrin

[PATCH 3/4] mm: zpool: implement common zpool api to zbud/zsmalloc

Add zpool api. zpool provides an interface for memory storage, typically of compressed memory. Users can select what backend to use; currently the only implementations are zbud, a low density implementation with exactly two compressed pages per storage page, and zsmalloc, a higher density impleme

[PATCH 2/4] mm: zpool: implement zsmalloc shrinking

Add zs_shrink() and helper functions to zsmalloc. Update zsmalloc zs_create_pool() creation function to include ops param that provides an evict() function for use during shrinking. Update helper function fix_fullness_group() to always reinsert changed zspages even if the fullness group did not c

[PATCH 1/4] mm: zpool: zbud_alloc() minor param change

Change zbud to store gfp_t flags passed at pool creation to use for each alloc; this allows the api to be closer to the existing zsmalloc interface, and the only current zbud user (zswap) uses the same gfp flags for all allocs. Update zswap to use changed interface. Signed-off-by: Dan Streetman

Re: [PATCH 09/28] nios2: Page table management

Hi! > This patch adds support for page table management. > > Signed-off-by: Ley Foon Tan > +/* > + * Initialize a new pgd / pmd table with invalid pointers. > + */ > +static void pgd_init(pgd_t *pgd) > +{ > + unsigned long *p = (unsigned long *) pgd; > + int i; > + > + for (i = 0; i

Re: [PATCH 16/28] nios2: System calls handling

On Fri 2014-04-18 20:26:59, Ley Foon Tan wrote: > This patch adds support for system calls from userspaces. It uses the > asm-generic/unistd.h definitions with architecture spcific syscall. The > sys_call_table > is just an array defined in a C file and it contains pointers to the syscall > funct

Re: [RFC] Only a.out QMAGIC format is working

Hi! > I was researching about old binary formats and did some tests. > Meantime, I was able to run sucessfully only the QMAGIC format. > Nonetheless, the OMAGIC, NMAGIC and ZMAGIC didn't work anymore. Some time ago, I ran into similar problem, and turning off userspace randomization was neccessar

Re: current->sched_class->yield_task is NULL, any hint?

On Wed, Apr 9, 2014 at 5:39 PM, Lin Ming wrote: > On Wed, Apr 9, 2014 at 1:08 PM, Peter Zijlstra wrote: [...] >>> >>> Look at that, its calling yield() from a non-preemptible context as >>> well. >>> >>> That code is full of fail. >> >> *phew* none of that br_igmp_* muck lives in any kernel tre

Re: [PATCH v2 0/7] of: setup dma parameters using dma-ranges and dma-coherent

Dear Santosh Shilimkar, On Sat, 19 Apr 2014 10:32:45 -0400, Santosh Shilimkar wrote: > Here is an updated version of [2] based on discussion. Series introduces > support for setting up dma parameters based on device tree properties > like 'dma-ranges' and 'dma-coherent' and also update to ARM 32 b

Re: [Kernel-BR] Re: [RFC] Only a.out QMAGIC format is working

Pavel, Thank you. Maintainers, is there some chance to fix it or a.out is really doomed? 2014-04-19 13:15 GMT-03:00 Pavel Machek : > Hi! > >> I was researching about old binary formats and did some tests. >> Meantime, I was able to run sucessfully only the QMAGIC format. >> Nonetheless, the OMA

Re: current->sched_class->yield_task is NULL, any hint?

On Sat, Apr 19, 2014 at 9:21 AM, Paul Gortmaker wrote: > On Wed, Apr 9, 2014 at 5:39 PM, Lin Ming wrote: >> On Wed, Apr 9, 2014 at 1:08 PM, Peter Zijlstra wrote: > > [...] > Look at that, its calling yield() from a non-preemptible context as well. That code is full of fa

[PATCH 0/5] uprobes/x86: cleanup validate_insn_* paths, fix X86_X32 case

Peter, feel free to ignore 1-4, but could you look at 5/5? It lacks the test-case because I do not have a x32-ready testing machine. On 04/17, Oleg Nesterov wrote: > > This series only fixes the problem. I'll send more changes to address > some of TODO's mentioned in the changelogs later. In parti

[PATCH 5/5] uprobes/x86: Fix is_64bit_mm() with CONFIG_X86_X32

is_64bit_mm() assumes that mm->context.ia32_compat means the 32-bit instruction set, this is not true if the task is TIF_X32. Change set_personality_ia32() to initialize mm->context.ia32_compat by TIF_X32 or TIF_IA32 instead of 1. This allows to fix is_64bit_mm() without affecting other users, the

[PATCH 1/5] uprobes/x86: Add uprobe_init_insn(), kill validate_insn_{32,64}bits()

validate_insn_32bits() and validate_insn_64bits() are very similar, turn them into the single uprobe_init_insn() which has the additional "bool x86_64" argument which can be passed to insn_init() and used to choose between good_insns_64/good_insns_32. Also kill UPROBE_FIX_NONE, it has no users. N

  1   2   >