Re: [PATCH net v2 1/4] net/core: relax BUILD_BUG_ON in netdev_stats_to_stats64

On Sat, Jan 30, 2016 at 03:26:35PM -0800, David Miller wrote: > From: Jarod Wilson > Date: Sat, 30 Jan 2016 15:53:05 -0500 > > > On Sat, Jan 30, 2016 at 03:39:01PM -0500, Jarod Wilson wrote: > >> Ew, no, it won't work correctly on 32-bit. The for loop is going to copy > >> data

Re: [PATCH 4/4] sigaltstack: allow disabling and re-enabling sas within sighandler

On Sun, Jan 31, 2016 at 9:33 AM, Stas Sergeev wrote: > 31.01.2016 20:00, Andy Lutomirski пишет: >> >> On Sun, Jan 31, 2016 at 8:28 AM, Stas Sergeev wrote: >>> >>> linux implements the sigaltstack() in a way that makes it impossible to >>> use with swapcontext(). Per

Re: [PATCH 4.1 000/127] 4.1.17-stable review

On Thu, Jan 28, 2016 at 09:17:10AM +0100, Ard Biesheuvel wrote: > On 28 January 2016 at 03:14, Guenter Roeck wrote: > > On 01/27/2016 10:12 AM, Greg Kroah-Hartman wrote: > >> > >> - > >> NOTE: > >>There are still a lot of pending stable patches in

Re: [PATCH 4.1 000/127] 4.1.17-stable review

On Wed, Jan 27, 2016 at 06:14:22PM -0800, Guenter Roeck wrote: > On 01/27/2016 10:12 AM, Greg Kroah-Hartman wrote: > >- > >NOTE: > > There are still a lot of pending stable patches in the queue, well > > over 400 of them to be specific, so some of your favorite/pet

[PATCH kernel.org] 4.1 is now maintained by Sasha Levin

From: Greg Kroah-Hartman Sasha has volunteered to maintain the 4.1-longterm kernel for some strange and insane reason. So quick, before he comes to his senses, mark 4.1 as being maintained by him publicly so that the world will know. Cc: Sasha Levin

Re: [PATCH 4/4] sigaltstack: allow disabling and re-enabling sas within sighandler

31.01.2016 22:03, Andy Lutomirski пишет: On Sun, Jan 31, 2016 at 9:33 AM, Stas Sergeev wrote: 31.01.2016 20:00, Andy Lutomirski пишет: On Sun, Jan 31, 2016 at 8:28 AM, Stas Sergeev wrote: linux implements the sigaltstack() in a way that makes it impossible to use

Re: [PATCH 2/2] dax: fix bdev NULL pointer dereferences

On Sun, Jan 31, 2016 at 10:07 AM, Matthew Wilcox wrote: > One option that I've been looking at (primarily for x86-32) is > having an rbtree of PFN ranges that drivers add to when they register > peristent memory. On this specific point we do already have

Re: [Xen-devel] [PATCH v5 09/10] vring: Use the DMA API on Xen

On Sun, Jan 31, 2016 at 12:09 PM, Michael S. Tsirkin wrote: > On Fri, Jan 29, 2016 at 10:34:59AM +, David Vrabel wrote: >> On 29/01/16 02:31, Andy Lutomirski wrote: >> > Signed-off-by: Andy Lutomirski >> > --- >> > drivers/virtio/virtio_ring.c | 12

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

Hi Jesper, On Sun, 31 Jan 2016 19:40:48 +0100 Jesper Dangaard Brouer wrote: > > On Sun, 31 Jan 2016 13:15:06 +1100 > Stephen Rothwell wrote: > > > On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer > > wrote: > > > > > >

Re: PM domain change on unbound devices warning on ipmi_si unload

On Fri, Jan 29, 2016 at 11:45 PM, Rafael J. Wysocki wrote: > On Friday, January 29, 2016 12:56:14 PM Joe Lawrence wrote: >> On 01/29/2016 12:01 PM, Steven Rostedt wrote: >> > On Thu, Jan 28, 2016 at 02:13:04PM -0600, Corey Minyard wrote: >> >> Tomeu, you added that check in >>

Re: [PATCH] staging: rtl8723au: use list_for_each_entry*()

Geliang Tang writes: > Use list_for_each_entry*() instead of list_for_each*() to simplify > the code. Fix coding style by the way. > > Signed-off-by: Geliang Tang > --- > drivers/staging/rtl8723au/core/rtw_ap.c | 166 > --

Re: [PATCH v2 2/2] devicetree: sound: Fix fsl-asoc-card identation

