Re: [PATCH 6/6] UBI: Fastmap: Make ubi_refill_pools() fair

Hi Richard On 12/5/2014 10:56 PM, Richard Weinberger wrote: -/** - * refill_wl_user_pool - refills all the fastmap pool used by ubi_wl_get_peb. - * @ubi: UBI device description object - */ -static void refill_wl_user_pool(struct ubi_device *ubi) -{ -struct ubi_fm_pool *pool = >fm_pool; +

Re: [PATCH v5 1/4] tools/perf: support parsing parameterized events

Jiri Olsa [jo...@redhat.com] wrote: | anyway we could assign directly to the param term name as you do, | but I think we just need to mark the term as parametrized, like: | | in /sys/bus/event_source/devices/pmu/events/event_name you have: | param2=?,bar=1,param1=? I like the idea of just

Re: [PATCH 4/6] UBI: Fastmap: Fix races in ubi_wl_get_peb()

On 12/5/2014 11:08 PM, Richard Weinberger wrote: spin_unlock(>wl_lock); +if (retried) { +ubi_err(ubi, "Unable to get a free PEB from user WL pool"); +ret = -ENOSPC; +goto out; +} +retried = 1; Why did you decide to

Re: [PATCH] video: ocfb: Fix data type warning

On Fri, Dec 05, 2014 at 04:18:30PM +0800, Qiang Chen wrote: > When allocate framebuffer memory using dma_alloc_coherent(), > we'd better use dma_addr_t instead of phys_addr_t. Because the > address we got in fact is DMA or bus address for the platform. > > This patch also fixes below build

Re: Where exactly will arch_fast_hash be used

If you want DoS-resistant hash tables, I'm working on adding SipHash to the kernel. This is a keyed pseudo-random function designed specifically for that application. I am starting with ext4 directory hashes, and then intended to expand to secure sequence numbers (since it's far faster than

[no subject]

¿Necesita un préstamo personal o de negocios urgente? Si es así Email: customers_solut...@live.com para el formulario solicitud de préstamo y obtener más información. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

[PATCH] arch: arm: mach-mxs: mach-mxs.c: Remove unused function

Remove the function __mxs_togl() that is not used anywhere. This was partially found by using a static code analysis program called cppcheck. Signed-off-by: Rickard Strandqvist --- arch/arm/mach-mxs/mach-mxs.c |5 - 1 file changed, 5 deletions(-) diff --git

[PATCH] arch: arm: mach-msm: vreg.c: Remove unused function

Remove the function vreg_put() that is not used anywhere. This was partially found by using a static code analysis program called cppcheck. Signed-off-by: Rickard Strandqvist --- arch/arm/mach-msm/include/mach/vreg.h |1 - arch/arm/mach-msm/vreg.c |4 2 files

[PATCH] arch: arm: mach-msm: smd.c: Remove some unused functions

Removes some functions that are not used anywhere: smsm_set_sleep_duration() smsm_get_state() smd_wait_until_writable() smd_wait_until_readable() smd_write_atomic() smd_sleep_exit() This was partially found by using a static code analysis program called cppcheck. Signed-off-by: Rickard

[PATCH v3] ASoC: add xtensa xtfpga I2S interface and platform

XTFPGA boards provides an audio subsystem that consists of TI CDCE706 clock synthesizer, I2S transmitter and TLV320AIC23 audio codec. I2S transmitter has MMIO-based interface that resembles that of the OpenCores I2S transmitter. I2S transmitter is always a master on I2S bus. There's no

Re: [PATCH 3.12 00/66] 3.12.35-stable review

On 12/06/2014 07:07 AM, Jiri Slaby wrote: This is the start of the stable review cycle for the 3.12.35 release. There are 66 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

[PATCH v3] staging: lustre: fix sparse warning on LPROC_SEQ_FOPS macros

This patch fix a sparse warning in lustre sources warning: incorrect type in argument 1 (different address spaces) expected void [noderef] *to got char * This is done by adding the missing __user attribute on userland pointers inside the LPROC_SEQ_FOPS like macros: - LPROC_SEQ_FOPS -

[PATCH v2] staging: lustre: replace static value with define

This patch replace the value '80' used in several files in the lustre source code with a define LUSTRE_MDT_MAXNAMELEN. This value is used in 4 different structures as the maximum len for a service name. According to the comments, these names follow a convention which make it possible to use

Re: [PATCH v4 2/5] crypto: AF_ALG: add AEAD support

On Fri, Dec 05, 2014 at 10:51:51PM +0100, Stephan Mueller wrote: > > Would you please be so kind and help me understand when some operations are > intended for the parent FD and when for the child FD? If it changes the tfm it goes in the parent FD otherwise it's the child FD. Cheers, -- Email:

Re: [PATCH v4 2/5] crypto: AF_ALG: add AEAD support

On Sat, Dec 06, 2014 at 09:08:54PM +0100, Stephan Mueller wrote: > > While implementing that request, I thought about setting the auth size as > part > of the msg control in sendmsg instead of setsockopt. This would save us a > system call and thus CPU cycles. No, this is a tfm property and

[PATCHv2 3/3] ARM:dts:sunxi:ps2 dt nodes for A10/A20 PS2 controller.

Added ps2 nodes in lime2 board dts. By default ps20 and ps21 nodes are commented as ps20 pins conflict with HDMI connector on Lime2 Board. Signed-off-by: vishnupatekar --- arch/arm/boot/dts/sun4i-a10.dtsi| 27 +

[PATCHv2 0/3] ARM:sunxi:ps2 Added support for A10/A20 ps2 controller.

Here is v2 of SUNXI PS2 controller support patch-set as with v1. Changes in v2: 1. added default n depends on ARCH_SUNXI || COMPILE_TEST in Kconfig. 2. handled errors and free resources on errors. 3. used BIT(x), DIV_ROUND_UP macros. 4. corrected style errors. 5. added support for A10 also, A10

[PATCHv2 1/3] sunxi:dts-bindings:input:ps2 bindings for A10/A20 ps2.

A10 and A20 have same PS2 addresses, clocks, interrupts. added compatible as allwinner,sun4i-a10-ps2. Signed-off-by: vishnupatekar --- .../bindings/input/allwinner,sunxi-ps2.txt | 23 1 file changed, 23 insertions(+) create mode 100644

[PATCHv2 2/3] sunxi:drivers:input:ps2 Added sunxi A10/A20 ps2 driver

-added compatible as allwinner,sun4i-a10-ps2 and allwinner,sun7i-a20-ps2. - added default n depends on ARCH_SUNXI || COMPILE_TEST in Kconfig. -handled errors and free resources on errors. -used BIT(x), DIV_ROUND_UP macros. -corrected style errors. Signed-off-by: vishnupatekar ---

Re: [PATCH v2 1/4] pwm: kona: Remove setting default smooth type and polarity for all channels

On Thu, Dec 4, 2014 at 12:22 PM, Jonathan Richardson wrote: > Hi Tim, > > I'm going to take over this submission because I made the changes to the > driver. Arun was filling in for me while I was on leave. Now I'm back > and I think I can help clarify why these changes were made. A summary > for

Re: How can I parse the command name from /proc//stat?

Thank you, I dislike the idea of relying upon stat never gaining any other part that uses ) but that would work instead of using status. -- 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

