* Oleg Nesterov wrote:
> On 03/05, Ingo Molnar wrote:
> >
> > * Oleg Nesterov wrote:
> >
> > > --- a/arch/x86/kernel/traps.c
> > > +++ b/arch/x86/kernel/traps.c
> > > @@ -774,7 +774,10 @@ void math_state_restore(void)
> > > struct task_struct *tsk = current;
> > >
> > > if
When phy_pm_runtime_get_sync() returns -ENOTSUPP, phy_exit() also returns
-ENOTSUPP if !phy->ops->exit. Fix it.
Also move the code to override ret close to the code we got ret.
I think it is less error prone this way.
Signed-off-by: Axel Lin
---
drivers/phy/phy-core.c | 7 +++
1 file
The locks_insert/delete_block() functions are used for flock, posix
and leases types. blocked_lock_lock is used to serialize all access to
fl_link, fl_block, fl_next and blocked_hash. Here, we prepare the
stage for using blocked_lock_lock only to protect blocked_hash.
Signed-off-by: Daniel Wagner
blocked_lock_lock and file_lock_lglock are used to protect file_lock's
fl_link, fl_block, fl_next, blocked_hash and the percpu
file_lock_list.
Let's use blocked_lock_lock only to protect blocked_hash since it is a
global lock.
Whenever we insert a new lock we are going to grab besides the
Hi,
Finally, I got a bigger machine and did a quick test round. I expected
to see some improvements but the resutls do not show any real gain. So
they are merely refactoring patches.
4x Intel(R) Xeon(R) CPU E5-4610 v2 @ 2.30GHz
4.0.0-rc2/flock01.data
# NumSamples = 3; Min = 47160.80; Max =
On Thu, 05 Mar 2015, Joe Perches wrote:
> Only commit log and patch additions are checked for
> typos and spelling errors currently. Add a check
> of the email subject line too.
>
> Suggested-by: Jani Nikula
> Signed-off-by: Joe Perches
Thanks Joe.
FWIW,
Tested-by: Jani Nikula
> ---
>
On 03/06/2015 01:21 AM, Andres Freund wrote:
> Long mail ahead, sorry for that.
No problem, thanks a lot!
> TL;DR: THP is still noticeable, but not nearly as bad.
>
> On 2015-03-05 17:30:16 +0100, Vlastimil Babka wrote:
>> That however means the workload is based on hugetlbfs and shouldn't
On 2015/3/5 上午 06:32, Paul Bolle wrote:
> Chih-Chiang Chang schreef op wo 04-03-2015 om 20:53 [+0800]:
>> From fe37688e226f83ba477a3c2fbc1e64946cd4ec4e Mon Sep 17 00:00:00 2001
>> From: Chih-Chiang Chang
>> Date: Wed, 4 Mar 2015 20:03:21 +0800
>> Subject: [PATCH v2] ASoC: Add support for
Fix perf probe --line to handle aliased symbols correctly
in glibc.
This makes line_range search failing back to address-based
alternative search as same as --add and --vars.
Without this patch;
-
# ./perf probe -x /usr/lib64/libc-2.17.so -L malloc
Specified source line is not found.
Hi,
Here is a series of patches which improves perf-probe to
handle glibc's aliased symbols and weak symbols more
correctly.
This version includes 2 new patches from Namhyung (Thanks!)
which solves a problem on weak symbols. I added a fix
on his latter patch to modify
From: Namhyung Kim
It currently prevents adding probes in weak symbols. But there're cases
that given name is an only weak symbol so that we cannot add probe.
$ perf probe -x /usr/lib/libc.so.6 -a calloc
Failed to find symbol calloc in /usr/lib/libc-2.21.so
Error: Failed to add events.
This reverts commit 906451b98b67 ("perf probe: Fix to fall back to find probe
point in symbols").
Since perf-probe retries with the address of given symbol
searched from map before this path, this fall back routine
doesn't need anymore.
Signed-off-by: Masami Hiramatsu
---
From: Namhyung Kim
When perf probe tries to add a probe in a binary using symbol name, it
sometimes failed since some symbols were discard during loading dso.
When it resolves an address to symbol, it'd be better to have just one
symbol at given address. But for finding address from symbol,
Fix perf probe to handle aliased symbols correctly in glibc.
In the glibc, several symbols are defined as an alias of
__libc_XXX, e.g. malloc is an alias of __libc_malloc.
In such cases, dwarf has no subroutine instances of the
alias functions (e.g. no "malloc" instance), but the map
has that
* Andy Lutomirski wrote:
> This has nothing to do with the init thread or the initial anything.
> It's just the TSS.
>
> Signed-off-by: Andy Lutomirski
> ---
> arch/x86/kernel/entry_64.S | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git
From: Vivek Goyal
Subject: Re: [RESEND PATCH] kernel/panic/kexec: fix
"crash_kexec_post_notifiers" option issue in oops path
Date: Thu, 5 Mar 2015 17:22:04 -0500
> On Thu, Mar 05, 2015 at 05:19:30PM -0500, Vivek Goyal wrote:
>> On Wed, Mar 04, 2015 at 05:56:48PM +0900, HATAYAMA Daisuke wrote:
On Thu, Mar 5, 2015 at 6:07 PM, Andy Lutomirski wrote:
> On Mar 5, 2015 10:32 AM, "David Drysdale" wrote:
>>
>> Hi,
>>
>> Do we currently expect the audit system to work with x32 syscalls?
>>
>> I was playing with the audit system for the first time today (on
>> v4.0-rc2, due to [1]), and it
On 2015/3/4 下午 08:55, Mark Brown wrote:
> On Wed, Mar 04, 2015 at 08:35:52PM +0800, Chih-Chiang Chang wrote:
>> On 2015/2/24 下午 10:13, Mark Brown wrote:
>
>>> I would have expected the headphone volume control to be a stereo
>>> (double) control - same for speakers.
>
>> The nau8824 related
On Fri, Mar 6, 2015 at 4:05 PM, Masami Hiramatsu
wrote:
> (2015/03/04 22:52), Namhyung Kim wrote:
>> It currently prevents adding probes in weak symbols. But there're cases
>> that given name is an only weak symbol so that we cannot add probe.
>>
>> $ perf probe -x /usr/lib/libc.so.6 -a calloc
On Thu, Mar 05, 2015 at 06:48:50PM +0100, Vlastimil Babka wrote:
> On 03/05/2015 05:53 PM, Vlastimil Babka wrote:
> > On 02/12/2015 08:32 AM, Joonsoo Kim wrote:
> >>
> >> 1) Break non-overlapped zone assumption
> >> CMA regions could be spread to all memory range, so, to keep all of them
> >>
Change the RNGs to always return 0 in success case.
This patch ensures that seqiv.c works with RNGs other than krng. seqiv
expects that any return code other than 0 is an error. Without the
patch, rfc4106(gcm(aes)) will not work when using a DRBG or an ANSI
X9.31 RNG.
Signed-off-by: Stephan
In __set_free we will check whether all segment are free in one section
when free one segment, in order to set section to free status. But the
searching region of segmap is from start segno to last segno of main
area, it's not necessary. So let's just only check all segment bitmap
of target
extent tree/node slab cache is created during f2fs insmod,
how, it isn't destroyed during f2fs rmmod, this patch fix
it by destroy extent tree/node slab cache once rmmod f2fs.
Signed-off-by: Wanpeng Li
---
fs/f2fs/super.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/f2fs/super.c
On Thu, Mar 05, 2015 at 12:22:34PM +, Mark Brown wrote:
> On Thu, Mar 05, 2015 at 06:35:36PM +0800, Peter Chen wrote:
>
> > Any good ways at code/dts to show parent/child hierarchy for regulator?
>
> There's plenty of examples in mainline...
>
Thanks, I get answer for adding parent
On Tue, Mar 03, 2015 at 01:58:46PM +0530, Aneesh Kumar K.V wrote:
> Joonsoo Kim writes:
>
> > Until now, reserved pages for CMA are managed altogether with normal
> > page in the same zone. This approach has numorous problems and fixing
> > them isn't easy. To fix this situation, ZONE_CMA is
(2015/03/04 22:52), Namhyung Kim wrote:
> It currently prevents adding probes in weak symbols. But there're cases
> that given name is an only weak symbol so that we cannot add probe.
>
> $ perf probe -x /usr/lib/libc.so.6 -a calloc
> Failed to find symbol calloc in /usr/lib/libc-2.21.so
>
On 2015/3/5 23:19, Catalin Marinas wrote:
> On Thu, Mar 05, 2015 at 02:13:58PM +0100, Rafael J. Wysocki wrote:
>> On Thu, Mar 5, 2015 at 12:27 PM, Catalin Marinas
>> wrote:
>>> On Thu, Mar 05, 2015 at 04:03:21PM +0800, Hanjun Guo wrote:
On 2015/3/5 6:46, Rafael J. Wysocki wrote:
> IMO,
> -Original Message-
> From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> Sent: Wednesday, March 04, 2015 8:06 PM
> To: Wu, Feng
> Cc: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org;
> g...@kernel.org; pbonz...@redhat.com; dw...@infradead.org;
> j...@8bytes.org;
On 2015/3/5 21:23, Rafael J. Wysocki wrote:
> On Thu, Mar 5, 2015 at 8:44 AM, Hanjun Guo wrote:
>> On 2015/3/5 6:29, Rafael J. Wysocki wrote:
>>> On Wednesday, February 25, 2015 04:39:42 PM Hanjun Guo wrote:
> [cut]
>
@@ -190,7 +190,7 @@ int acpi_map_cpuid(int phys_id, u32 acpi_id)
Le 06/03/2015 01:21, Kim Phillips a écrit :
On Thu, 5 Mar 2015 17:46:05 +0100
Christophe Leroy wrote:
[15/17] crypto: talitos - Implementation of SEC1
...
[16/17] crypto: talitos - SEC1 bugs on 0 data hash
[17/17] crypto: talitos - Update DT bindings with SEC1
This patchseries doesn't
> From that regard, RSB is a multiple device bus, using addresses, just
> like I2C. The way it communicates is basically the one used by P2WI.
I am not keen to allow everything which "is a bus and has addresses"
into the I2C realm. The addresses are 12 bit, whilst I2C has at maximum
10 bit which
(2015/03/06 15:15), Namhyung Kim wrote:
> Hi Masami,
>
> On Thu, Mar 05, 2015 at 12:57:21AM +0900, Masami Hiramatsu wrote:
>> (2015/03/04 22:52), Namhyung Kim wrote:
>>> It currently prevents adding probes in weak symbols. But there're cases
>>> that given name is an only weak symbol so that we
Hi Vladimir,
On Fri, Mar 06, 2015 at 09:09:37AM +0300, Vladimir Davydov wrote:
> Hi,
>
> This bug should have been fixed by "[PATCH -next] cpuset: initialize
> cpuset a bit early":
>
> http://www.spinics.net/lists/cgroups/msg12599.html
OK, sorry for the late report! I only searched for the
On Thu, Mar 05, 2015 at 04:08:44PM +, James Hogan wrote:
> [ Upstream commit 3ce465e04bfd8de9956d515d6e9587faac3375dc ]
>
> Export the _save_fp asm function used by the lose_fpu(1) macro to GPL
> modules so that KVM can make use of it when it is built as a module.
>
> This fixes the
This patch series introduce ACPI support for AHCI platform driver.
Existing ACPI support for AHCI assumes the device controller is a PCI device.
Since there is no ACPI _CID for generic AHCI controller, the driver
could not use it for matching devices. Therefore, this patch introduces
a mechanism
Device drivers typically use ACPI _HIDs/_CIDs listed in struct device_driver
acpi_match_table to match devices. However, for generic drivers, we do not
want to list _HID for all supported devices. Also, certain classes of devices
do not have _CID (e.g. SATA, USB). Instead, we can leverage ACPI
These 2 patches are fixup for MT8173 pinctrl driver:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/320066.html
Arm64 maintainers doesn't want to add MACH_* in Kconfig, this patch
is used to replace the first one in that series.
Matthias,
Can you take this one?
Linus,
This one make PINCTRL_MT8173 option user selectable and is based on
mtk-staging in your tree. If you think this is OK, please applied or
squash this into previous change. Thanks.
--
ARM64 maintainer doesn't want to add MACH_* for each SoC.
Hi Masami,
On Thu, Mar 05, 2015 at 12:57:21AM +0900, Masami Hiramatsu wrote:
> (2015/03/04 22:52), Namhyung Kim wrote:
> > It currently prevents adding probes in weak symbols. But there're cases
> > that given name is an only weak symbol so that we cannot add probe.
> >
> > $ perf probe -x
Hi Stefan,
On Thu, Mar 05, 2015 at 12:10:20AM +0100, Stefan Agner wrote:
> +
> +static int vf610_nfc_probe_dt(struct device *dev, struct vf610_nfc_config
> *cfg)
> +{
> + struct device_node *np = dev->of_node;
> + int buswidth;
> + u32 clkrate;
> +
> + if (!np)
> +
From: Cyrille Pitchen
Most of the functions from the Common Clk Framework handle NULL pointer as
input argument.
Since the TX clock is optional, we now set tx_clk to NULL value
instead of ERR_PTR(-ENOENT) when this clock is not available. This simplifies
the clock management and avoid the need
From: Cyrille Pitchen
macb and at91_ether drivers can be compiled as modules, but the at91_ether
driver use some functions and variables defined in the macb one, thus
creating a dependency on the macb driver.
Since these drivers are sharing the same logic we can easily merge
at91_ether into
Hello,
The rm9200 boards use the dedicated at91_ether driver instead of the
regular macb driver.
Both the macb and at91_ether drivers can be compiled as separated
modules.
Since the at91_ether driver uses code from the macb driver, at91_ether.ko
depends on macb.ko.
However the macb.ko module
This patch adds ACPI supports for AHCI platform driver, which uses _CLS
method to match the device.
The following is an example of ASL structure in DSDT for a SATA controller,
which contains _CLS package to be matched by the ahci_platform driver:
Device (AHC0) // AHCI Controller
{
Hi,
This bug should have been fixed by "[PATCH -next] cpuset: initialize
cpuset a bit early":
http://www.spinics.net/lists/cgroups/msg12599.html
Thanks,
Vladimir
On Fri, Mar 06, 2015 at 01:57:58PM +0800, Fengguang Wu wrote:
> [0.021989] [ cut here ]
> [0.021989]
On 05/03/15 22:29, David Rientjes wrote:
On Thu, 5 Mar 2015, Alex Dowad wrote:
diff --git a/kernel/fork.c b/kernel/fork.c
index cf65139..b38a2ae 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -1186,10 +1186,12 @@ init_task_pid(struct task_struct *task, enum
pid_type type, struct pid *pid)
60+
2 Merge tag 'dma-buf-for-4.0-rc3' of
git://git.kernel.org/pub/scm/linux/kernel/git/sumits/dma-buf
# extra tests on tree/branch next/master
git bisect good cbbf783608bd1f177fd8b1f6498bb2481116beed # 23:53 60+
0 Add linux-next specific files for 20150305
This scri
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
commit 0b2af171520e5d5e7d5b5f479b90a6a5014d9df6
Author: Murali Karicheri
AuthorDate: Tue Mar 3 12:52:13 2015 -0500
Commit: Bjorn Helgaas
> From: Hiroshi Shimamoto
>
> Disable hardware VLAN filtering if netdev->features VLAN flag is dropped.
>
> In SR-IOV case, there is a use case which needs to disable VLAN filter.
> For example, we need to make a network function with VF in virtualized
> environment. That network function may
rc3' of
git://git.kernel.org/pub/scm/linux/kernel/git/sumits/dma-buf
# extra tests on tree/branch next/master
git bisect good cbbf783608bd1f177fd8b1f6498bb2481116beed # 14:52 60+
60 Add linux-next specific files for 20150305
This script may reproduce the er
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git
revert-295458e67284f57d154ec8156a22797c0cfb044a-295458e67284f57d154ec8156a22797c0cfb044a
commit 295458e67284f57d154ec8156a22797c0cfb044a
Author:
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip
revert-3f4560207f796d5f79c18329d5a5d383fe3c97bb-3f4560207f796d5f79c18329d5a5d383fe3c97bb
commit 3f4560207f796d5f79c18329d5a5d383fe3c97bb
Author: Konrad
+cc Sascha
On 5 March 2015 at 17:55, Viresh Kumar wrote:
> On 5 March 2015 at 12:57, Pi-Cheng Chen wrote:
>
>> On 4 March 2015 at 19:09, Viresh Kumar wrote:
>> There are 2 clusters, but only the big cluster need to do voltage scaling in
>> the
>> notifier, since the voltage controlling is
On Thu, Mar 05, 2015 at 01:24:47AM +, Horiguchi Naoya(堀口 直也) wrote:
...
> > Is the "UC" entry at the end of the severities[] table just a catch-all for
> > things that made it
> > past all the other entries? Does it ever really get used?
>
> I read through the severity check table and it
Uprobe uses inode address to index all registered uprobes in a
rb_tree, this works well in most filesystems but failed on 9pfs.
9pfs allocate more than one vfs inode to the same file, the inode
address when we create uprobe is not same as the inode address we
run later. As a result, neither perf
Hi all,
Changes since 20150305:
The net-next tree lost its build failure.
The vhost tree gained a conflict against the virtio tree.
Non-merge commits (relative to Linus' tree): 2757
2807 files changed, 87638 insertions(+), 60274 deletions
Hi Changman,
On Fri, Mar 06, 2015 at 11:37:28AM +0800, Chao Yu wrote:
>Hi Changman,
>
>> -Original Message-
>> From: Changman Lee [mailto:cm224@samsung.com]
>> Sent: Tuesday, March 03, 2015 9:40 AM
>> To: linux-f2fs-de...@lists.sourceforge.net
>> Cc: Jaegeuk Kim; Chao Yu;
On Thu, Mar 05, 2015 at 12:10:20AM +0100, Stefan Agner wrote:
> This driver supports Freescale NFC (NAND flash controller) found on
> Vybrid (VF610), MPC5125, MCF54418 and Kinetis K70.
>
> Limitations:
> - DMA and pipelining not used
> - Pages larger than 2k are not supported
> - No hardware ECC
On Tue, Feb 17, 2015 at 03:14:00PM -0800, Feng Kan wrote:
> The generic accessor functions for pci-xgene uses map_bus
> call that returns the base address but did not add the additional
> offset.
>
> Signed-off-by: Feng Kan
Applied to for-linus for v4.0, with acks from Tanmay and Rob. Thanks!
On Thu, Mar 05, 2015 at 02:57:55PM -0600, Rob Herring wrote:
> On Thu, Mar 5, 2015 at 10:38 AM, Bjorn Helgaas wrote:
> > [+cc Mark]
> >
> > On Thu, Feb 26, 2015 at 06:21:51PM -0600, Bjorn Helgaas wrote:
> >> On Tue, Feb 17, 2015 at 03:14:00PM -0800, Feng Kan wrote:
> >> > The generic accessor
On Thu, 2015-03-05 at 17:12 -0500, Steven Rostedt wrote:
> A bug in ftrace was reported to me that affects ARM and ARM64 but not
> x86. Looking at the code it appears to affect PowerPC as well. So I
> booted up my old PA Semi, to give it a try. The last time I booted it
> was for a 3.17 kernel.
On Thu, 2015-03-05 at 21:05 -0700, David Ahern wrote:
> Hi Peter/Mike/Ingo:
>
> I've been banging my against this wall for a week now and hoping you or
> someone could shed some light on the problem.
>
> On larger systems (256 to 1024 cpus) there are several use cases (e.g.,
>
Hi Frederic and Arnaldo,
On Thu, Mar 05, 2015 at 05:08:56PM +0100, Frederic Weisbecker wrote:
> On Wed, Mar 04, 2015 at 09:02:55AM +0900, Namhyung Kim wrote:
> > Hi Frederic,
> >
> > On Tue, Mar 03, 2015 at 05:28:40PM +0100, Frederic Weisbecker wrote:
> > > On Tue, Mar 03, 2015 at 12:07:24PM
On Fri, Feb 27, 2015 at 09:06:00AM -0500, Matt Porter wrote:
> The chipidea driver adds an extra line of spam to the log when a
> host-only chipidea instance is left set to the default of a dual role
> controller.
>
> [2.010873] ci_hdrc ci_hdrc.1: doesn't support gadget
>
> Set the dr_mode
Hi, Christoph Hellwig
resend: + cc lkml
I found regression in v4.0-rc1 caused by this patch:
Author: Christoph Hellwig
Date: Wed Jan 14 10:42:36 2015 +0100
fs: export inode_to_bdi and use it in favor of mapping->backing_dev_info
Test process is following:
2015-02-25 15:50:22: Start
On 2015/3/6 2:57, Olof Johansson wrote:
> Hi,
Hi Olof,
>
> On Wed, Feb 25, 2015 at 04:39:40PM +0800, Hanjun Guo wrote:
>> Changes since v8:
>> - remove MPIDR packing things by introducing phys_cpuid_t;
>>
>> - update patch acpi: fix acpi_os_ioremap for arm64 to follow
>> Rafael's
On Thu, Mar 05, 2015 at 08:56:44AM +0100, Jiri Olsa wrote:
> On Tue, Mar 03, 2015 at 12:07:20PM +0900, Namhyung Kim wrote:
>
> SNIP
>
> > +static int record__merge_index_files(struct record *rec, int nr_index)
> > +{
> > + int i;
> > + int ret = -1;
> > + u64 offset;
> > + char
Hi Jiri,
On Wed, Mar 04, 2015 at 05:19:54PM +0100, Jiri Olsa wrote:
> On Tue, Mar 03, 2015 at 12:07:19PM +0900, Namhyung Kim wrote:
> > When perf detects data file has index table, process header part first
> > and then rest data files in a row. Note that the indexed sample data is
> > recorded
The field of page size in register GITS_BASERn might be read-only
if an implementation only supports a single, fixed page size. But
currently the ITS driver will throw out an error when PAGE_SIZE
is less than the minimum size supported by an ITS. So addressing
this problem by using 64KB pages as
This patch series makes some enhancement to ITS configuration in the
following aspects:
o make allocation of the ITS tables more sensible
o replace magic numbers with sensible macros
o guarantees a safe quiescent status before initializing an ITS
This patch series is based on Marc's branch[1],
Some kind of brain-dead implementations chooses to insert ITEes in
rapid sequence of disabled ITEes, and an un-zeroed ITT will confuse
ITS on judging whether an ITE is really enabled or not. Considering
the implementations are still supported by the GICv3 architecture,
in which ITT is not required
When required size of Device Table is out of the page allocator's
capability, the whole ITS will fail in probing. This actually is
not the hardware's problem and is mainly a limitation of the kernel
page allocator. This patch will keep ITS going on to the next
initializaion stage with an explicit
Define macros for GITS_CTLR fields to avoid using magic numbers.
Acked-by: Marc Zyngier
Signed-off-by: Yun Wu
---
drivers/irqchip/irq-gic-v3-its.c | 2 +-
include/linux/irqchip/arm-gic-v3.h | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git
It's unsafe to change the configurations of an activated ITS directly
since this will lead to unpredictable results. This patch guarantees
the ITSes being initialized are quiescent.
Acked-by: Marc Zyngier
Signed-off-by: Yun Wu
---
drivers/irqchip/irq-gic-v3-its.c | 35
On Thu, Mar 05, 2015 at 08:53:38AM -0800, Feng Kan wrote:
> Please take Mark's patch if you think it is better.
>
>
>
> On Thu, Mar 5, 2015 at 8:38 AM, Bjorn Helgaas wrote:
> > [+cc Mark]
> >
> > On Thu, Feb 26, 2015 at 06:21:51PM -0600, Bjorn Helgaas wrote:
> >> On Tue, Feb 17, 2015 at
Hi Peter/Mike/Ingo:
I've been banging my against this wall for a week now and hoping you or
someone could shed some light on the problem.
On larger systems (256 to 1024 cpus) there are several use cases (e.g.,
http://www.cs.virginia.edu/stream/) that regularly trigger the NMI
watchdog with
On 03/05/2015 03:27 PM, Randy Dunlap wrote:
From: Randy Dunlap
Fix build errors when CONFIG_THERMAL=m and SENSORS_PWM_FAN=y
by restricting SENSORS_PWM_FAN to 'm' when THERMAL=m.
drivers/built-in.o: In function `pwm_fan_remove':
pwm-fan.c:(.text+0x22ba58): undefined reference to
On Thu, Mar 05, 2015 at 11:54:52PM +, Mel Gorman wrote:
> Dave Chinner reported the following on https://lkml.org/lkml/2015/3/1/226
>
>Across the board the 4.0-rc1 numbers are much slower, and the
>degradation is far worse when using the large memory footprint
>configs. Perf
On Fri, 2015-03-06 at 09:49 +0800, Jiang Liu wrote:
> On 2015/3/6 5:06, Alex Williamson wrote:
> > The IRQ resource for a device is established when pci_enabled_device()
> > is called on a fully disabled device (ie. enable_cnt == 0). With
> > commit b4b55cda5874 ("x86/PCI: Refine the way to
Hi Linus,
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.0-3
for you to fetch changes up to
Hi Changman,
> -Original Message-
> From: Changman Lee [mailto:cm224@samsung.com]
> Sent: Tuesday, March 03, 2015 9:40 AM
> To: linux-f2fs-de...@lists.sourceforge.net
> Cc: Jaegeuk Kim; Chao Yu; linux-fsde...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2]
Functions rtsx_usb_ep0_read_register() and rtsx_usb_get_card_status()
both use arbitrary buffer addresses from arguments directly for DMA and
the buffers could be located in stack. This was caught by DMA-API debug
check.
Fixes this by using double-buffers via kzalloc in both functions to
Hi Michael,
Today's linux-next merge of the vhost tree got a conflict in
drivers/virtio/virtio_balloon.c between commit 7f8998200dcb
("virtio_balloon: annotate possible sleep waiting for event") from the
virtio tree and commit 2426d3b03d07 ("virtio-balloon: do not call
blocking ops when
We are running CPU and network heavy test on marmot.pdl.cmu.edu cluster.
It has Mellanox Technologies MT23108 InfiniHost controller.
When we start using it for network communications, after just few
minutes some of the nodes of the cluster die
with the following machine check exception.
I
On (03/05/15 09:20), Minchan Kim wrote:
> In summary, I want to support only "cat /sys/class/zram-control/zram_add"
> unless you have feasible usecase.
>
> What do you think about it?
>
Hello Minchan,
I've tried to contact as many guys (who has previously demonstrated some
interest in
On Mon, Mar 02, 2015 at 11:45:11AM +1100, Chris Dunlop wrote:
> Heads up...
>
> We've hit this BUG() in v3.10.70, v3.14.27 and v3.18.7:
>
> net/core/skbuff.c:
> 1027 int pskb_expand_head(struct sk_buff *skb, int nhead, int ntail,
> 1028 gfp_t gfp_mask)
> 1029 {
> 1030
From: Stefan Agner
Date: Thu, 5 Mar 2015 15:09:29 +0100
> When the driver is removed (e.g. using unbind through sysfs), the
> clocks get disabled twice, once on fec_enet_close and once on
> fec_drv_remove. Since the clocks are enabled only once, this leads
> to a warning:
>
> WARNING: CPU: 0
From: Michal Simek
Date: Thu, 5 Mar 2015 15:02:10 +0100
> From: Punnaiah Choudary Kalluri
>
> The latest spec "I-IPA01-0266-USR Rev 10" limit the MID field length to 12 bit
> value. For previous versions it is 16 bit value.
>
> This change will not break the backward compatibility as the
We currently store references to the top of the kernel stack in
multiple places: kernel_stack (with an offset) and
init_tss.x86_tss.sp0 (no offset). The latter is defined by hardware
and is a clean canonical way to find the top of the stack. Add an
accessor so we can start using it.
This needs
The INIT_TSS is unnecessary. Just define the initial TSS where cpu_tss
is defined.
While we're at it, merge the 32-bit and 64-bit definitions. The only
syntactic change is that 32-bit kernels were computing sp0 as long, but
now they compute it as unsigned long.
Verified by objdump: the
This has nothing to do with the init thread or the initial anything.
It's just the TSS.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/entry_64.S | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/entry_64.S b/arch/x86/kernel/entry_64.S
index
Denys is right that KERNEL_STACK_OFFSET is a mess. Let's start fixing
it.
This removes all C code that *reads* kernel_stack. It also fixes the
KERNEL_STACK_OFFSET abomination in ia32_sysenter_target.
It does not fix the KERNEL_STACK_OFFSET abomination in GET_THREAD_INFO
and THREAD_INFO. I
This will make modifying the semantics of kernel_stack easier.
The change to ist_begin_non_atomic() is necessary because sp0 no
longer points to the same THREAD_SIZE-aligned region as rsp; it's
one byte too high for that. At Denys' suggestion, rather than
offsetting it, just check explicitly
It has nothing to do with init -- there's only one tss per cpu.
Other names considered include:
- current_tss: Confusing because we never switch the tss.
- singleton_tss: Too long.
This patch was generated with 's/init_tss/cpu_tss/g'. Followup patches
will fix INIT_TSS and INIT_TSS_IST by
The ia32 sysenter code loaded the top of the kernel stack into rsp
by loading kernel_stack and then adjusting it. It can be simplified
to just read sp0 directly.
This requires the addition of a new asm-offsets entry for sp0.
Signed-off-by: Andy Lutomirski
---
arch/x86/ia32/ia32entry.S
On Thu, Mar 5, 2015 at 5:35 PM, Alexandre Belloni
wrote:
> On 05/03/2015 at 16:50:57 -0600, Rob Herring wrote :
>> > -config SOC_SAMA5
>> > +config ARCH_AT91
>> > bool
>> > - select ATMEL_AIC5_IRQ
>> > + select ARCH_REQUIRE_GPIOLIB
>> > select COMMON_CLK_AT91
>> > -
On Thu, Mar 05, 2015 at 09:37:52AM +, Naoya Horiguchi wrote:
...
> > With the above simplified versions used, the rest of the patch becomes
> > almost trivial.
>
> Other than that, I'm OK to write in the simplified form.
Here is the updated one.
And I found some cleanups and/or tiny fixes
On Thu, Mar 05, 2015 at 12:22:34PM +, Mark Brown wrote:
> On Thu, Mar 05, 2015 at 06:35:36PM +0800, Peter Chen wrote:
>
> > Any good ways at code/dts to show parent/child hierarchy for regulator?
>
> There's plenty of examples in mainline...
>
thanks, I am back to study again.
> > The
From: Alexander Drozdov
Date: Thu, 5 Mar 2015 10:29:39 +0300
> ip_check_defrag() may be used by af_packet to defragment outgoing packets.
> skb_network_offset() of af_packet's outgoing packets is not zero.
>
> Signed-off-by: Alexander Drozdov
Applied, thanks.
--
To unsubscribe from this
From: Mike Frysinger
Date: Thu, 5 Mar 2015 00:47:08 -0500
> The NLMSG_OK macro compares three things:
> - the len arg from the user
> - a size_t: sizeof(struct nlmsghdr)
> - an int: sizeof(struct nlmsghdr) casted
> - an u32: the nlmsghdr->nlmsg_len member
>
> When building with
1 - 100 of 1698 matches
Mail list logo
