With commit ff36ab345 ("dm: remove request-based logic from
make_request_fn wrapper") DM no longer calls blk_queue_bio() directly,
so remove its export. Doing so required a forward declaration in
blk-core.c.
Signed-off-by: Mike Snitzer
---
block/blk-core.c | 5 +++--
> There are several things in that queue; most of it is fs/namei.c
> rewrite and closer to the end we get
> * non-recursive link_path_walk()
> * the only symlink-related limitation is that there should be no
> more than 40 symlinks traversals, no matter how nested they are.
>
From: Al Viro
when we go for on-demand allocation of saved state in
link_path_walk(), we'll want nameidata to stay around
for all 3 calls of path_mountpoint().
Signed-off-by: Al Viro
---
fs/namei.c | 28 +---
1 file changed, 13 insertions(+), 15 deletions(-)
diff
k2e netcp range size is 16M (0x100) and not 0xff. This patch fixes
this. Similarly fix the size of switch module register space to 0x2.
Signed-off-by: Murali Karicheri
---
arch/arm/boot/dts/k2e-netcp.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Al Viro
Signed-off-by: Al Viro
---
fs/9p/vfs_inode.c | 26 +-
1 file changed, 5 insertions(+), 21 deletions(-)
diff --git a/fs/9p/vfs_inode.c b/fs/9p/vfs_inode.c
index 703342e..cda68f7 100644
--- a/fs/9p/vfs_inode.c
+++ b/fs/9p/vfs_inode.c
@@ -1370,6 +1370,8 @@
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 118c855b5623f3e2e6204f02623d88c09e0c34de upstream.
The 3w-9xxx driver needs to tear down the dma mappings before returning
the command to the midlayer, as there is no
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 9cd9554615cba14f0877cc9972a6537ad2bdde61 upstream.
The 3w- driver needs to tear down the dma mappings before returning
the command to the midlayer, as there is no
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 579d69bc1fd56d5af5761969aa529d1d1c188300 upstream.
The 3w-sas driver needs to tear down the dma mappings before returning
the command to the midlayer, as there is no
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit 309be239369609929d5d3833ee043f7c5afc95d1 upstream.
Make sure we're using the new macro, so our
resume signaling will always pass certification.
Based on original work by
There are few fixes required in the dt bindings for netcp driver to
make the reg and range sizes to match with data sheet. Also fix the
typical size error (last bit 1 instead of 0). Please apply this for
to next branch for v4.2.
Thanks
Murali Karicheri (3):
ARM: dts: k2hk: fix the netcp range
On 05/08/2015 04:09 PM, Darren Hart wrote:
> The futextest testsuite [1] provides functional, stress, and
> performance tests for the various futex op codes. Those tests will be of
> more use to futex developers if they are included with the kernel
> source.
>
> Copy the core infrastructure and
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit d02260824e2cad626fb2a9d62e27006d34b6dedc upstream.
Some models provide too long string for the shortname that has 32bytes
including the terminator, and it results in a
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit cd17e02ff4db58ec32d35cf331c705d295779930 upstream.
Seems to have problems with high mclks.
bug:
https://bugs.freedesktop.org/show_bug.cgi?id=76490
Signed-off-by: Alex
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Lukas Czerner
commit d2dc317d564a46dfc683978a2e5a4f91434e9711 upstream.
Currently it is possible to lose whole file system block worth of data
when we hit the specific interaction with
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit 84c0d178eb9f3a3ae4d63dc97a440266cf17f7f5 upstream.
Make sure we're using the new macro, so our
resume signaling will always pass certification.
Signed-off-by: Felipe
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sudip Mukherjee
commit 2c20d92dad5db6440cfa88d811b69fd605240ce4 upstream.
the lcd type as defined in the Kconfig is not matching in the code.
as a result the rs, rw and en pins were getting
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "K. Y. Srinivasan"
commit 73cffdb65e679b98893f484063462c045adcf212 upstream.
Don't wait after sending request for offers to the host. This wait is
unnecessary and simply adds 5 seconds to the
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andrzej Pietrasiewicz
commit eb132ccbdec5df46e29c9814adf76075ce83576b upstream.
Function-specific setup requests should be handled in such a way, that
apart from filling in the data buffer,
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 07b0e5d49d227e3950cb13a3e8caf248ef2a310e upstream.
The emux-synth driver has a possible AB/BA mutex deadlock at unloading
the emu10k1 driver:
snd_emux_free() ->
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit ea16328f80ca8d74434352157f37ef60e2f55ce2 upstream.
Make sure we're using the new macro, so our
resume signaling will always pass certification.
Signed-off-by: Felipe
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit ad774702f1705c04e5fa492b793d8d477a504fa6 upstream.
The commit c2be45f09bb0 ("compal-laptop: Use
devm_hwmon_device_register_with_groups") wanted to change the
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: hujianyang
commit 9aa272b492e7551a9ee0e2c83c720ea013698485 upstream.
Running mtd-utils/tests/ubi-tests/io_basic.c could cause
soft lockup or watchdog reset. It is because *updatevol*
will
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 1c94e65c668f44d2c69ae7e7fc268ab3268fba3e upstream.
The OSS emulation in synth-emux helper has a potential AB/BA deadlock
at the simultaneous closing and opening:
close
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Vineet Gupta
commit e4140819dadc3624accac8294881bca8a3cba4ed upstream.
A malicious signal handler / restorer can DOS the system by fudging the
user regs saved on stack, causing weird things
On Mon, 11 May 2015 19:33:06 +0200
Frederic Weisbecker wrote:
> On Mon, May 11, 2015 at 10:27:44AM -0700, Andrew Morton wrote:
> > On Mon, 11 May 2015 10:19:16 -0700 "Paul E. McKenney"
> > wrote:
> >
> > > On Mon, May 11, 2015 at 08:57:59AM -0400, Steven Rostedt wrote:
> > > >
> > > >
To be consistent with the queued spinlocks which use
CONFIG_QUEUED_SPINLOCKS config parameter, the one for the queued
rwlocks is now renamed to CONFIG_QUEUED_RWLOCKS.
Signed-off-by: Waiman Long
---
arch/x86/Kconfig |2 +-
kernel/Kconfig.locks |6 +++---
On 05/11/15 08:15, Yaniv Gardi wrote:
> Since ARCH_MSM is no longer supported as configuration definition,
> it should be modified into ARCH_QCOM in order to add support for
> Qualcomm platforms.
>
> Signed-off-by: Yaniv Gardi
>
> ---
I've already sent this patch[1]. Can you please ack it?
[1]
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Michal Simek
commit 6befa9d883385c580369a2cc9e53fbf329771f6d upstream.
Do not probe all serial drivers by of_serial.c which are using
device_type = "serial"; property. Only drivers which have
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zubaj
commit 7241ea558c6715501e777396b5fc312c372e11d9 upstream.
Looks like audigy emu10k2 (probably emu10k1 - sb live too) support two
modes for DMA. Second mode is useful for 64 bit os
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit a134f083e79fb4c3d0a925691e732c56911b4326 ]
If we don't do that, then the poison value is left in the ->pprev
backlink.
This can cause crashes if we do a
This is the start of the stable review cycle for the 3.14.42 release.
There are 25 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 Wed May 13 17:54:40 UTC 2015.
Anything
Hi Javier,
Am Samstag, 9. Mai 2015, 12:10:31 schrieb Javier Martinez Canillas:
> Newer Chromebooks have more than one Embedded Controller (EC) in the
> system. These additional ECs are connected through I2C with a host EC
> which is the one that is connected to the Application Processor (AP)
>
With both gcc 4.7.2 and 4.9.2, sometimes gcc mysteriously doesn't inline
very small functions we expect to be inlined. In particular,
with this config: http://busybox.net/~vda/kernel_config
there are more than a thousand copies of tiny spinlock-related functions:
$ nm --size-sort vmlinux | grep
On 05/11/15 08:15, Yaniv Gardi wrote:
> Since ARCH_MSM is no longer supported as configuration definition,
> it should be modified into ARCH_QCOM in order to add support for
> Qualcomm platforms.
>
> Signed-off-by: Yaniv Gardi
>
> ---
I've already sent this patch[1]. Can you please ack it?
[1]
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit d02260824e2cad626fb2a9d62e27006d34b6dedc upstream.
Some models provide too long string for the shortname that has 32bytes
including the terminator, and it results in a
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Charles Keepax
commit a2d97723cb3a7741af81868427b36bba274b681b upstream.
Correct small copy and paste error where autodisable was not being
enabled for the SOC_DAPM_SINGLE_TLV_AUTODISABLE
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit 8e779c6c4a398763c21371fe40f649206041dc1e upstream.
Testing has shown that ASM1053 devices do not work properly with transfers
larger than 240 sectors, so set max_sectors
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Davide Italiano
commit 280227a75b56ab5d35854f3a77ef74a7ad56a203 upstream.
fallocate() checks that the file is extent-based and returns
EOPNOTSUPP in case is not. Other tasks can convert from
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Lukas Czerner
commit d2dc317d564a46dfc683978a2e5a4f91434e9711 upstream.
Currently it is possible to lose whole file system block worth of data
when we hit the specific interaction with
On 11.05.2015 19:48, Okash Khawaja wrote:
>> On 11 May 2015, at 14:24, Jonas Gorski wrote:
>>
>> Hi,
>>
>>> On Mon, May 11, 2015 at 12:38 PM, Kalle Valo wrote:
>>> Okash Khawaja writes:
>>>
Sure, I'll create v2 of the patch with updated commit log.
Since it's part of a patch set,
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit ee136af4a064c2f61e2025873584d2c7ec93f4ae upstream.
The usb-storage driver sets max_sectors = 240 in its scsi-host template,
for uas we do not want to do that for all
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit a5011d44f0e1117a6db14b19b57c51f8be5673a0 upstream.
uas_use_uas_driver may set some US_FL_foo flags during detection, currently
these are stored in a local variable and
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Lars Persson
Commit 5b9593f3bccb9904f260f9ad7f184e1d2921bd1e upstream.
Revert commit 2a4a8b1e5d9d ("MIPS: Remove race window in page fault
handling") because it increased the number of
4.0-stable review patch. If anyone has any objections, please let me know.
--
Commit 9eaffa84a8a46adab065c983401fc9d5949c958f upstream.
For a discussion, see http://patchwork.linux-mips.org/patch/9539/.
This reverts commit 625c0a21700bdb90844d926a1508a17a77e369c9.
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 1c94e65c668f44d2c69ae7e7fc268ab3268fba3e upstream.
The OSS emulation in synth-emux helper has a potential AB/BA deadlock
at the simultaneous closing and opening:
close
Hi Linus,
The following changes since commit 5ebe6afaf0057ac3eaeb98defd5456894b446d22:
Linux 4.1-rc2 (2015-05-03 19:22:23 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
tags/iommu-fixes-v4.1-rc3
for you to fetch changes up to
On Mon, May 11, 2015 at 7:54 AM, Peter Zijlstra wrote:
>
> Hmm, so I looked at the set_mb() definitions and I figure we want to do
> something like the below, right?
I don't think you need to do this for the non-smp cases. The whole
thing is about smp memory ordering, so on UP you don't even
On Mon, May 11, 2015 at 03:26:19PM +0900, Yoshinori Sato wrote:
> Changes for v12
> - IRQ chip convert to OF
> - dts cleanup
> - some headers use generic
> - rebase to v4.1-rc3
>
Configurations in arch/h8300/configs shtill build ok.
make allmodoconfig, after fixing the spi build error, results
On Mon, May 11, 2015 at 7:41 PM, Geert Uytterhoeven
wrote:
> On Mon, May 11, 2015 at 5:38 PM, Guenter Roeck wrote:
>>> + /home/kisskb/slave/src/fs/hostfs/hostfs_user.c: error: 'AT_FDCWD'
>>> undeclared (first use in this function): => 373
>>> +
> On 11 May 2015, at 14:24, Jonas Gorski wrote:
>
> Hi,
>
>> On Mon, May 11, 2015 at 12:38 PM, Kalle Valo wrote:
>> Okash Khawaja writes:
>>
>>> Sure, I'll create v2 of the patch with updated commit log.
>>>
>>> Since it's part of a patch set, do you want me to send both the
>>> patches in
From: Alex Ng
This enables dynamic protocol support on Windows 10 Hyper-V hosts.
If the host does not support Windows 10 protocol, then it falls back to
previous versions.
The change allows guests on Windows 10 Hyper-V hosts to hot-add memory
even when dynamic memory is not enabled on the
On 05/11/2015 12:00 PM, Russell King - ARM Linux wrote:
On Mon, May 11, 2015 at 11:55:41AM -0400, Murali Karicheri wrote:
On 04/24/2015 11:36 AM, santosh shilimkar wrote:
On 4/24/2015 8:15 AM, Murali Karicheri wrote:
On 04/23/2015 04:43 PM, santosh shilimkar wrote:
On 4/23/2015 12:37 PM,
On Mon, May 11, 2015 at 5:38 PM, Guenter Roeck wrote:
>> + /home/kisskb/slave/src/fs/hostfs/hostfs_user.c: error: 'AT_FDCWD'
>> undeclared (first use in this function): => 373
>> + /home/kisskb/slave/src/fs/hostfs/hostfs_user.c: error: (Each undeclared
>> identifier is reported only once:
On Fri, May 08, 2015 at 10:15:29AM -0600, Azael Avalos wrote:
> This patch fixes the build warning caused by the BT status variable,
> it was previously printing a u64 value, but since it was moved to
> another function, the value is now an int, and thus causing such
> warning.
>
> Signed-off-by:
On 05/10/2015 01:15 AM, Rafael J. Wysocki wrote:
On Saturday, May 09, 2015 10:33:05 PM Rafael J. Wysocki wrote:
On Saturday, May 09, 2015 10:11:41 PM Rafael J. Wysocki wrote:
On Saturday, May 09, 2015 11:19:16 AM Preeti U Murthy wrote:
Hi Rafael,
On 05/08/2015 07:48 PM, Rafael J. Wysocki
Hi Roger,
On Mon, May 11, 2015 at 4:13 PM, Roger Quadros wrote:
> commit b80eef95beb0 ('gpio: pcf857x: Propagate wake-up setting to parent irq
> controller')
> introduces the following recursive locking warning while suspending dra7-evm.
>
> The issue addressed by that commit has been already
On Mon, May 11, 2015 at 10:27:44AM -0700, Andrew Morton wrote:
> On Mon, 11 May 2015 10:19:16 -0700 "Paul E. McKenney"
> wrote:
>
> > On Mon, May 11, 2015 at 08:57:59AM -0400, Steven Rostedt wrote:
> > >
> > > NO_HZ_LEAVE_ME_THE_FSCK_ALONE!
> >
> > NO_HZ_OVERFLOWING?
>
> Actually, "NO_HZ"
On Mon, 11 May 2015, Trond Myklebust wrote:
> On Mon, May 11, 2015 at 12:39 PM, Sage Weil wrote:
> > On Mon, 11 May 2015, Dave Chinner wrote:
> >> On Sun, May 10, 2015 at 07:13:24PM -0400, Trond Myklebust wrote:
> >> > On Fri, May 8, 2015 at 6:24 PM, Sage Weil wrote:
> >> > > I'm sure you
On Mon, May 11, 2015 at 04:59:58PM +0100, a...@redhat.com wrote:
> Em Mon, May 11, 2015 at 12:58:14PM -0300, a...@redhat.com escreveu:
> > Em Mon, May 11, 2015 at 02:33:04PM +0200, Ingo Molnar escreveu:
> > > > That was already proposed here (as part of the fallback from getconf):
> > > >
> > > >
Hi,
* Dave Gerlach [150401 12:38]:
> Add the device tree bindings document for the TI Wakeup M3 remote
> processor devices on AM33xx and AM43xx SoCs. These devices are used
> to offload low-level power management functionality, and are handled
> by the wkup_m3 remoteproc driver.
>
>
Hello,
On Monday 11 May 2015 13:15:17 Nicholas Krause wrote:
> This adds a pointer cast to long in the function, sh_mmif_request_dma_one
I would use the uintptr_t type instead of long, as it has been designed for
this purpose exactly.
> for the when assigning one of the variables slave_id_tx
On Mon, 11 May 2015 10:19:16 -0700 "Paul E. McKenney"
wrote:
> On Mon, May 11, 2015 at 08:57:59AM -0400, Steven Rostedt wrote:
> >
> > NO_HZ_LEAVE_ME_THE_FSCK_ALONE!
>
> NO_HZ_OVERFLOWING?
Actually, "NO_HZ" shouldn't appear in the name at all. The objective
is to permit userspace to execute
On 11/05/15 18:10, Catalin Marinas wrote:
On Fri, May 08, 2015 at 04:08:53PM +0200, Arnd Bergmann wrote:
On Friday 01 May 2015 12:06:44 Catalin Marinas wrote:
If we just disallow DMA to devices that are marked with _CCA=0
in ACPI, we can avoid this case, or discuss it by the time someone has
From: Tejun Heo
Date: Mon, 11 May 2015 12:41:34 -0400
> + /* need to insert extra header fields, detect header and body */
> + header = msg;
> + body = memchr(msg, ';', msg_len);
> + if (WARN_ON_ONCE(!body))
> + return;
> +
> + header_len = body - header;
> +
On Mon, May 11, 2015 at 08:57:59AM -0400, Steven Rostedt wrote:
>
> NO_HZ_LEAVE_ME_THE_FSCK_ALONE!
NO_HZ_OVERFLOWING?
Kconfig naming controversy aside, I believe this patchset is addressing
a real need. Might need additional adjustment, but something useful.
Tejun,
thanks for your review and answer.
On 04.05.15 12:06:52, Tejun Heo wrote:
> > This patch also enables AHCI for Cavium Thunder SoCs that uses MSI-X.
>
> Please don't mix these two changes in the same patch.
I will split the patch.
> > + /* per-port msix interrupts are not supported */
On 05/10/2015 09:49 PM, Paul Gortmaker wrote:
All these drivers are configured with Kconfig options that are
declared as bool. Hence it is not possible for the code
to be built as modular. However the code is currently using the
module_platform_driver() macro for driver registration.
While
On Thu, May 07, 2015 at 07:37:13PM -0500, Suravee Suthikulpanit wrote:
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 4269dba..c7227e8 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -1,5 +1,6 @@
> config ARM64
> def_bool y
> + select ACPI_CCA_REQUIRED
On Mon, May 11, 2015 at 12:39 PM, Sage Weil wrote:
> On Mon, 11 May 2015, Dave Chinner wrote:
>> On Sun, May 10, 2015 at 07:13:24PM -0400, Trond Myklebust wrote:
>> > On Fri, May 8, 2015 at 6:24 PM, Sage Weil wrote:
>> > > I'm sure you realize what we're try to achieve is the same "invisible IO"
On Fri, May 08, 2015 at 04:08:53PM +0200, Arnd Bergmann wrote:
> On Friday 01 May 2015 12:06:44 Catalin Marinas wrote:
> > > If we just disallow DMA to devices that are marked with _CCA=0
> > > in ACPI, we can avoid this case, or discuss it by the time someone has
> > > hardware
> > > that wants
en function signatures and return values in this case this produced:
> ./kernel/rcu/tree.c:3538 WARNING: return of wrong type
> int != bool,
>
> Patch was compile tested with x86_64_defconfig (implies CONFIG_TREE_RCU=y)
>
> Patch is against 4.1-rc3 (loca
On 5/11/2015 8:55 AM, Murali Karicheri wrote:
On 04/24/2015 11:36 AM, santosh shilimkar wrote:
On 4/24/2015 8:15 AM, Murali Karicheri wrote:
On 04/23/2015 04:43 PM, santosh shilimkar wrote:
On 4/23/2015 12:37 PM, Murali Karicheri wrote:
NetCP driver support patches are already merged to
On 05/11/2015 07:44 AM, Christoph Hellwig wrote:
On Mon, May 11, 2015 at 01:20:00PM +0200, Bart Van Assche wrote:
Document when it is safe to call this function for blk-mq queues.
Maybe we should move the queue_lock acquisition into blk_abort_request
for the !blk-mq case? libata and libsas
ase this produced:
> > ./kernel/rcu/tree.c:3538 WARNING: return of wrong type
> > int != bool,
> >
> > Patch was compile tested with x86_64_defconfig (implies CONFIG_TREE_RCU=y)
> >
> > Patch is against 4.1-rc3 (localversion-next is -ne
>From j...@perches.com Mon May 11 16:49:27 2015
X-Session-Marker: 6A6F6540706572636865732E636F6D
X-Spam-Summary:
On Mon, May 11, 2015 at 10:42:49PM +0900, Krzysztof Kozlowski wrote:
> Usage of labels instead of full paths reduces possible mistakes when
> overriding nodes.
>
> Signed-off-by: Krzysztof Kozlowski
Wrt thermal zones:
Acked-by: Eduardo Valentin
> ---
>
On 05/11/2015 10:54 AM, Peter Zijlstra wrote:
On Mon, May 11, 2015 at 05:43:55AM -0700, tip-bot for Waiman Long wrote:
- (void)xchg(>state, vcpu_halted);
+ set_mb(pn->state, vcpu_halted);
Hmm, so I looked at the set_mb() definitions and I figure we want to do
On Fri, May 08, 2015 at 05:05:44PM -0700, Dmitry Torokhov wrote:
> From: Colin Cross
>
> The pointers to the 2nd level page tables are converted to 1st level
> page table entries, which means kmemleak can't find them and assumes
> they have been leaked. Call kmemleak_ignore on the 2nd level
On Mon, 2015-05-11 at 12:32 -0400, George Spelvin wrote:
> I suspect it's a speedup, but since this is not hot code, the important
> part is that it shrinks the function from 332 to 256 bytes.
shrinking code in vsprintf is always good
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
[]
> for
On 2015-05-08 John Stultz wrote:
> It was noted that the 32bit implementation of ktime_divns()
> was doing unsigned division and didn't properly handle
> negative values.
[...]
I have compiled, installed and tested (all weekend) the v3 of the patch
against 3.19.5-201.fc21.i686+PAE and it seems to
On Mon, May 11, 2015 at 09:43:41AM -0700, Stephane Eranian wrote:
> On Mon, May 11, 2015 at 9:36 AM, Peter Zijlstra wrote:
> > On Mon, May 11, 2015 at 09:32:33AM -0700, Stephane Eranian wrote:
> >> >> This is a minimal change. In principle the ACK could be moved much
> >> >> later.
> >> >
> >> >
On Mon, May 11, 2015 at 9:36 AM, Peter Zijlstra wrote:
> On Mon, May 11, 2015 at 09:32:33AM -0700, Stephane Eranian wrote:
>> >> This is a minimal change. In principle the ACK could be moved much later.
>> >
>> > Right, so the more complete change would be to use the new and improved
>> >
On Mon, May 11, 2015 at 07:52:29AM +0200, Nicholas Mc Guire wrote:
> klp_initialized() should return bool but is actually returning
> struct kobject * - convert it to a boolean explicitly.
>
> Signed-off-by: Nicholas Mc Guire
> ---
>
> static code checking was not happy with
>
printk logbuf keeps various metadata and optional key=value dictionary
for structured messages, both of which are stripped when messages are
handed to regular console drivers.
It can be useful to have this metadata and dictionary available to
netconsole consumers. This obviously makes logging
netconsole uses both bool and int for boolean values. Let's convert
nt->enabled to bool for consistency.
Signed-off-by: Tejun Heo
Cc: David Miller
---
drivers/net/netconsole.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/net/netconsole.c
Currently, each dynamic netconsole_target uses its own separate mutex
to synchronize the configuration operations. This patch replaces the
per-netconsole_target mutexes with a single mutex -
dynamic_netconsole_mutex. The reduced granularity doesn't hurt
anything, the code is minutely simpler and
This patchset is v3 of netconsole extended console support. v1 was
part of "printk, netconsole: implement reliable netconsole"
patchset[1]. The printk part is broken off to a separate patchset[2]
"printk: implement extended console support" which this patchset is
dependent upon.
Changes from
write_msg() grabs target_list_lock and walks target_list invoking
netpool_send_udp() on each target. Curiously, it protects each
iteration with netconsole_target_get/put() even though it never
releases target_list_lock which protects all the members.
While this doesn't harm anything, it doesn't
Frame pointer based stack traces aren't always reliable. One big reason
is that most asm functions don't set up the frame pointer.
Fix that by enforcing that all asm functions honor CONFIG_FRAME_POINTER.
This is done with a new stackvalidate host tool which is automatically
run for every
On Mon, 11 May 2015, Dave Chinner wrote:
> On Sun, May 10, 2015 at 07:13:24PM -0400, Trond Myklebust wrote:
> > On Fri, May 8, 2015 at 6:24 PM, Sage Weil wrote:
> > > I'm sure you realize what we're try to achieve is the same "invisible IO"
> > > that the XFS open by handle ioctls do by default.
In discussions around the live kernel patching consistency model RFC
[1], Peter and Ingo correctly pointed out that stack traces aren't
reliable. And as Ingo said, there's no "strong force" which ensures we
can rely on them.
So I've been thinking about how to fix that. My goal is to eventually
Add some helper macros for asm functions so that they can comply with
stackvalidate.
The FUNC_ENTER and FUNC_RETURN macros help asm functions save, set up,
and restore frame pointers.
The RET_NOVALIDATE and FILE_NOVALIDATE macros can be used to whitelist
the few locations which need a return
The separate push{lq}_cfi and pop_{lq}_cfi macros aren't needed. Push
and pop only come in one size per architecture, so the trailing 'q' or
'l' characters are redundant, and awkward to use in arch-independent
code.
Replace the push/pop CFI macros with architecture-independent versions:
I didn't see your decimal print changes before they went in, but great
work! That's a real "why didn't I think of that?" change.
Anyway, merging some local patches I have with that prompted me to look
over that file and I came up with the following two patches which might
be interesting. RFC
On Mon, May 11, 2015 at 09:32:33AM -0700, Stephane Eranian wrote:
> >> This is a minimal change. In principle the ACK could be moved much later.
> >
> > Right, so the more complete change would be to use the new and improved
> > FREEZE_ON_PMI and reenable both the LBRs and the CTRs with the
> >
On Tue, May 05, 2015 at 02:14:01PM +0100, Hanjun Guo wrote:
> On 2015???05???05??? 19:25, Sudeep Holla wrote:
> >
> >
> > On 05/05/15 03:46, Hanjun Guo wrote:
> >> Introduce invalid_phys_cpuid() to identify cpu with invalid
> >> physical ID, then used it as replacement of the direct comparisons
>
(Cc'ing netdev and netfilter-devel)
On Mon, May 11, 2015 at 2:29 AM, Klaus Ethgen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Recently I tried to mitigate some slow attacks via netfilter rule
> utilizing hashlimit target. I used the following specification:
>
>-A
On Monday 11 May 2015 19:15:52 Baolin Wang wrote:
> +static int default_timer_set64(struct k_itimer *timr, int flags,
> + struct itimerspec64 *new_setting64,
> + struct itimerspec64 *old_setting64)
> +{
> + struct k_clock *kc =
On Mon, May 11, 2015 at 9:23 AM, Peter Zijlstra wrote:
> On Sun, May 10, 2015 at 12:22:47PM -0700, Andi Kleen wrote:
>> From: Andi Kleen
>>
>> With Arch Perfmon v4 the PMU ack unfreezes the LBRs. So we need to do
>> the PMU ack after the LBR reading, otherwise the LBRs would be polluted by
>>
On Monday 11 May 2015 19:15:14 Baolin Wang wrote:
> +static int default_timer_get64(struct k_itimer *timr,
> + struct itimerspec64 *cur_setting64)
> +{
> + struct itimerspec cur_setting;
> + struct k_clock *kc = clockid_to_kclock(timr->it_clock);
> +
> +
501 - 600 of 2452 matches
Mail list logo