Re: [PATCH 3.17 000/122] 3.17.5-stable review

On Sat, Dec 06, 2014 at 02:35:52PM -0700, Shuah Khan wrote: > On 12/05/2014 03:42 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.17.5 release. > > There are 122 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH] arch: arm: mach-davinci: cdce949.c: Remove unused function

Remove the function cdce_set_rate() that is not used anywhere. This was partially found by using a static code analysis program called cppcheck. Signed-off-by: Rickard Strandqvist --- arch/arm/mach-davinci/cdce949.c | 37 --

[PATCH] arch: arm: common: edma.c: Remove some unused functions

Removes some functions that are not used anywhere: edma_shadow0_read() edma_or_array() This was partially found by using a static code analysis program called cppcheck. Signed-off-by: Rickard Strandqvist --- arch/arm/common/edma.c |8 1 file changed, 8 deletions(-) diff --git

[PATCH] arch: arc: plat-arcfpga: smp.c: Remove some unused functions

Removes some functions that are not used anywhere: idu_irq_get_pend() idu_irq_get_ack() This was partially found by using a static code analysis program called cppcheck. Signed-off-by: Rickard Strandqvist --- arch/arc/plat-arcfpga/smp.c | 27 --- 1 file changed, 27

Re: [PATCH] staging: lustre: replace static value with define