Hi Nicolin, On 29/01/16 18:02, Nicolin Chen wrote: > On Fri, Jan 29, 2016 at 11:01:01AM +, Felipe F. Tonello wrote: >> Signed-off-by: Felipe F. Tonello >> --- >> Documentation/devicetree/bindings/sound/fsl-asoc-card.txt | 2 +- >> 1 file changed, 1 insertion(+), 1

[PATCH 4/4] sigaltstack: allow disabling and re-enabling sas within sighandler

linux implements the sigaltstack() in a way that makes it impossible to use with swapcontext(). Per the man page, sigaltstack is allowed to return EPERM if the process is altering its sigaltstack while running on sigaltstack. This is likely needed to consistently return oss->ss_flags, that

[GIT PULL] TTY/Serial fixes for 4.5-rc2

The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d: Linux 4.5-rc1 (2016-01-24 13:06:47 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-4.5-rc2 for you to fetch changes up to

[GIT PULL] Driver core fixes for 4.5-rc2

The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d: Linux 4.5-rc1 (2016-01-24 13:06:47 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-4.5-rc2 for you to fetch changes up to

Re: [PATCH 4.4 00/67] 4.4.1-stable review

On Wed, Jan 27, 2016 at 07:21:27PM -0800, Guenter Roeck wrote: > On 01/27/2016 06:23 PM, Guenter Roeck wrote: > >On 01/27/2016 10:11 AM, Greg Kroah-Hartman wrote: > >>- > >>NOTE: > >> There are still a lot of pending stable patches in the queue, well > >> over 400 of

Re: Linux 4.4.1

diff --git a/Documentation/ABI/testing/sysfs-bus-usb b/Documentation/ABI/testing/sysfs-bus-usb index 3a4abfc44f5e..136ba17d2da0 100644 --- a/Documentation/ABI/testing/sysfs-bus-usb +++ b/Documentation/ABI/testing/sysfs-bus-usb @@ -134,19 +134,21 @@ Description: enabled for the

Linux 4.3.5

I'm announcing the release of the 4.3.5 kernel. All users of the 4.3 kernel series must upgrade. The updated 4.3.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.3.y and can be browsed at the normal kernel.org git web browser:

Linux 4.1.17

I'm announcing the release of the 4.1.17 kernel. All users of the 4.1 kernel series must upgrade. The updated 4.1.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.1.y and can be browsed at the normal kernel.org git web browser:

mfd: tps65090: set regmap config reg counts properly

Regmap config max_register field should contain number of device last register, however num_reg_defaults_raw field should be set to register count instead (usually one register more than max_register). tps65090 driver had both of these fields set to the same value, fix this by introducing

Re: [PATCH v6 10/22] usb: dwc2: host: Properly set the HFIR

Kever, On Sun, Jan 31, 2016 at 1:23 AM, Kever Yang wrote: > Doug, > > On 01/29/2016 10:20 AM, Douglas Anderson wrote: >> >> According to the most up to date version of the dwc2 databook, the FRINT >> field of the HFIR register should be programmed to: >> * 125 us *

Re: [PATCH 2/4] dmi: Add a DMI firmware node and handling

On Fri, Jan 29, 2016 at 2:43 PM, wrote: > From: Corey Minyard > > This is so that an IPMI platform device can be created from a > DMI firmware entry. This doesn't apply for me. What's it based on? --Andy

Re: [PATCH 4/4] sigaltstack: allow disabling and re-enabling sas within sighandler

On Sun, Jan 31, 2016 at 2:36 PM, Stas Sergeev wrote: > 31.01.2016 23:11, Andy Lutomirski пишет: >> >> On Sun, Jan 31, 2016 at 12:08 PM, Stas Sergeev wrote: >>> >>> 31.01.2016 22:03, Andy Lutomirski пишет: Also, consider a use case like yours but with *two*

Re: [PATCH] ACPI: Do not report _OSI("Darwin") when acpi_osi=!Darwin provided

-when-acpi_osi-Darwin-provided/20160131-224855 base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next config: arm64-allyesconfig (attached as .config) reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O

[PATCH] net: smc91x: propagate irq return code

The smc91x driver doesn't honor the probe deferral mechanism when the interrupt source is not yet available, such as one provided by a gpio controller not probed. Fix this by propagating the platform_get_irq() error code as the probe return value. Signed-off-by: Robert Jarzmik

Re: [PATCH 4/4] sigaltstack: allow disabling and re-enabling sas within sighandler

01.02.2016 01:44, Andy Lutomirski пишет: On Sun, Jan 31, 2016 at 2:36 PM, Stas Sergeev wrote: 31.01.2016 23:11, Andy Lutomirski пишет: On Sun, Jan 31, 2016 at 12:08 PM, Stas Sergeev wrote: 31.01.2016 22:03, Andy Lutomirski пишет: Also, consider a use case like

Re: [PATCH RFC 10/11] clk: sunxi: rewrite sun6i-ar100 using factors clk

On Mon, Jan 25, 2016 at 8:15 AM, Chen-Yu Tsai wrote: > sun6i's AR100 clock is a classic factors clk case: > > AR100 = ((parent mux) >> p) / (m + 1) > > Signed-off-by: Chen-Yu Tsai This patch adds a ".remove" function to a driver that is controlled by a bool

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

On Sun, 31 Jan 2016 13:15:06 +1100 Stephen Rothwell wrote: > Hi Jesper, > > On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer > wrote: > > > > Let me know, if the linux-next tree need's an explicit fix? > > It would be a good idea if you

Re: [PATCH 4/4] sigaltstack: allow disabling and re-enabling sas within sighandler

31.01.2016 23:11, Andy Lutomirski пишет: On Sun, Jan 31, 2016 at 12:08 PM, Stas Sergeev wrote: 31.01.2016 22:03, Andy Lutomirski пишет: Also, consider a use case like yours but with *two* contexts that use their own altstack. If you go to context A, enable sigaltstack, get a

[RESEND PATCH] vfio: Enable VFIO device for powerpc

ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is used to handle any necessary interactions between KVM and VFIO. Currently that device is built on x86 and ARM, but not powerpc, although powerpc does support both KVM and VFIO. This makes things awkward in userspace

Re: [PATCH 3/4] x86: signal: unify the sigaltstack check with other arches

On Sun, Jan 31, 2016 at 8:24 AM, Stas Sergeev wrote: > > Currently x86's get_sigframe() checks for "current->sas_ss_size" > to determine whether there is a need to switch to sigaltstack. > The common practice used by all other arches is to check for > sas_ss_flags(sp) == 0 > > This

Re: [PATCH 3/5] HSI: ssi-protocol: export modem info via sysfs

On Sun 2016-01-31 02:19:45, Sebastian Reichel wrote: > Currently userspace knows about the rapuyama version by > checking, which gpios have been exported. This does no > longer work with kernel based power management, so export > a sysfs file, which provides the rapuyama generation. Also Umm. So

Re: [PATCH 2/5] HSI: nokia-modem: kernel based PM

Hi, On Sun, Jan 31, 2016 at 06:29:48PM +0100, Pavel Machek wrote: > > So far power management had to be done in uerspace using exported > > "userspace" Right, thanks. > > This patch adds kernel based power management, which will bind the > > modem's power state to the state of the phonet

[PATCH] tools build: use .s extension for preprocessed assembler code

The "man gcc" says .i extension represents the file is C source code that should not be preprocessed. Here, .s should be used. For clarification, .c ---(preprocess)---> .i .S ---(preprocess)---> .s Signed-off-by: Masahiro Yamada ---

Re: [PATCH 2/2] dax: fix bdev NULL pointer dereferences

On Sun, Jan 31, 2016 at 10:27 AM, Matthew Wilcox wrote: > On Sun, Jan 31, 2016 at 10:18:46AM -0800, Dan Williams wrote: >> On Sun, Jan 31, 2016 at 10:07 AM, Matthew Wilcox >> wrote: >> > Yes. This is just the default implementation of dax_map_pfn()

[PATCH v2 0/4] make sigaltstack() compatible with swapcontext()

The following patches add the self-test for sigaltstack(SS_DISABLE) inside the signal handler, and allow an app to temporarily disable and re-enable the sigaltstack within a sighandler. This is needed to make sigaltstack() compatible with swapcontext(): before using swapcontext() inside the

Re: [PATCH v5 00/10] virtio DMA API, yet again

On Fri, Jan 29, 2016 at 11:01:00AM +, David Woodhouse wrote: > Also, wasn't Christoph looking at making per-device DMA ops more > generic instead of an 'archdata' thing on basically every platform? Or > did I just imagine that part? What I've done for 4.5 is to switch all architectures to use

[GIT PULL] libnvdimm-fixes for 4.5-rc2

Hi Linus, please pull from:   git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes 1/ Fixes to the libnvdimm 'pfn' device that establishes a reserved area for storing a struct page array. 2/ Fixes for dax operations on a raw block device to prevent pagecache collisions

Re: [PATCH 4/4] sigaltstack: allow disabling and re-enabling sas within sighandler

On Sun, Jan 31, 2016 at 12:08 PM, Stas Sergeev wrote: > 31.01.2016 22:03, Andy Lutomirski пишет: >> Also, consider a use case like yours but with *two* contexts that use >> their own altstack. If you go to context A, enable sigaltstack, get a >> signal, temporarily disable, then

Re: [Xen-devel] [PATCH v5 09/10] vring: Use the DMA API on Xen

On Fri, Jan 29, 2016 at 10:34:59AM +, David Vrabel wrote: > On 29/01/16 02:31, Andy Lutomirski wrote: > > Signed-off-by: Andy Lutomirski > > --- > > drivers/virtio/virtio_ring.c | 12 > > 1 file changed, 12 insertions(+) > > > > diff --git

Re: [PATCH 00/14] USB: serial: Fix coccinelle warnings

On Sat, Jan 30, 2016 at 06:44:33PM +0100, Mathieu OTHACEHE wrote: > This series of patches fixes all coccinelle warnings in > USB serial subsystem > > Mathieu OTHACEHE (14): > USB: serial: safe_serial: fix assignment of bool to 0/1 > USB: serial: safe_serial: fix assignment of bool to non 0/1

Re: [PATCH 0/3] x86/entry/64: Fixes for syscall rework

On Sun, Jan 31, 2016 at 09:33:25AM -0800, Andy Lutomirski wrote: > I broke iopl(2) with my syscall rework. Fix it up. While debugging > it, I found a bug in my IRQ state handling. Fix that, too. > > Andy Lutomirski (3): > x86/entry/64: Fix an IRQ state error on ptregs-using syscalls >

Re: [PATCH v2] locktorture: Fix NULL pointer when torture_type is invalid

On Sat, 30 Jan 2016, Paul E. McKenney wrote: On 2016/1/28 12:25, Kefeng Wang wrote: > Insmod locktorture with torture_type=mutex will lead to crash, You actually want mutex_lock here, we always use the _lock suffix, mainly because it all started out with spin_lock. And you just showed how

Re: [PATCH v2] gpio: Add driver for TI TPIC2810

On Thu, Jan 28, 2016 at 4:56 PM, Andrew F. Davis wrote: > On 01/28/2016 04:47 AM, Linus Walleij wrote: >> So the TI datasheet says: >> "8 bit LED driver with I2C interface" >> >> So it is *not* "general purpose input/output" (GPIO). >> >> It is special purpose LED drive output-only

Re: Linux 4.3.5

On Sun, Jan 31, 2016 at 02:01:28PM -0800, Linus Torvalds wrote: > On Sun, Jan 31, 2016 at 11:33 AM, Greg KH wrote: > > I'm announcing the release of the 4.3.5 kernel. > > > > All users of the 4.3 kernel series must upgrade. > > Hmm. I may be missing something, but

Re: [PATCH 4/4] sigaltstack: allow disabling and re-enabling sas within sighandler

31.01.2016 20:00, Andy Lutomirski пишет: On Sun, Jan 31, 2016 at 8:28 AM, Stas Sergeev wrote: linux implements the sigaltstack() in a way that makes it impossible to use with swapcontext(). Per the man page, sigaltstack is allowed to return EPERM if the process is altering its

[PATCH 3/3] x86/syscalls/64: Mark sys_iopl as using ptregs

sys_iopl both reads and writes pt_regs->flags. Mark it as using ptregs. This isn't strictly necessary, as pt_regs->flags is available even in the fast path, but this is very lightweight now that we have syscall qualifiers and it could avoid some pain down the road. Signed-off-by: Andy

[PATCH 1/3] x86/entry/64: Fix an IRQ state error on ptregs-using syscalls

I messed up the IRQ state when jumping off the fast path due to invocation of a ptregs-using syscall. This bug shouldn't have had any impact yet, but it would have caused problems with subsequent context tracking cleanups. Fixes: 1e423bff959e x86/entry/64: ("Migrate the 64-bit syscall slow path

[PATCH 0/3] x86/entry/64: Fixes for syscall rework

I broke iopl(2) with my syscall rework. Fix it up. While debugging it, I found a bug in my IRQ state handling. Fix that, too. Andy Lutomirski (3): x86/entry/64: Fix an IRQ state error on ptregs-using syscalls x86/entry/64: Fix fast-path syscall return register state x86/syscalls/64: Mark

[PATCH 2/3] x86/entry/64: Fix fast-path syscall return register state

I was fishing RIP (i.e. RCX) out of pt_regs->cx and RFLAGS (i.e. R11) out of pt_regs->r11. While it usually worked (pt_regs started out with cx == ip and r11 == flags), it was very fragile. In particular, it broke iopl because iopl forgot to mark itself as using ptregs. Undo that part of the

[PATCH] selftests/cgroupns: new test for cgroup namespaces

kinvolk.io> Acked-by: Serge E. Hallyn <serge.hal...@ubuntu.com> --- Changelog: 20160131 - rebase on sergeh/cgroupns.v10 and fix conflicts 20160115 - Detect where cgroup2 is mounted, don't assume /sys/fs/cgroup (suggested by sergeh) - Chec

[PATCH 2/4] score: signal: fix sigaltstack check

Currently get_sigframe() checks only (ka->sa.sa_flags & SA_ONSTACK) && (!on_sig_stack(sp)) to determine whether the switch to sigaltstack is needed. It forgets to checks whether the sigaltstack was previously set. This patch replaces the !on_sig_stack(sp) with the standard check

[PATCH 3/4] x86: signal: unify the sigaltstack check with other arches

Currently x86's get_sigframe() checks for "current->sas_ss_size" to determine whether there is a need to switch to sigaltstack. The common practice used by all other arches is to check for sas_ss_flags(sp) == 0 This patch makes the code consistent with other arches and also allows for the

Re: [PATCH 3.14 30/59] xhci: refuse loading if nousb is used

On Thu, Jan 28, 2016 at 05:57:35PM +, Luis Henriques wrote: > On Wed, Jan 27, 2016 at 10:15:18AM -0800, Greg Kroah-Hartman wrote: > > 3.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Oliver Neukum > > >

mfd: rc5t583: set regmap config reg counts properly

Regmap config max_register field should contain number of device last register, however num_reg_defaults_raw field should be set to register count instead (usually one register more than max_register). rc5t583 driver had both of these fields set to the same value, fix this by introducing separate

mfd: as3711: set regmap config reg counts properly

Regmap config max_register field should contain number of device last register, however num_reg_defaults_raw field should be set to register count instead (usually one register more than max_register). as3711 driver had both of these fields set to the same value, fix this by introducing separate

Re: [PATCH 4/4] sigaltstack: allow disabling and re-enabling sas within sighandler

On Sun, Jan 31, 2016 at 8:28 AM, Stas Sergeev wrote: > > linux implements the sigaltstack() in a way that makes it impossible to > use with swapcontext(). Per the man page, sigaltstack is allowed to return > EPERM if the process is altering its sigaltstack while running on >

Re: [PATCH 2/5] HSI: nokia-modem: kernel based PM

Hi! > So far power management had to be done in uerspace using exported "userspace" > This patch adds kernel based power management, which will bind the > modem's power state to the state of the phonet network interface. Ok, so I have ofonod that already does power management in userspace.

Re: [PATCH 2/2] dax: fix bdev NULL pointer dereferences

On Sun, Jan 31, 2016 at 08:38:20AM -0800, Dan Williams wrote: > On Sun, Jan 31, 2016 at 2:55 AM, Matthew Wilcox wrote: > > On Sat, Jan 30, 2016 at 11:12:12PM -0700, Ross Zwisler wrote: > >> Is there a reason to store pnfs instead of kaddrs in the radix tree? > > > > Once

Re: [PATCH 2/2] dax: fix bdev NULL pointer dereferences

On Sun, Jan 31, 2016 at 10:18:46AM -0800, Dan Williams wrote: > On Sun, Jan 31, 2016 at 10:07 AM, Matthew Wilcox > wrote: > > Yes. This is just the default implementation of dax_map_pfn() which works > > for most situations. We can introduce more complex implementations

Re: [Xen-devel] [PATCH v5 09/10] vring: Use the DMA API on Xen

On Sun, Jan 31, 2016 at 12:18 PM, Michael S. Tsirkin wrote: > On Sun, Jan 31, 2016 at 12:13:58PM -0800, Andy Lutomirski wrote: >> On Sun, Jan 31, 2016 at 12:09 PM, Michael S. Tsirkin wrote: >> > On Fri, Jan 29, 2016 at 10:34:59AM +, David Vrabel wrote: >> >>

Re: [PATCH v2] USB: option: add support for SIM7100E

On Sun, Jan 31, 2016 at 09:13:19PM +0100, Johan Hovold wrote: > On Fri, Jan 29, 2016 at 12:07:30AM +0300, Andrey Skvortsov wrote: > > $ lsusb: > > Bus 001 Device 101: ID 1e0e:9001 Qualcomm / Option > > > > $ usb-devices: > > T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=101 Spd=480 MxCh= 0 > >

Re: Linux 4.3.5

On Sun, Jan 31, 2016 at 11:33 AM, Greg KH wrote: > I'm announcing the release of the 4.3.5 kernel. > > All users of the 4.3 kernel series must upgrade. Hmm. I may be missing something, but this still doesn't seem to have commit 23688bf4f830 ("block: ensure to split

Re: [PATCH v2 3/3] vfs: Enable list batching for the superblock's inode list

On Fri, Jan 29, 2016 at 02:30:46PM -0500, Waiman Long wrote: > The inode_sb_list_add() and inode_sb_list_del() functions in the vfs > layer just perform list addition and deletion under lock. So they can > use the new list batching facility to speed up the list operations > when many CPUs are

Re: [PATCH] mac80211: fix memory leak

Hi Sudip, On Fri, Jan 29, 2016 at 8:49 PM, Sudip Mukherjee wrote: > On error we jumped to the error label and returned the error code but we > missed releasing sinfo. > > Signed-off-by: Sudip Mukherjee Should the From: and Signed-off-by: email

Re: [PATCHv3 1/3] rdmacg: Added rdma cgroup controller.

Hi Doug, Liran, Jason, How would you like to see RDMA verb resources being defined - in RDMA cgroup or in IB stack? In current patch v5, its defined by the IB stack which is often shipped as different package due to high amount of changes, bug fixes, features. In v0 patch it was defined by the

Re: [RFC][PATCH] seccomp: add SECCOMP_RET_ACK for non-fatal SIGSYS

On Jan 28, 2016 6:33 PM, "Andy Lutomirski" wrote: > > On Thu, Jan 28, 2016 at 5:06 PM, Kees Cook wrote: > > Tracing processes for syscall usage can be done one step at a time with > > SECCOMP_RET_TRAP, but this will block the syscall. Alternatively,

Re: [Xen-devel] [PATCH v5 09/10] vring: Use the DMA API on Xen

On Sun, Jan 31, 2016 at 12:13:58PM -0800, Andy Lutomirski wrote: > On Sun, Jan 31, 2016 at 12:09 PM, Michael S. Tsirkin wrote: > > On Fri, Jan 29, 2016 at 10:34:59AM +, David Vrabel wrote: > >> On 29/01/16 02:31, Andy Lutomirski wrote: > >> > Signed-off-by: Andy Lutomirski

Re: [PATCH 2/2] dax: fix bdev NULL pointer dereferences

On Sun, Jan 31, 2016 at 10:07 AM, Matthew Wilcox wrote: > On Sun, Jan 31, 2016 at 08:38:20AM -0800, Dan Williams wrote: >> On Sun, Jan 31, 2016 at 2:55 AM, Matthew Wilcox >> wrote: >> > On Sat, Jan 30, 2016 at 11:12:12PM -0700, Ross Zwisler wrote:

[GIT PULL] Staging driver fixes for 4.5-rc2

The following changes since commit 9f9499ae8e6415cefc4fe0a96ad0e27864353c89: Linux 4.4-rc5 (2015-12-13 17:42:58 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.5-rc2 for you to fetch changes up to

[GIT PULL] USB driver fixes for 4.5-rc2

The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d: Linux 4.5-rc1 (2016-01-24 13:06:47 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.5-rc2 for you to fetch changes up to

Re: [PATCH v5 00/10] virtio DMA API, yet again

On Thu, Jan 28, 2016 at 06:31:13PM -0800, Andy Lutomirski wrote: > This switches virtio to use the DMA API on Xen and if requested by > module option. > > This fixes virtio on Xen, and it should break anything because it's > off by default on everything except Xen PV on x86. > > To the Xen

Re: [PATCH v2] USB: option: add support for SIM7100E

On Fri, Jan 29, 2016 at 12:07:30AM +0300, Andrey Skvortsov wrote: > $ lsusb: > Bus 001 Device 101: ID 1e0e:9001 Qualcomm / Option > > $ usb-devices: > T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=101 Spd=480 MxCh= 0 > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 2 > P:

[PATCH] ARM: pxa: fix irq initialization for pxa3xx devicetree

The initialization of interrupt controller for devicetree platform was done for pxa2xx platforms, but not for pxa3xx ones. Fix this my adding the missing initialization call. Fixes: 089d03629b04 ("ARM: pxa: add devicetree code for irq handling") Signed-off-by: Robert Jarzmik

Re: [PATCH 3/4] x86: signal: unify the sigaltstack check with other arches

31.01.2016 19:58, Andy Lutomirski пишет: On Sun, Jan 31, 2016 at 8:24 AM, Stas Sergeev wrote: Currently x86's get_sigframe() checks for "current->sas_ss_size" to determine whether there is a need to switch to sigaltstack. The common practice used by all other arches is to check

Re: [PATCH 3/5] HSI: ssi-protocol: export modem info via sysfs

Hi Pavel, On Sun, Jan 31, 2016 at 06:36:05PM +0100, Pavel Machek wrote: > On Sun 2016-01-31 02:19:45, Sebastian Reichel wrote: > > Currently userspace knows about the rapuyama version by > > checking, which gpios have been exported. This does no > > longer work with kernel based power management,

[PATCH 1/4] selftests: Add test for sigaltstack(SS_DISABLE) inside sighandler

sigaltstack needs to be disabled before the signal handler can safely use swapcontext(). Unfortunately linux implementation of sigaltstack() returns EPERM in that case. Re-enabling is also needed and tested. CC: Shuah Khan CC: linux-kernel@vger.kernel.org CC:

Linux 4.4.1

I'm announcing the release of the 4.4.1 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Re: [PATCH v5 00/10] virtio DMA API, yet again

On Sun, Jan 31, 2016 at 12:12 PM, Michael S. Tsirkin wrote: > On Thu, Jan 28, 2016 at 06:31:13PM -0800, Andy Lutomirski wrote: >> This switches virtio to use the DMA API on Xen and if requested by >> module option. >> >> This fixes virtio on Xen, and it should break anything

Re: [PATCH 11/14] USB: serial: mos7840: move constants to right

Mathieu OTHACEHE writes: > This patch fixes the following coccinelle warnings: > > drivers/usb/serial/mos7840.c:2042:4-10: Move constant to right. > drivers/usb/serial/mos7840.c:2062:16-22: Move constant to right. > > Signed-off-by: Mathieu OTHACEHE >

Re: [PATCH v6 18/22] usb: dwc2: host: Schedule periodic right away if it's time

Kever, On Sun, Jan 31, 2016 at 1:36 AM, Kever Yang wrote: > Doug, > > > On 01/29/2016 10:20 AM, Douglas Anderson wrote: >> >> In dwc2_hcd_qh_deactivate() we will put some things on the >> periodic_sched_ready list. These things won't be taken off the ready >> list

URGENT DECENT LOAN OFFER

-- Email chryslerfina...@hotmail.com and get a decent loan.

Re: [PATCH 2/2] dax: fix bdev NULL pointer dereferences

On Fri, Jan 29, 2016 at 04:34:30PM -0700, Ross Zwisler wrote: > On Fri, Jan 29, 2016 at 11:28:15AM -0700, Ross Zwisler wrote: > > On Thu, Jan 28, 2016 at 01:38:58PM -0800, Christoph Hellwig wrote: > > > On Thu, Jan 28, 2016 at 12:35:04PM -0700, Ross Zwisler wrote: > > > > There are a number of

Re: [PATCH RESEND v2 4/4] ARM: dts: enable audio clock support for Cygnus

Le 29/01/2016 16:42, Ray Jui a écrit : > Hi Florian, > > With Stephen merging the first 3 patches into the clk tree, could you > please take this DT patch now? > > Thanks, > > Ray > > On 1/26/2016 5:18 PM, Ray Jui wrote: >> From: Simran Rai >> >> Add audio clock to the

[lkp] [gpio] 1b06d64f73: kmsg.dio-#e#-dio-#e:Unable_to_lock#-dio-#e_port_addresses(#-#)

FYI, we noticed the below changes on https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git devel commit 1b06d64f73746c30ddba43bb57c30ba9a126f53b ("gpio: Add GPIO support for the ACCES 104-DIO-48E") With your commit, there are the following new messages in kernel log. [

[PATCH v2] Race between cat /proc/kallsyms and rmmod

Iterating code of /proc/kallsyms calls module_get_kallsym() which grabs and drops module_mutex internally and returns "struct module *", module is removed, aforementioned "struct module *" is used in non-trivial way. So, grab module_mutex for entire operation like /proc/modules does. Steps to

linux-next: manual merge of the dt-rh tree with the qcom tree

Hi Rob, Today's linux-next merge of the dt-rh tree got a conflict in: MAINTAINERS between commit: 43ed2986476d ("MAINTAINERS: add qcom i2c and spi drivers to list") from the qcom tree and commit: e68d7c143a62 ("MAINTAINERS: Add missing platform maintainers for dts files") from the

Re: [PATCH V2 1/4] mfd: f81504-core: Add Fintek F81504/508/512 PCIE-to-UART/GPIO core support

Hi Andy, Andy Shevchenko 於 2016/1/29 下午 09:41 寫道: On Fri, 2016-01-29 at 13:50 +0800, Peter Hung wrote: Andy Shevchenko 於 2016/1/28 下午 07:55 寫道: I would suggest to rearrange definition block here (and in the rest of the functions in entire series) to somehow follow the following pattern 1)

Re: [PATCH 0/3] ACPI: parse the SPCR table

On 01/27/2016 08:45 AM, One Thousand Gnomes wrote: > On Wed, 27 Jan 2016 15:17:52 +0300 > Aleksey Makarov wrote: > >> On 01/25/2016 07:11 PM, Peter Hurley wrote: >>> On 01/25/2016 03:45 AM, Aleksey Makarov wrote: This patchset is based on the patchset by Leif

Re: [RFC PATCH 00/19] cpufreq locking cleanups and documentation

On 29-01-16, 16:57, Saravana Kannan wrote: > I haven't looked at the cpufreq-tests, but I doubt they do hotplug testing > where they remove all the CPUs of a policy (to trigger a policy exit). They do. -- viresh

linux-next: Tree for Feb 1

Hi all, Changes since 20160129: The dt-rh tree gained a conflict against the qcom tree. The rcu tree gained a build failure so I used the version from next-20160129. The staging tree gained conflicts against the staging.current and tty trees. The gpio tree still had its build failure so I

[RESEND][PATCH v5 2/3] spi: spi-ti-qspi: add mmap mode read support

ti-qspi controller provides mmap port to read data from SPI flashes. mmap port is enabled in QSPI_SPI_SWITCH_REG. ctrl module register may also need to be accessed for some SoCs. The QSPI_SPI_SETUP_REGx needs to be populated with flash specific information like read opcode, read mode(quad, dual,

[RESEND][PATCH v5 1/3] spi: introduce accelerated read support for spi flash devices

In addition to providing direct access to SPI bus, some spi controller hardwares (like ti-qspi) provide special port (like memory mapped port) that are optimized to improve SPI flash read performance. This means the controller can automatically send the SPI signals required to read data from the

Re: [PATCH] staging: rtl8192u: Fix block comments use * on subsequent lines in r8192U_wx.c

On Mon, 1 Feb 2016, Byeoungwook Kim wrote: > clean up checkpatch warning: > WARNING: Block comments use * on subsequent lines > > Signed-off-by: Byeoungwook Kim > --- > drivers/staging/rtl8192u/r8192U_wx.c | 38 > +++- > 1 file changed,

and NTP incompatibility (MOD_NANO)

Hi folks! I'd wish ntp_loopfilter.c would compile without problems. The mess is (I had fixed it about 15 years ago (keyword "PPSkit")) that Linux uses ADJ_* flags to do traditional adjtime() things, as well as NTP kernel-related things (That's why the Linux syscall is named adjtimex()). NTP

Re: [PATCHv3 1/1] staging/ion: Add support to get ion handle from dma buf

Kindly review the patch. Patchv2 had refcount issue which is fixed here. On Tue, 12 Jan 2016 09:31:46 +0530 Rohit kumar wrote: > Currently we can only import dma buf fd's to get ion_handle. > Adding support to import dma buf handles to support kernel > specific use cases.

[PATCH v3] android: binder: Sanity check at binder ioctl

Sanity check at binder ioctl function, Only allow the shared mm_struct to use the same binder-object to do binder operate. And add proc->vma_vm_mm = current->mm at the open function. The libbinder do ioctl before mmap called. V2: Fix compile error for error commit V3: Change the condition to

Re: [PATCH v2 2/2] phy: add a driver for the Rockchip SoC internal eMMC PHY

On Monday 25 January 2016 01:19 PM, Shawn Lin wrote: > Hello Kishon, > > Any changce to apply this patch? :) back from vacation. Will review it this week. Sorry for the delay. Thanks Kishon > > On 2016/1/5 9:08, Shawn Lin wrote: >> This patch to add a generic PHY driver for ROCKCHIP eMMC

Re: [PATCH v4 9/9] ARM: dts: rockchip: support the spi for rk3036

Heiko, 在 2016年01月31日 19:06, Heiko Stuebner 写道: Hi Caesar, Am Donnerstag, 28. Januar 2016, 16:43:38 schrieb Caesar Wang: [...] memory { @@ -485,6 +486,23 @@ status = "disabled"; }; + spi: spi@20074000 { + compatible =

[PATCH] [dm]fix NULL pointer in dm_exception_store_create() when create dm device

In some conditions(such as umount fs failed),origin path or origin bdev or both of the two is same as cow's.If this happens, origin dev will be freed when get cow dev in function "dm_get_device" , then "s->origin->dev" which used by "dm_exception_store_create" will be a NULL pointer.

  1   2   3   4   5   6   >