2013/11/20 Sebastian Hesselbarth :
> Since phy_attach ensures PHYs are resumed, we can now suspend all
> PHYs that have no attached netdev after initcalls.
I do like the idea, but I think you might want to make sure that the
MDIO bus suspend policy was set to "auto" (which is the default afair)
On Wed, 20 Nov 2013, Tony Luck wrote:
> On Tue, Sep 17, 2013 at 11:53 AM, Thomas Gleixner wrote:
> > Use the proper core function instead of fiddling with PREEMPT_ACTIVE
> > and enable/disable interrupts in the low level code.
> >
> > Index: linux-2.6/arch/ia64/kernel/entry.S
> >
Put kfree after the 'clear_bit()' call.
Signed-off-by: Geyslan G. Bem
---
drivers/media/usb/cx231xx/cx231xx-cards.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/usb/cx231xx/cx231xx-cards.c
b/drivers/media/usb/cx231xx/cx231xx-cards.c
index e9d017b..528cce9
Hi,
I reported this bug a few days ago, but nobody did respond to my bug
report:
http://lkml.indiana.edu/hypermail/linux/kernel/1311.2/00058.html
Every time I restart the X server I will run into this bug with 3.12.0.
Help is welcome.
[ 9913.719551] BUG: Bad page state in process Xorg
Commit-ID: 372474e12a858807f03f73cb30e830a76fd1ae07
Gitweb: http://git.kernel.org/tip/372474e12a858807f03f73cb30e830a76fd1ae07
Author: H. Peter Anvin
AuthorDate: Wed, 20 Nov 2013 12:50:51 -0800
Committer: H. Peter Anvin
CommitDate: Wed, 20 Nov 2013 12:50:51 -0800
x86-64, copy_user:
> This is assuming your hard drive _itself_ doesn't have bufferbloat, but
> http://spritesmods.com/?art=hddhack=rss implies they don't, and
> tagged command queueing lets you see through that anyway so your
> "actually committed" numbers could presumably still be accurate if the
>
Hi,
On Wed, Nov 20, 2013 at 08:34:00PM +, Mark Brown wrote:
> On Wed, Nov 20, 2013 at 11:58:14AM -0600, Felipe Balbi wrote:
>
> > commit c368e5fc2a190923b786f2de3e79430ea3566a25 (regulator: fixed: get
> > rid of {get|list}_voltage()) regresses any MMC host controller which
> > uses fixed
http://goo.gl/ReMnjO располагаете бытовать Зрячим?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Tue, Nov 19, 2013 at 5:12 AM, Geert Uytterhoeven
wrote:
> Let early_init_dt_scan() fall-back to the built-in DT if no DT was passed,
> or if it's invalid, so architectures don't have to duplicate this logic.
>
> Suggested-by: Rob Herring
> Signed-off-by: Geert Uytterhoeven
> ---
Looks good
2013/11/20 Sebastian Hesselbarth :
> Network PHYs consume a noticable amount of power. This adds phy_resume
> on slave_open and phy_suspend on slave_stop to save this power if the
> port is down anyway.
>
> Signed-off-by: Sebastian Hesselbarth
> ---
> Cc: David S. Miller
> Cc:
On Sat, Nov 9, 2013 at 2:37 PM, Geert Uytterhoeven wrote:
> Add a DTS and defconfig for the Terasic DE0-Nano Development and Education
> Board running ORPSoC. This board contains an Altera Cyclone IV FPGA with
> support chips and I/O.
>
> The DTS was derived from published versions by Kevin
I'm announcing the release of the 3.11.9 kernel.
All users of the 3.11 kernel series must upgrade.
The updated 3.11.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.11.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 67077ad6edbb..eb29ec754a9e 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 12
-SUBLEVEL = 0
+SUBLEVEL = 1
EXTRAVERSION =
NAME = One Giant Leap for Frogkind
diff --git a/drivers/misc/atmel_pwm.c b/drivers/misc/atmel_pwm.c
diff --git a/Makefile b/Makefile
index 7521adbea135..06379bd78b64 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 11
-SUBLEVEL = 8
+SUBLEVEL = 9
EXTRAVERSION =
NAME = Linux for Workgroups
diff --git a/drivers/gpu/drm/i915/intel_dp.c
I'm announcing the release of the 3.12.1 kernel.
All users of the 3.12 kernel series must upgrade.
The updated 3.12.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.12.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 83a02f5b2c00..ba784b7b0f51 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 10
-SUBLEVEL = 19
+SUBLEVEL = 20
EXTRAVERSION =
NAME = TOSSUG Baby Fish
diff --git a/drivers/media/platform/sh_vou.c
I'm announcing the release of the 3.10.20 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web
On 11/20/2013 10:33 PM, Santosh Shilimkar wrote:
On Wednesday 20 November 2013 03:17 PM, Grygorii Strashko wrote:
On 11/20/2013 06:24 PM, Ivan Khoronzhuk wrote:
This series contains updates of Davinci nand driver, in order to be
reused for Keystone platform.
Depends on:
- Davinci nand driver
2013/11/20 Sebastian Hesselbarth :
> This adds helper functions to resume and suspend a given phy_device
> by calling the corresponding driver callbacks if available.
>
> Signed-off-by: Sebastian Hesselbarth
Looks good, thanks Sebastian:
Acked-by: Florian Fainelli
> ---
> Cc: David S. Miller
From: Sebastian Hesselbarth
Date: Wed, 20 Nov 2013 21:21:46 +0100
> Ethernet PHYs consume a significant amount of power when link is detected.
> Especially, for embedded systems it can be easily 20-40% of total system
> power. Now, currently most likely all ethernet drivers leave PHYs powered
>
On 11/20/2013 12:13 PM, Linus Torvalds wrote:
> On Wed, Nov 20, 2013 at 11:28 AM, H. Peter Anvin wrote:
>>>
>>> .section .fixup,"ax"
>>> 11: lea (%rdx,%rcx,8),%rcx
>>> 12: movl %ecx,%edx /* ecx is zerorest also */
>>
>> -> Even if %rdx+%rcx*8 > 2^32 we end up truncating at 12:
On Wednesday 20 November 2013 03:17 PM, Grygorii Strashko wrote:
> On 11/20/2013 06:24 PM, Ivan Khoronzhuk wrote:
>> This series contains updates of Davinci nand driver, in order to be
>> reused for Keystone platform.
>>
>> Depends on:
>> - Davinci nand driver fixes and updates:
>>
On Wed, Nov 20, 2013 at 11:58:14AM -0600, Felipe Balbi wrote:
> commit c368e5fc2a190923b786f2de3e79430ea3566a25 (regulator: fixed: get
> rid of {get|list}_voltage()) regresses any MMC host controller which
> uses fixed regulator for functionality.
This is already fixed in -next. Please remember
+ Kevin and Rafiel,
On Wednesday 20 November 2013 03:11 PM, Grygorii Strashko wrote:
> On 11/20/2013 09:53 PM, Stephen Boyd wrote:
>> On 11/20/13 11:06, Grygorii Strashko wrote:
>>> On 11/20/2013 08:42 PM, Stephen Boyd wrote:
On 11/20/13 05:31, Grygorii Strashko wrote:
> @@ -230,7 +230,7
On Wed, Nov 20, 2013 at 12:16 PM, Thomas Hellstrom
wrote:
> On 11/20/2013 05:50 PM, Andy Lutomirski wrote:
>>
>> On Wed, Nov 20, 2013 at 12:12 AM, Thomas Hellstrom
>> wrote:
>>>
>>> On 11/19/2013 11:51 PM, Andy Lutomirski wrote:
On 11/19/2013 12:06 PM, Thomas Hellstrom wrote:
>
Ethernet PHYs consume a significant amount of power when link is detected.
Especially, for embedded systems it can be easily 20-40% of total system
power. Now, currently most likely all ethernet drivers leave PHYs powered
on, even if the device is taken down. Also, some stupid boot loaders power
Network PHYs consume a noticable amount of power. This adds phy_resume
on slave_open and phy_suspend on slave_stop to save this power if the
port is down anyway.
Signed-off-by: Sebastian Hesselbarth
---
Cc: David S. Miller
Cc: net...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc:
Since phy_attach ensures PHYs are resumed, we can now suspend all
PHYs that have no attached netdev after initcalls.
Signed-off-by: Sebastian Hesselbarth
---
Cc: David S. Miller
Cc: net...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
Network PHYs consume a noticable amount of power. This adds phy_resume
on start_dev and phy_suspend on stop_dev to save this power if the
port is down anyway.
Signed-off-by: Sebastian Hesselbarth
---
Cc: David S. Miller
Cc: net...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc:
Marvell PHYs support generic PHY suspend/resume, so provide those
callbacks to all marvell specific drivers.
Signed-off-by: Sebastian Hesselbarth
---
Cc: David S. Miller
Cc: net...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
This adds helper functions to resume and suspend a given phy_device
by calling the corresponding driver callbacks if available.
Signed-off-by: Sebastian Hesselbarth
---
Cc: David S. Miller
Cc: net...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
This ensures PHYs are resumed on attach and suspended on detach.
Signed-off-by: Sebastian Hesselbarth
---
Cc: David S. Miller
Cc: net...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
drivers/net/phy/phy_device.c |3 +++
1 files changed, 3
Network PHYs consume a noticable amount of power. This adds phy_resume
on port start and phy_suspend on port stop to save this power if the
port is down anyway. While at it, also properly start/stop the phy.
Signed-off-by: Sebastian Hesselbarth
---
Cc: David S. Miller
Cc: net...@vger.kernel.org
On 11/20/2013 06:24 PM, Ivan Khoronzhuk wrote:
This series contains updates of Davinci nand driver, in order to be
reused for Keystone platform.
Depends on:
- Davinci nand driver fixes and updates:
https://lkml.org/lkml/2013/11/20/271
I suggest to merge this series with above one as
On 11/20/2013 05:22 PM, Ivan Khoronzhuk wrote:
This series contains fixes and updates of Davinci nand driver, in
order to prepare it to be reused for Keystone platform.
V1:
https://lkml.org/lkml/2013/11/11/352
Ivan Khoronzhuk (7):
mtd: nand: davinci: fix driver registration
mtd: nand:
On 11/20/2013 05:50 PM, Andy Lutomirski wrote:
On Wed, Nov 20, 2013 at 12:12 AM, Thomas Hellstrom
wrote:
On 11/19/2013 11:51 PM, Andy Lutomirski wrote:
On 11/19/2013 12:06 PM, Thomas Hellstrom wrote:
Hi!
Before going any further with this I'd like to check whether this is an
acceptable way
On 11/20/2013 09:53 PM, Stephen Boyd wrote:
> On 11/20/13 11:06, Grygorii Strashko wrote:
>> On 11/20/2013 08:42 PM, Stephen Boyd wrote:
>>> On 11/20/13 05:31, Grygorii Strashko wrote:
@@ -230,7 +230,7 @@ int pm_clk_suspend(struct device *dev)
list_for_each_entry_reverse(ce,
On Wed, Nov 20, 2013 at 11:28 AM, H. Peter Anvin wrote:
>>
>> .section .fixup,"ax"
>> 11: lea (%rdx,%rcx,8),%rcx
>> 12: movl %ecx,%edx /* ecx is zerorest also */
>
> -> Even if %rdx+%rcx*8 > 2^32 we end up truncating at 12: -- not that it
> matters, since both arguments are
From: Matt Wilson
Commit f62805f1 introduced a bug where lazy MMU mode isn't exited if a
m2p_add/remove_override call fails.
Cc: Stefano Stabellini
Cc: Konrad Rzeszutek Wilk
Cc: Boris Ostrovsky
Cc: David Vrabel
Cc: Anthony Liguori
Cc: xen-de...@lists.xenproject.org
Cc:
Hi,
On 01/04/2013 01:02 AM, Austin Boyle wrote:
This patch adds generic support for flash protection on STmicro chips.
On chips with less than 3 protection bits, the unused bits are don't cares
and so can be written anyway.
I have two remarks:
1) I believe this introduces incompatibilities
On Wed, Nov 20, 2013 at 03:00:56PM -0500, bfields wrote:
> On Wed, Nov 20, 2013 at 11:45:05AM -0500, Jeff Layton wrote:
> > Show "private" locks in /proc/locks with a 'P' suffix. This does mean
> > that we need to widen the column by one character.
> >
> > Also, tighten up the check in
On Wed, 20 Nov 2013 15:00:56 -0500
"J. Bruce Fields" wrote:
> On Wed, Nov 20, 2013 at 11:45:05AM -0500, Jeff Layton wrote:
> > Show "private" locks in /proc/locks with a 'P' suffix. This does mean
> > that we need to widen the column by one character.
> >
> > Also, tighten up the check in
Pavel Machek reports that this config is exposed on x86 where the
ARM architected timers aren't even present. Make it depend on the
ARM architected timers being selected so that non-ARM builds
aren't asked about it.
Reported-by: Pavel Machek
Signed-off-by: Stephen Boyd
---
On Wed, 20 Nov 2013 14:50:32 -0500
"J. Bruce Fields" wrote:
> On Wed, Nov 20, 2013 at 11:45:04AM -0500, Jeff Layton wrote:
> > Due to some unfortunate history, POSIX locks have very strange and
> > unhelpful semantics. The thing that usually catches people by surprise
> > is that they are
On Tue, Sep 17, 2013 at 11:53 AM, Thomas Gleixner wrote:
> Use the proper core function instead of fiddling with PREEMPT_ACTIVE
> and enable/disable interrupts in the low level code.
>
> Index: linux-2.6/arch/ia64/kernel/entry.S
>
On 11/20/13 11:06, Grygorii Strashko wrote:
> On 11/20/2013 08:42 PM, Stephen Boyd wrote:
>> On 11/20/13 05:31, Grygorii Strashko wrote:
>>> @@ -230,7 +230,7 @@ int pm_clk_suspend(struct device *dev)
>>> list_for_each_entry_reverse(ce, >clock_list, node) {
>>> if (ce->status <
On 11/20/2013 11:34 AM, Arnd Bergmann wrote:
> On Wednesday 20 November 2013, John Stultz wrote:
>> On 11/14/2013 04:40 AM, Arnd Bergmann wrote:
>>
>> Sorry, somehow this mail slipped by me.
>>
>> So yea, as I mentioned earlier, the build testing is the one thing I
>> don't have a good argument
Currently, zswap is writeback cache; stored pages are not sent
to swap disk, and when zswap wants to evict old pages it must
first write them back to swap cache/disk manually. This avoids
swap out disk I/O up front, but only moves that disk I/O to
the writeback case (for pages that are evicted),
The changes in commit 0ab0abcf511545d1fddbe72a36b3ca73388ac937
introduce a bug in writeback, if an entry is in use by load
it will be evicted anyway, which isn't correct (technically,
the code currently in zbud doesn't actually care much what the
zswap evict function returns, but that could
Since zswap_rb_erase was added to the final (when refcount == 0)
zswap_put_entry, there is no need to call zswap_rb_erase before
calling zswap_put_entry.
Signed-off-by: Dan Streetman
---
mm/zswap.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/mm/zswap.c b/mm/zswap.c
index
Dear RT Folks,
I'm pleased to announce the 3.2.52-rt73 stable release.
This release is just an update to the new stable 3.2.52 version
and no RT specific changes have been made.
You can get this release via the git tree at:
On Wed, 20 Nov 2013, Arjan van de Ven wrote:
>
> but for powerclamp to work, it needs to inject a deep idle I'm
> very ok using generic abstractions for that, but the abstraction
> needs to then include a "don't be nice about picking shallow C
> states for performance reasons, just pick
On Wednesday 20 November 2013, John Stultz wrote:
> On 11/14/2013 04:40 AM, Arnd Bergmann wrote:
>
> Sorry, somehow this mail slipped by me.
>
> So yea, as I mentioned earlier, the build testing is the one thing I
> don't have a good argument against. But I still would rather not having
> user
Hi Bruno,
I have tested the latest kernel and X, mesa etc, but am still using wine-1.3.24.
I am working on upgrading that. If I still
have the error I will file a bug report at bugs.freedesktop.org. I already have
a login because of the same problem
happening with Myst 5, but it was never
On Wed, 20 Nov 2013 20:18:41 +0100
Peter Zijlstra wrote:
> I think the below will cure both -- will fold in the proper patches
> tomorrow, need to get away from the computer noaw.
[Jacob Pan] looks good to me. one more thing for tomorrow :)
diff --git a/kernel/softirq.c b/kernel/softirq.c
On 11/16/2013 10:44 PM, Linus Torvalds wrote:
> So this doesn't do the 32-bit truncation in the error path of the
> generic string copy. Oversight?
>
>Linus
I looked at the code again, and it turns out to be false alarm.
We *do* do 32-bit truncation in every path, still:
>
Hi!
On x86, I get asked if I want to support arm architectured
timer. That's not exactly clever question... right?
I'd say it is from this merge... please fix.
Pavel
commit 191124efb4d6e5e47fe073b4b97350873523e88c
Merge: 68e9074
On Wed, Nov 20, 2013 at 10:54:57AM -0800, Jacob Pan wrote:
> run into a couple of compile issues.
>
> 1)
> include/linux/rcupdate.h: In function ‘rcu_read_unlock_sched_notrace’:
> include/linux/rcupdate.h:889:2: error: implicit declaration of function
> ‘preempt_enable_no_resched_notrace’
On Wed, Nov 20, 2013 at 03:20:28PM +0900, Jingoo Han wrote:
> On Wednesday, November 20, 2013 1:14 PM, Stefan Kristiansson wrote:
>
> > +static int ocfb_probe(struct platform_device *pdev)
> > +{
> > + int ret = 0;
> > + struct ocfb_dev *fbdev;
> > + struct ocfb_par *par = _par_priv;
> > +
On 11/19/2013 11:38 AM, Linus Torvalds wrote:
> On Mon, Nov 18, 2013 at 8:37 PM, H. Peter Anvin wrote:
>>
>> Do you have a preference:
>>
>> 1. Considering the 32-bit truncation incidental (take it or leave it);
>> 2. Require the 32-bit truncation, or
>> 3. Get rid of it completely?
>
> I don't
Hi Stephen,
On 11/20/2013 08:42 PM, Stephen Boyd wrote:
> On 11/20/13 05:31, Grygorii Strashko wrote:
>> The following warning is shown and clk_enable() failed on Keystone platform
>> if CONFIG_PM_RUNTIME is set and Runtime PM is enabled for Davinci gpio
>> driver:
>> [0.564486]
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>> +the chip select signal.
>> +Minimum value is 1 (0 treated as 1).
>> +
>> +- ti,cs-wsetup: write setup width, ns
>> +Time between the
On Wed, Nov 20, 2013 at 10:54:57AM -0800, Jacob Pan wrote:
> run into a couple of compile issues.
>
> 1)
> include/linux/rcupdate.h: In function ‘rcu_read_unlock_sched_notrace’:
> include/linux/rcupdate.h:889:2: error: implicit declaration of function
> ‘preempt_enable_no_resched_notrace’
On 20/11/2013 16:02, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 14:37 Wed 28 Aug , Boris BREZILLON wrote:
Add a new at91rm9200ek_mmc board (based on at91rm9200ek board) which enables
mmc0/slot0.
no for multiple dts
this need to handle at user space level
You mean, by controlling the
Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven
> Cc: David Howells
> Cc: linux-am33-l...@redhat.com
Acked-by: David Howells
--
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
Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven
> Cc: David Howells
Acked-by: David Howells
--
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
On Wed, 20 Nov 2013 09:55:18 -0800
"Frank Filz" wrote:
> > FL_FILP_PRIVATE locks are no longer tied to a particular PID, and are
> instead
> > inheritable by child processes. Report a l_pid of '-1' for these sorts of
> locks
> > since the pid is somewhat meaningless for them.
>
> Hmm, I suppose
Why are you posting this message a second time?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wed, 20 Nov 2013 17:04:57 +0100
Peter Zijlstra wrote:
> Discourage drivers/modules to be creative with preemption.
>
> Sadly all is implemented in macros and inline so if they want to do
> evil they still can, but at least try and discourage some.
>
> Cc: Rusty Russell
> Cc: Arjan van de
From: Grant Grundler
Date: Wed, 20 Nov 2013 09:42:42 -0800
> While this patch raises a new issue, can you apply this patch anyway
> since in most cases (default settings) it improves "the user
> experience" for most users?
I'm not applying a patch which knowingly is not implemented correctly.
On Thu, 7 Nov 2013 14:43:38 +0100
Juri Lelli wrote:
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index cb93f2e..18a73b4 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -10,6 +10,7 @@
> * miss some of their deadlines), and won't affect any
diff --git a/Makefile b/Makefile
index 2f9a0467..d7c0a383 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 4
-SUBLEVEL = 69
+SUBLEVEL = 70
EXTRAVERSION =
NAME = Saber-toothed Squirrel
diff --git a/arch/arm/lib/memset.S b/arch/arm/lib/memset.S
index
I'm announcing the release of the 3.4.70 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
On Tue, 2013-11-19 at 10:47 +0530, Bharat Bhushan wrote:
> From: Bharat Bhushan
>
> PAMU (FSL IOMMU) has a concept of primary window and subwindows.
> Primary window corresponds to the complete guest iova address space
> (including MSI space), with respect to IOMMU_API this is termed as
>
Hello,
I've been seeing some servers hit a condition where they receive a
large number of packets (over 500,000 per second, for example) which
causes a kernel panic due to a null pointer dereference. I've included
the tracebacks below.
I have not been able to reproduce this in my lab, but out in
On Wed, Nov 20, 2013 at 11:28 PM, J. Bruce Fields wrote:
> On Wed, Nov 20, 2013 at 10:41:54PM +0530, Chinmay V S wrote:
>> On Wed, Nov 20, 2013 at 9:25 PM, J. Bruce Fields
>> wrote:
>> > Some SSD's are also claim the ability to flush the cache on power loss:
>> >
>> >
>> >
> + the chip select signal.
> + Minimum value is 1 (0 treated as 1).
> +
> +- ti,cs-wsetup: write setup width, ns
> + Time between the beginning of a memory cycle
> + and
On 11/20/13 05:31, Grygorii Strashko wrote:
> The following warning is shown and clk_enable() failed on Keystone platform
> if CONFIG_PM_RUNTIME is set and Runtime PM is enabled for Davinci gpio driver:
> [0.564486] [ cut here ]
> [0.569221] WARNING: CPU: 0 PID: 1
On 20 November 2013 10:40, Guenter Roeck wrote:
> On Wed, Nov 20, 2013 at 10:24:54AM -0800, Markus Mayer wrote:
>> > Hi Markus,
>> >
>> > Yes, I noticed when I merged it into my watchdog-next branch.
>> >
>> > Reminds me ... v3 had a whitespace problem. I don't recall if you fixed
>> > that in
On Wed, Nov 20, 2013 at 10:24:54AM -0800, Markus Mayer wrote:
> > Hi Markus,
> >
> > Yes, I noticed when I merged it into my watchdog-next branch.
> >
> > Reminds me ... v3 had a whitespace problem. I don't recall if you fixed
> > that in v4. If you didn't, that might be a better reason to send
On Mon, Nov 18, 2013 at 12:46:00PM -0800, John Stultz wrote:
> Hmm. Reading this, but not having studied your patch in depth, is
> interesting. It originally was that we only applied any NTP adjustment
> to future changes. Also, since at that time the tick length was only
> changed on the second
Hi Linus,
Please pull the following Squashfs updates ...
Thanks
Phillip
The following changes since commit 959f58544b7f20c92d5eb43d1232c96c15c01bfb:
Linux 3.12-rc7 (2013-10-27 16:12:03 -0700)
are available in the git repository at:
On 11/14/2013 04:40 AM, Arnd Bergmann wrote:
> On Wednesday 13 November 2013, John Stultz wrote:
>>> +config EM_TIMER_STI
>>> + bool "STI timer driver"
>>> + default y if ARM
>>> + help
>>> + This enables build of the STI timer driver.
>>
>> So since I do want to avoid
Why? Live patching works fine and keys the other threads run along just fine.
We do this for ftrace already...
Andi Kleen wrote:
>"H. Peter Anvin" writes:
>>
>> We're talking user space here, which has different requirement (COW,
>> memory protection, ...) which means it is not really the
Rerwrite the main loop to use while_each_thread() instead of
next_thread(). We are going to fix or replace while_each_thread(),
next_thread() should be avoided whenever possible.
Signed-off-by: Oleg Nesterov
---
fs/proc/base.c | 20 ++--
1 files changed, 10 insertions(+), 10
proc_task_readdir() verifies that the result of get_proc_task()
is pid_alive() and thus its ->group_leader is fine too. However
this is not necessarily true after rcu_read_unlock(), we need
to recheck this again after first_tid() does rcu_read_lock().
Otherwise leader->thread_group.next (used by
proc_task_readdir() does not really need "leader", first_tid() has
to revalidate it anyway. Just pass proc_pid(inode) to first_tid()
instead, it can do pid_task(PIDTYPE_PID) itself and read
->group_leader only if necessary.
The patch also extracts the "inode is dead" code from
201 - 300 of 1243 matches
Mail list logo