On Sat, Dec 06, 2014 at 05:09:29PM +, Dilger, Andreas wrote: > > > >diff --git a/drivers/staging/lustre/lustre/fld/lproc_fld.c > >b/drivers/staging/lustre/lustre/fld/lproc_fld.c > >index 74b4db9..7a55941 100644 > >--- a/drivers/staging/lustre/lustre/fld/lproc_fld.c > >+++

Re: frequent lockups in 3.18rc4

On Fri, 5 Dec 2014, Linus Torvalds wrote: > On Fri, Dec 5, 2014 at 10:48 AM, Dave Jones wrote: > > > > In the meantime, I rebooted into the same kernel, and ran trinity > > solely doing the lsetxattr syscalls. > > Any particular reason for the lsetxattr guess? Just the last call > chain? I don't

Re: [PATCH] staging: lustre: fix sparse warning on LPROC_SEQ_FOPS macros

Andreas, On Sat, Dec 06, 2014 at 05:05:14PM +, Dilger, Andreas wrote: > On 2014/12/05, 3:41 PM, "Tristan Lelong" wrote: > > > Sorry, but I don't see where you get 80 from? fh_name is declared as a > "const char *", and initialized in the declaration of fld_hash[]. I'd > thought to reply

[PATCH] arch: alpha: kernel: core_titan.c: Remove some unused functions

Removes some functions that are not used anywhere: titan_write_tig() titan_read_tig() This was partially found by using a static code analysis program called cppcheck. Signed-off-by: Rickard Strandqvist --- arch/alpha/kernel/core_titan.c | 14 -- 1 file changed, 14 deletions(-)

Re: [PATCH 2/4] clk: iproc: add initial common clock support

On Thu, Dec 4, 2014 at 1:43 PM, Ray Jui wrote: > This adds basic and generic support for various iProc PLLs and clocks > including the ARMPLL, GENPLL, LCPLL, MIPIPLL, and ASIU clocks. > > SoCs under the iProc architecture can define their specific register > offsets and clock parameters for their

Re: next-20141204 crashing on ext4_fill_super()

Please revert fdfe07398761 and that should the crashes; this will be fixed in the next linux-next release. My apologies for the inconvenience. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: frequent lockups in 3.18rc4

On Sat, 6 Dec 2014, Chuck Ebbert wrote: > On Fri, 5 Dec 2014 13:48:08 -0500 > Dave Jones wrote: > > > [ 1611.749570] [] do_nmi+0xb8/0xf0 > > [ 1611.750438] [] end_repeat_nmi+0x1e/0x2e > > [ 1611.751312] [] ? preempt_count_add+0x18/0xb0 > > [ 1611.752177] [] ? preempt_count_add+0x18/0xb0 > >

[PATCH] ASoC: fix platform_no_drv_owner.cocci warnings

sound/soc/xtensa/xtfpga-i2s.c:666:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci Signed-off-by: Fengguang Wu --- xtfpga-i2s.c |1 - 1 file changed, 1

[PATCH] kobject: grammar fix

Signed-off-by: John de la Garza --- Documentation/kobject.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/kobject.txt b/Documentation/kobject.txt index f87241d..1be59a3 100644 --- a/Documentation/kobject.txt +++ b/Documentation/kobject.txt @@ -173,7 +173,7

Re: [PATCH 3.14 00/73] 3.14.26-stable review

On 12/05/2014 03:44 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.14.26 release. > There are 73 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

Re: [PATCH 3.10 00/45] 3.10.62-stable review

On 12/05/2014 03:44 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.10.62 release. > There are 45 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

Re: [PATCH 3.17 000/122] 3.17.5-stable review

On 12/05/2014 03:42 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.17.5 release. > There are 122 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

Re: frequent lockups in 3.18rc4

On Sat, Dec 6, 2014 at 9:09 PM, Linus Torvalds wrote: > On Sat, Dec 6, 2014 at 8:22 AM, Martin van Es wrote: >> >> Hope this may help in finding the right direction for this bug? > > If you can reproduce it with your spare J1900 system and could perhaps > bisect it there, that would be a huge

Re: frequent lockups in 3.18rc4

On Sat, Dec 6, 2014 at 12:09 PM, Linus Torvalds wrote: > On Sat, Dec 6, 2014 at 8:22 AM, Martin van Es wrote: >> >> Hope this may help in finding the right direction for this bug? > > If you can reproduce it with your spare J1900 system and could perhaps > bisect it there, that would be a huge

Re: [BUG] kzalloc overflow in lpfc driver on 6k core system

Alex, Myself and several others here at Emulex maintain the code. The recommendations look fine. Feel free to post something if you beat us to the work. -- james s On 12/3/2014 11:05 AM, Alex Thorlton wrote: On Tue, Dec 02, 2014 at 10:39:40PM +, Elliott, Robert (Server Storage)

Re: frequent lockups in 3.18rc4

On Sat, Dec 6, 2014 at 8:22 AM, Martin van Es wrote: > > Hope this may help in finding the right direction for this bug? If you can reproduce it with your spare J1900 system and could perhaps bisect it there, that would be a huge help. Linus -- To unsubscribe from

Re: [PATCH v4 2/5] crypto: AF_ALG: add AEAD support

Am Freitag, 5. Dezember 2014, 22:51:51 schrieb Stephan Mueller: Hi Herbert, > > > +static struct proto_ops algif_aead_ops = { > > > + .family = PF_ALG, > > > + > > > + .connect= sock_no_connect, > > > + .socketpair = sock_no_socketpair, > > > + .getname

[PATCH 4/5] f2fs: release inmemory pages when the file was closed

If file is closed, let's drop inmemory pages. Signed-off-by: Jaegeuk Kim --- fs/f2fs/file.c | 9 + 1 file changed, 9 insertions(+) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index 146e58a..b6f3fbf 100644 --- a/fs/f2fs/file.c +++ b/fs/f2fs/file.c @@ -901,6 +901,14 @@ static int

[PATCH 5/5] f2fs: count the number of inmemory pages

This patch adds counting # of inmemory pages in the page cache. Signed-off-by: Jaegeuk Kim --- fs/f2fs/debug.c | 3 +++ fs/f2fs/f2fs.h| 3 ++- fs/f2fs/segment.c | 3 +++ 3 files changed, 8 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/debug.c b/fs/f2fs/debug.c index 40b679c..4e2e39c

[PATCH 2/5] f2fs: count inline_xx in do_read_inode

In do_read_inode, if we failed __recover_inline_status, the inode has inline flag without increasing its count. Later, f2fs_evict_inode will decrease the count, which causes -1. Signed-off-by: Jaegeuk Kim --- fs/f2fs/inode.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff

[PATCH 1/5] f2fs: do retry operations with cond_resched

This patch revists retrial paths in f2fs. The basic idea is to use cond_resched instead of retrying from the very early stage. Suggested-by: Gu Zheng Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h| 7 +++ fs/f2fs/gc.c | 5 ++--- fs/f2fs/node.c| 41

[PATCH 3/5] f2fs: set page private for inmemory pages for truncation

The inmemory pages should be handled by invalidate_page since it needs to be released int the truncation path. Signed-off-by: Jaegeuk Kim --- fs/f2fs/segment.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c index c79d67e..3ebcf96 100644 ---

next-20141204 crashing on ext4_fill_super()

Hello, everyone. next-20141204 started crashing on my laptop with the following error right after I enter my disk encryption password: http://opsfelder.com/~murilo/lkml/next-20141204_crash.jpg The previous version next-20141203 was working just fine. next-20141205 is also crashing.

[PATCH v3 2/3] fanotify: dont recalculate a marks mask if only the ignored mask changed

If removing bits from a marks ignored mask, the concerning inodes/vfsmounts mask is not affected. So dont recalculate it. Signed-off-by: Lino Sanfilippo Reviewed-by: Jan Kara --- fs/notify/fanotify/fanotify_user.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH v3 3/3] fanotify: dont set FAN_ONDIR implicitly on a marks ignored mask

Currently FAN_ONDIR is always set on a marks ignored mask when the event mask is extended without FAN_MARK_ONDIR being set. This may result in events for directories being ignored unexpectedly for call sequences like fanotify_mark(fd, FAN_MARK_ADD, FAN_OPEN | FAN_ONDIR , AT_FDCWD, "dir");

[PATCH v3 1/3] fanotify: only destroy mark when both mask and ignored_mask are cleared

In fanotify_mark_remove_from_mask() a mark is destroyed if only one of both bitmasks (mask or ignored_mask) of a mark is cleared. However the other mask may still be set and contain information that should not be lost. So only destroy a mark if both masks are cleared. Signed-off-by: Lino

Vorgeschlagene Finanzdarlehen...

Vorgeschlagene Finanzdarlehen Ich bin ein und bietet privater Investor Raha Darlehen für alle Personen, zu haben und gute Manieren in der Lage, mit einem Zinssatz von und 3% einer von Laufzeit 1-30 aastat zurück, von der abhängig gewünschten Menge. Ich will meine Brüder und einfach nur Schwestern

Re: N900: fixing MMC at boot

On Saturday 06 December 2014 19:04:29 Pavel Machek wrote: > On Sat 2014-12-06 18:40:16, Pali Rohár wrote: > > On Saturday 06 December 2014 18:35:27 Pavel Machek wrote: > > > Hi! > > > > > > For a long time, MMC was not working during boot... > > > (making the box unusable without nfsroot). It

Make it clear that cache-l2x0 handles L310 cache controller, too

It is not clear from the filename, and comment at the begining adds to the confusion by not listing L310. Fix it. Signed-off-by: Pavel Machek diff --git a/arch/arm/mm/cache-l2x0.c b/arch/arm/mm/cache-l2x0.c index 5e65ca8..b07cc54 100644 --- a/arch/arm/mm/cache-l2x0.c +++

Re: N900: fixing MMC at boot

On Sat 2014-12-06 18:40:16, Pali Rohár wrote: > On Saturday 06 December 2014 18:35:27 Pavel Machek wrote: > > Hi! > > > > For a long time, MMC was not working during boot... (making > > the box unusable without nfsroot). It seems problem is in the > > regulators, because with diff below, I was

[ 00/25] 2.6.32.65-longterm review

This is the start of the longterm review cycle for the 2.6.32.65 release. All patches will be posted as a response to this one. If anyone has any issue with these being applied, please let me know. If anyone is a maintainer of the proper subsystem, and wants to add a Signed-off-by: line to the

[ 19/25] USB: whiteheat: Added bounds checking for bulk command response

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: James Forshaw commit c5fd4126151855330280ea9382684980afcfdd03 upstream This patch fixes a potential security issue in the whiteheat USB driver which might allow a local attacker to cause

[ 09/25] x86, espfix: Make espfix64 a Kconfig option, fix UML

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: "H. Peter Anvin" commit 197725de65477bc8509b41388157c1a2283542bb upstream. Make espfix64 a hidden Kconfig option. This fixes the x86-64 UML build which had broken due to the

[ 10/25] x86, espfix: Make it possible to disable 16-bit support

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: "H. Peter Anvin" commit 34273f41d57ee8d854dcd2a1d754cbb546cb548f upstream. Embedded systems, which may be very memory-size-sensitive, are extremely unlikely to ever encounter any 16-bit

[ 16/25] net/l2tp: dont fall back on UDP [get|set]sockopt

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Sasha Levin (commit 3cf521f7dc87c031617fd47e4b7aa2593c2f3daf upstream) The l2tp [get|set]sockopt() code has fallen back to the UDP functions for socket option levels != SOL_PPPOL2TP since

[ 02/25] x86, 64-bit: Move K8 B step iret fixup to fault entry asm

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Brian Gerst Move the handling of truncated %rip from an iret fault to the fault entry path. This allows x86-64 to use the standard search_extable() function. Signed-off-by: Brian Gerst

[ 05/25] x86-32, espfix: Remove filter for espfix32 due to race

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: "H. Peter Anvin" commit 246f2d2ee1d715e1077fc47d61c394569c8ee692 upstream. It is not safe to use LAR to filter when to go down the espfix path, because the LDT is per-process (rather than

[ 24/25] mac80211: fix fragmentation code, particularly for encryption

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit a722a419815ed203b519151f9556859ff256638b upstream The "new" fragmentation code (since my rewrite almost 5 years ago) erroneously sets skb->len rather than using

[ 25/25] ttusb-dec: buffer overflow in ioctl

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit dc0ab1ddeb0c5f5eb3f37a72eadb394792b3c40d upstream We need to add a limit check here so we don't overflow the buffer. Signed-off-by: Dan Carpenter Signed-off-by:

[ 23/25] net: sctp: fix NULL pointer dereference in af->from_addr_param on malformed packet

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit a6e1af6f5e9e75095ae1b004f6f00082e5fc4d2d upstream An SCTP server doing ASCONF will panic on malformed INIT ping-of-death in the form of: INIT[PARAM:

[ 22/25] udf: Avoid infinite loop when processing indirect ICBs

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 541d302ee5c46336cbad333222bc278b76cc1c42 upstream We did not implement any bound on number of indirect ICBs we follow when loading inode. Thus corrupted medium could cause

[ 18/25] ALSA: control: Fix replacing user controls

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen (commit 82262a46627bebb0febcc26664746c25cef08563 upstream) There are two issues with the current implementation for replacing user controls. The first is that the code

[ 11/25] x86_64/entry/xen: Do not invoke espfix64 on Xen

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 7209a75d2009dbf7745e2fd354abf25c3deb3ca3 upstream. This moves the espfix64 logic into native_iret. To make this work, it gets rid of the native patch for

[ 08/25] x86, espfix: Fix broken header guard

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: "H. Peter Anvin" commit 20b68535cd27183ebd3651ff313afb2b97dac941 upstream. Header guard is #ifndef, not #ifdef... Reported-by: Fengguang Wu Signed-off-by: H. Peter Anvin Signed-off-by:

[ 03/25] x86-64: Adjust frame type at paranoid_exit:

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Jan Beulich As this isn't an exception or interrupt entry point, it doesn't have any of the hardware provide frame layouts active. Signed-off-by: Jan Beulich Acked-by: Alexander van

[ 20/25] net: sctp: fix panic on duplicate ASCONF chunks

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit 12b18fdbbda747ad22a7684413a6559b681e503c upstream When receiving a e.g. semi-good formed connection scan in the form of ... -- INIT[ASCONF;

[ 06/25] x86-64, espfix: Dont leak bits 31:16 of %esp returning to 16-bit stack

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: "H. Peter Anvin" commit 3891a04aafd668686239349ea58f3314ea2af86b upstream. The IRET instruction, when returning to a 16-bit segment, only restores the bottom 16 bits of the user space

[ 12/25] x86/espfix/xen: Fix allocation of pages for paravirt page tables

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Boris Ostrovsky commit 8762e5092828c4dc0f49da5a47a644c670df77f3 upstream. init_espfix_ap() is currently off by one level when informing hypervisor that allocated pages will be used for

[ 07/25] x86, espfix: Move espfix definitions into a separate header file

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: "H. Peter Anvin" commit e1fe9ed8d2a4937510d0d60e20705035c2609aea upstream. Sparse warns that the percpu variables aren't declared before they are defined. Rather than hacking around it,

[ 04/25] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: "H. Peter Anvin" commit b3b42ac2cbae1f3cecbb6229964a4d48af31d382 upstream. The IRET instruction, when returning to a 16-bit segment, only restores the bottom 16 bits of the user space

[ 13/25] x86_64, traps: Stop using IST for #SS

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski On a 32-bit kernel, this has no effect, since there are no IST stacks. On a 64-bit kernel, #SS can only happen in user code, on a failed iret to user space, a canonical

[ 17/25] ALSA: control: Dont access controls outside of protected regions

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen (commit fd9f26e4eca5d08a27d12c0933fceef76ed9663d upstream) A control that is visible on the card->controls list can be freed at any time. This means we must not access

[ 14/25] x86_64, traps: Fix the espfix64 #DF fixup and rewrite it in C

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski There's nothing special enough about the espfix64 double fault fixup to justify writing it in assembly. Move it to C. This also fixes a bug: if the double fault came from

[PATCH] regulator.txt: fix to fit to 80 columns

Fix documentation to fit into 80 columns. Signed-off-by: Pavel Machek diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt index 8607433..a0f9983 100644 ---

[ 21/25] net: sctp: fix remote memory pressure from excessive queueing

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit b2d33ef40de7161c23032106284959ae75bdf3cd upstream This scenario is not limited to ASCONF, just taken as one example triggering the issue. When receiving ASCONF

[ 15/25] x86_64, traps: Rework bad_iret

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski It's possible for iretq to userspace to fail. This can happen because of a bad CS, SS, or RIP. Historically, we've handled it by fixing up an exception from iretq to land

[ 01/25] net: sendmsg: fix failed backport of "fix NULL pointer dereference"

2.6.32-longterm review patch. If anyone has any objections, please let me know. -- From: Willy Tarreau Luis Henriques reported that while backporting commit 40eea80 ("net: sendmsg: fix NULL pointer dereference") and applying the diff by hand, I made a typo resulting in the

Re: N900: fixing MMC at boot

On Saturday 06 December 2014 18:35:27 Pavel Machek wrote: > Hi! > > For a long time, MMC was not working during boot... (making > the box unusable without nfsroot). It seems problem is in the > regulators, because with diff below, I was able to mount root > on SD card for a first time ... in a

Re: [PATCH 2/2 V8] intel_pstate: add kernel parameter to force loading.

On 12/5/2014 9:16 PM, ethan wrote: > Linda， > >> 在 2014年12月6日，00:09，Linda Knippers 写道： >> >>> On 12/5/2014 4:40 AM, Ethan Zhao wrote: >>> To force loading on Oracle Sun X86 servers, provide one kernel command line >>> parameter >>> >>> intel_pstate = force >>> >>> For those who be aware of the

N900: fixing MMC at boot

Hi! For a long time, MMC was not working during boot... (making the box unusable without nfsroot). It seems problem is in the regulators, because with diff below, I was able to mount root on SD card for a first time ... in a long time. Signed-off-by: Pavel Machek [but not for upstream] diff

Re: [PATCH] arm64: Enable CONFIG_COMPAT also for 64k page size

On 04.12.14 19:20, Will Deacon wrote: > On Thu, Dec 04, 2014 at 03:46:33PM +, Alexander Graf wrote: >> With binutils 2.25 the default alignment for 32bit arm sections changed to >> have everything 64k aligned. Armv7 binaries built with this binutils version >> run successfully on an arm64

Re: [PATCH 2/4] iio: dht11: IRQ fixes

Hi Richard, finally got around to test this patch on all HW I have. As expected the preamble needs to be shortend by two edges: With your patch in its current form, the driver stops to work reliably with DHT11. Also with DHT22 you get some delay when reading the data, because you always wait for

Re: [PATCH] staging: lustre: replace static value with define

On 2014/12/06, 12:16 AM, "Tristan Lelong" wrote: >This patch replace the value '80' used in several files in the lustre >source code >with a define LUSTRE_MDT_MAXNAMELEN. > >This value is used in 4 different structures as the maximum len for a >service name. >According to the comments, these

Re: [PATCH] staging: lustre: fix sparse warning on LPROC_SEQ_FOPS macros

On 2014/12/05, 3:41 PM, "Tristan Lelong" wrote: >On Fri, Dec 05, 2014 at 01:27:23PM -0800, Greg KH wrote: >> On Fri, Dec 05, 2014 at 12:03:47AM -0800, Tristan Lelong wrote: >> > static ssize_t >> > -fld_proc_hash_seq_write(struct file *file, const char *buffer, >> > - size_t

[PATCH] mm: memcontrol.c: Cleaning up function that are not used anywhere

Remove function mem_cgroup_lru_names_not_uptodate() that is not used anywhere. And move BUILD_BUG_ON() to the beginning of memcg_stat_show() instead. This was partially found by using a static code analysis program called cppcheck. Signed-off-by: Rickard Strandqvist --- mm/memcontrol.c |7

[PATCH V4 1/1] Drivers: hv: vmbus: Implement a clockevent device

Implement a clockevent device based on the timer support available on Hyper-V. In this version of the patch I have addressed Jason's review comments. Signed-off-by: K. Y. Srinivasan Reviewed-by: Jason Wang --- arch/x86/include/uapi/asm/hyperv.h | 11 + drivers/hv/hv.c

Re: frequent lockups in 3.18rc4

Hi, I've been following this thread with some interrest because my mythtv based media centre suffered from sudden freezes. I thought I had tried everything to solve the problem (including exchanging hardware) until I caught the slashdot article discussing this bug. I was running on 3.17.3 and and

RE: [PATCH 1/1] Drivers: hv: vmbus: Implement a clockevent device

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Friday, December 5, 2014 9:08 PM > To: KY Srinivasan > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; > o...@aepfle.de; a...@canonical.com; jasow...@redhat.com > Subject: Re: [PATCH 1/1]

Re: [PATCH] arch: uapi: asm: mman.h: Let MADV_FREE have same value for all architectures

Hello Maintainers: After this patch, our parisc can pass allmodconfig in linux next tree, for me, we can say parisc specific code have no touch for allmodconfig. :-) But for parisc gcc latest upstream compiler, I found several issues, and I shall try to analyse them and communicate with gcc

[PATCH 3/3] x86, microcode: Reload microcode on resume

From: Borislav Petkov Normally, we do reapply microcode on resume. However, in the cases where that microcode comes from the early loader and the late loader hasn't been utilized yet, there's no easy way for us to go and apply the patch applied during boot by the early loader. Thus, reuse the

[PATCH 1/3] x86, microcode, intel: Drop unused parameter

From: Borislav Petkov apply_microcode_early() doesn't use mc_saved_data, kill it. Signed-off-by: Borislav Petkov --- arch/x86/kernel/cpu/microcode/intel_early.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/arch/x86/kernel/cpu/microcode/intel_early.c

[PATCH 0/3] x86, microcode: Reloading fixes

From: Borislav Petkov Hi guys, please pull three fixes for the microcode loader. More specifically, microcode reloading for 3.19. Patches are against tip/x86/microcode. I have this also as a tag if you'd prefer to pull: git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git

[PATCH 2/3] x86, microcode: Don't initialize microcode code on paravirt

From: Boris Ostrovsky Paravirtual guests are not expected to load microcode into processors and therefore it is not necessary to initialize microcode loading logic. In fact, under certain circumstances initializing this logic may cause the guest to crash. Specifically, 32-bit kernels use

Re: Disable input device

On Sat, 29 Nov 2014 18:24:03 +0100 Pali Rohár wrote: > What do you think about adding new sysfs file "disable" (accept > values 1 or 0) for every input device? With "1" it cause that > kernel will drop all events from specific input device and if > driver provide some function is can be

[PATCH 3.12 10/66] PCI/MSI: Return msix_capability_init() failure if populate_msi_sysfs() fails

From: Alexander Gordeev 3.12-stable review patch. If anyone has any objections, please let me know. === commit 2adc7907bac2c72535894732c4b41f9210f9e577 upstream. If populate_msi_sysfs() function failed msix_capability_init() must return the error code, but it returns the success

  1   2   3   4   5   >