On Tue, Sep 24, 2013 at 03:22:46PM -0700, Tim Chen wrote:
> We will need the MCS lock code for doing optimistic spinning for rwsem.
> Extracting the MCS code from mutex.c and put into its own file allow us
> to reuse this code easily for rwsem.
>
> Signed-off-by: Tim Chen
> Signed-off-by:
On Fri, Aug 02, 2013 at 04:50:42PM +0200, Guennadi Liakhovetski wrote:
> This patch adds DMA slave bindings for the two required DMA channels
> for MMCIF0 to ape6evm-reference.
>
> Signed-off-by: Guennadi Liakhovetski
Does this patch depend on any of the other paches in this series?
> ---
>
On Tue, Aug 20, 2013 at 9:41 PM, Rafael J. Wysocki wrote:
> On Tuesday, August 20, 2013 08:27:27 AM Tejun Heo wrote:
>> On Tue, Aug 20, 2013 at 02:34:14PM +0200, Rafael J. Wysocki wrote:
>> > On Tuesday, August 20, 2013 08:22:00 AM Tejun Heo wrote:
>> > > On Tue, Aug 20, 2013 at 02:30:18PM +0200,
On Fri, Aug 02, 2013 at 04:50:41PM +0200, Guennadi Liakhovetski wrote:
> Add a DT node for the only system DMAC instance on r8a73a4. The RT DMAC
> can be added later under the same multiplexer, because they can serve the
> same slaves and use the same MID-RID values. Configuration data is
>
On Fri, Aug 02, 2013 at 04:50:40PM +0200, Guennadi Liakhovetski wrote:
> Add a DMAC platform device and clock definitions for it on r8a73a4.
>
> Signed-off-by: Guennadi Liakhovetski
> ---
>
> Depends on "DMA: shdma: support the new CHCLR register layout"
> https://lkml.org/lkml/2013/7/10/146
On 09/25/2013 10:34 AM, David Rientjes wrote:
On Mon, 23 Sep 2013, Ming Liu wrote:
After selecting a task to kill, the oom killer iterates all processes and
kills all other user threads that share the same mm_struct in different
thread groups.
But in some extreme cases, the selected task
On Tue, Sep 24, 2013 at 05:12:26PM -0700, H. Peter Anvin wrote:
> I am starting to think that we really should explicitly pass along the
> EFI mappings to the secondary kernel. This will also help if we have to
> change the algorithm in a future kernel.
That would be the most flexible solution,
On Mon, Sep 23, 2013 at 11:41:03PM +0200, Thierry Reding wrote:
> The GPIO API defines 0 as being a valid GPIO number, so this field needs
> to be initialized explicitly.
>
> Signed-off-by: Thierry Reding
> ---
> arch/arm/mach-shmobile/board-armadillo800eva.c | 1 +
> 1 file changed, 1
On 09/24/2013 11:50 PM, Eduardo Valentin wrote:
Zhang,
I appreciate your interest. I am replying a couple of your comments.
Please also check my answers to Mark's queries on other email thread.
When I replied to Mark yesterday, I missed your mail replying him already.
I should check that mail
On Tue, Sep 24, 2013 at 11:00:24AM +0200, Thierry Reding wrote:
> On Tue, Sep 24, 2013 at 05:14:46PM +0900, Simon Horman wrote:
> > [ Cc: Olof Johansson, Kevin Hilman and Arnd Bergman: arm-soc maintainers ]
> >
> > On Mon, Sep 23, 2013 at 11:40:57PM +0200, Thierry Reding wrote:
> > > This series
On Wed, Sep 25, 2013 at 09:59:19AM +1000, Stephen Rothwell wrote:
> Hi Steffen,
>
> On Tue, 24 Sep 2013 12:25:05 +0200 Steffen Klassert
> wrote:
> >
> > On Tue, Sep 24, 2013 at 12:16:29PM +1000, Stephen Rothwell wrote:
> > >
> > > Today's linux-next merge of the ipsec-next tree got a conflict
Hi all,
My embedded development box fails to NFS-boot with NFS server which uses recent
kernel.
Using git bisect, I found it is caused by commit 4bdc33ed ("NFSDv4.2: Add NFS
v4.2 support to the NFS server").
1. dmesg (NFS boot failure case)
...
[2.040893] ADDRCONF(NETDEV_UP): eth0:
On Mon, Sep 09, 2013 at 06:03:55PM +0200, Guennadi Liakhovetski wrote:
> Add support for the Z clock on r8a7790, driving the four SoC's CA15 cores,
> and its parent - PLL0. This is required for CPUFreq support on this SoC.
>
> Signed-off-by: Guennadi Liakhovetski
Magnus, I think this needs a
On Mon, Sep 23, 2013 at 10:50:07AM +0200, Linus Walleij wrote:
> On Tue, Sep 17, 2013 at 7:10 PM, Guennadi Liakhovetski
> wrote:
> > On Tue, 17 Sep 2013, Linus Walleij wrote:
>
> >> > +/* R8A7790 has 6 banks with 32 GPIOs in each = 192 GPIOs */
> >> > +#define ROW_GROUP_A(r) ('Z' - 'A' + 1 +
... Please plan accordingly.
Changes since 20130924:
The drm-intel tree gained a conflict against the drm-intel-fixes tree.
The block tree gained a conflict against Linus' tree.
The akpm-current tree gained a conflict against the cgroup tree
Hi Linus !
Here are a few things for -rc2, this time it's all written by me so it
can only be perfect right ? :)
So we have the fix to call irq_enter/exit on the irq stack we've been
discussing, plus a cleanup on top to remove an unused (and broken)
stack limit tracking feature (well, make
Hi,
On Tue, Sep 24, 2013 at 8:33 PM, Feng Kan wrote:
> Hi all:
>
> I have some drivers like Queue Manager and co-processor driver that
> are used by other
> drivers like Ethernet. Would it be appropriate to locate these drivers
> under one folder under
> drivers/misc/arch_name/xxx.
drivers/misc
(2013/09/15 20:28), Hemant wrote:
> Hi Masami,
Hi, and sorry for replying so late. I missed this in my mailbox.
> On 09/04/2013 01:31 PM, Masami Hiramatsu wrote:
>> (2013/09/04 15:42), Namhyung Kim wrote:
>>> On Tue, 03 Sep 2013 13:06:55 +0530, Hemant Kumar wrote:
>>>
>>> [SNIP]
>>>
diff
On 09/25/2013 09:47 AM, Chen Gang wrote:
> On 09/25/2013 09:14 AM, Tejun Heo wrote:
>> On Wed, Sep 25, 2013 at 09:06:52AM +0800, Chen Gang wrote:
>>> OK, I see, the 'root cause' is: "you are not the related maintainer
>>> either", so it is really necessary for me to spend additional time
>>>
On 09/24/2013 05:11 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.63 release.
There are 40 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
On Tue, Sep 24, 2013 at 5:20 PM, Krzysztof Kozlowski
wrote:
> Hi,
>
> On pon, 2013-09-23 at 17:07 -0500, Seth Jennings wrote:
>> On Tue, Sep 17, 2013 at 02:59:24PM +0800, Bob Liu wrote:
>> > Mel mentioned several problems about zswap/zbud in thread "[PATCH v6
>> > 0/5] zram/zsmalloc promotion".
Bindings for LP3943 MFD, GPIO and PWM controller are added.
Cc: devicet...@vger.kernel.org
Cc: Lee Jones
Cc: Linus Walleij
Cc: Samuel Ortiz
Cc: Thierry Reding
Signed-off-by: Milo Kim
---
.../devicetree/bindings/gpio/gpio-lp3943.txt | 37 +
This is one of LP3943 MFD driver.
LP3943 is configurable as a GPIO expander, up to 16 GPIOs.
* Application note: how to configure LP3943 as a GPIO expander
http://www.ti.com/lit/an/snva287a/snva287a.pdf
* Supported GPIO controller operations
request, free, direction_input, direction_output,
This is the other of the LP3943 MFD driver.
LP3943 can be used as a PWM generator, up to 2 channels.
* Two PWM generators supported
* Supported PWM operations
request, free, config, enable and disable
* Pin assignment
A driver data, 'pin_used' is checked when a PWM is requested.
If the
LP3943 is an integrated device capable of driving 16 output channels.
It can be used for GPIO expander and PWM generators.
LP3493 registers are controlled via the I2C interface.
This patch-set consists of four parts - MFD, GPIO, PWM and documents.
Update from v3 to v4:
Move the driver
LP3943 has 16 output pins which can be used as GPIO expander and PWM generator.
* Regmap I2C interface for R/W LP3943 registers
* Atomic operations for output pin assignment
The driver should check whether requested pin is available or not.
If the pin is already used, pin request returns as
On 09/24/2013 05:13 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.13 release.
There are 110 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
atomic* value is signed value, and atomic* functions need also process
signed value (parameter value, and return value), so use 'long long'
instead of 'u64'.
After replacement, it will also fix a bug for atomic64_add_negative():
"u64 is never less than 0".
The modifications are:
in vim, use
From: "peter.guo"
Apply SDHCI_QUIRK_MULTIBLOCK_READ_ACMD12 for some SD Host Controller.
Apply SDHCI_QUIRK_NO_ENDATTR_IN_NOPDESC for some SD Host Controller.
Add O2Micro/BayHubTech SD Host Controller specified Init.
Signed-off-by: peter.guo
---
drivers/mmc/host/sdhci-pci.c | 129
On Tue, 24 Sep 2013 18:29:11 -0700 "Paul E. McKenney"
wrote:
> --- a/mm/mlock.c
> +++ b/mm/mlock.c
> @@ -736,6 +736,7 @@ static int do_mlockall(int flags)
>
> /* Ignore errors */
> mlock_fixup(vma, , vma->vm_start, vma->vm_end, newflags);
> +
On 09/24/2013 05:17 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.11.2 release.
There are 117 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
On Tue, Sep 24, 2013 at 06:49:55PM -0700, Paul E. McKenney wrote:
> Hello!
>
> This series updates RCU's idle entry/exit processing:
>
> 1.Remove redundant code from rcu_cleanup_after_idle().
>
> 2.Throttle rcu_try_advance_all_cbs() execution to avoid kbuild
> slowdowns.
>
> 3.
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
mm/memcontrol.c between commit b86278359484 ("memcg: stop using css id")
from the cgroup tree and commit 4c34cae8f277 ("revert "memcg: get rid of
soft-limit tree infrastructure"") from the akpm-current tree.
I fixed
On Tue, Sep 24, 2013 at 06:16:57PM -0700, Paul E. McKenney wrote:
> Hello!
>
> This series provides a few documentation updates:
>
> 1.Update stall-warning documentation to catch up with recent updates.
>
> 2.Add a reference to the new vmstat-avoidance patch to the
> file
On Tue, Sep 24, 2013 at 06:17:23PM -0700, Paul E. McKenney wrote:
> From: Michael Opdenacker
>
> Signed-off-by: Michael Opdenacker
> Signed-off-by: Paul E. McKenney
> ---
See comment below.
> Documentation/RCU/checklist.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
Hi all:
I have some drivers like Queue Manager and co-processor driver that
are used by other
drivers like Ethernet. Would it be appropriate to locate these drivers
under one folder under
drivers/misc/arch_name/xxx.
My other question is on common header files (belonging to Queue
Manager) but is
On Tue, Sep 24, 2013 at 8:20 AM, Al Viro wrote:
> On Tue, Sep 17, 2013 at 06:17:45AM +0800, zwu.ker...@gmail.com wrote:
>> From: Zhi Yong Wu
>>
>> The patchset is trying to introduce hot tracking function in
>> VFS layer, which will keep track of real disk I/O in memory.
>> By it, you will
From: "peter.guo"
- Change tuning_loop_counter check from not zero to less than zero
in function sdhci_execute_tuning; Becasue some host may need 40 times tuning,
but orginal code only think tuning times <= 39 is successfull.
- When Host Capability Reg (0x40) bit[43:40] is zero, retuning
From: "peter.guo"
Add O2Micor/BayHubTect SD Host Controller PCI Devices IDs in pci_ids.h.
Apply SDHCI_QUIRK_MULTIBLOCK_READ_ACMD12 for some SD Host Controller.
Apply SDHCI_QUIRK_NO_ENDATTR_IN_NOPDESC for some SD Host Controller.
Add O2Micro/BayHubTech SD Host Controller specified Init.
On Tue, 2013-09-24 at 15:22 -0700, Tim Chen wrote:
> We have incorporated various suggestions from Ingo for version 5 of this
> patchset
> and will like to have it merged if there are no objections.
>
> In this patchset, we introduce two categories of optimizations to read
> write semaphore.
On Wed, Sep 25, 2013 at 03:20:07AM +, Peter Guo wrote:
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -1700,6 +1700,11 @@
> #define PCI_DEVICE_ID_O2_82210x8221
> #define PCI_DEVICE_ID_O2_83200x8320
> #define PCI_DEVICE_ID_O2_8321
Hi,
> + if (gpio_is_valid(charger->pdata->status_gpio)) {
> + ret = devm_gpio_request(>dev,
> + charger->pdata->status_gpio,
> + name);
> + if (ret)
> +
Add Atmel PWM controller driver based on PWM framework.
This is the basic function implementation of Atmel PWM controller.
It can work with PWM based led and backlight.
Signed-off-by: Bo Shen
---
Changes in v4:
- check the return value of clk_prepare()
- change channel register size as
On Tue, Sep 24, 2013 at 08:18:16PM -0700, David Rientjes wrote:
> On Tue, 24 Sep 2013, Dave Jones wrote:
>
> > > case MPOL_BIND:
> > > - /* Fall through */
> > > case MPOL_INTERLEAVE:
> > > nodes = pol->v.nodes;
> > >
On Tue, 24 Sep 2013, Dave Jones wrote:
> >case MPOL_BIND:
> > - /* Fall through */
> >case MPOL_INTERLEAVE:
> >nodes = pol->v.nodes;
> >break;
>
> Any reason not to leave this ?
>
> "missing break" is the 2nd most common thing that coverity picks
On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin wrote:
> On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote:
>> On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote:
>> > [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ]
>> >
>> > Hi,
>> >
>> > saw your
On Tue, Sep 24, 2013 at 7:53 PM, Rob Herring wrote:
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
Hmm. Did you mean for me to pull the "devicetree-fixes" tag?
If so, please say so very explicitly. I don't want to have to search
Hi Jens,
Today's linux-next merge of the block tree got a conflict in
drivers/md/bcache/request.c between commit c0f04d88e46d ("bcache: Fix
flushes in writeback mode") from Linus' tree and commit 53027147e43c
("bcache: Prune struct btree_op") and dd879364df83 ("bcache: Break up struct
search")
On Tue, Sep 24, 2013 at 07:58:22PM -0700, David Rientjes wrote:
> case MPOL_BIND:
> -/* Fall through */
> case MPOL_INTERLEAVE:
> nodes = pol->v.nodes;
> break;
Any reason not to leave this ?
"missing break" is the 2nd most common thing that
There's a bug in the blktrace client where it will stop and tear down
all of the tracing instances for devices it's opened whether it
successfully completed the setup or not.
By starting multiple blktrace processes on the same device, it's possible
to permanently disable blktrace on that device.
On Tue, Sep 24, 2013 at 6:14 PM, Ming Lei wrote:
> It is better to save one line by below:
>
> parent = get_device(dev->parent);
>
Done.
>
> Reviewed-by: Ming Lei
Thank you!
--
Benson Leung
Software Engineer, Chrom* OS
ble...@chromium.org
--
To unsubscribe from this
Hi Manfred
IIUC after reivewing your patch and src code, does it seem
sem_otime lost the chance to be updated when calling
semctl_main/semctl_setval?
In old codes, even whendo_smart_update(sma, NULL, 0, 0, ),
the otime can be updated after several conditions checking.
On Tue, 24 Sep 2013
The put_device(dev) at the bottom of the loop of device_shutdown
may result in the dev being cleaned up. In device_create_release,
the dev is kfreed.
However, device_shutdown attempts to use the dev pointer again after
put_device by referring to dev->parent.
Copy the parent pointer instead to
mpol_to_str() should not fail. Currently, it either fails because the
string buffer is too small or because a string hasn't been defined for a
mempolicy mode.
If a new mempolicy mode is introduced and no string is defined for it,
just warn and return "unknown".
If the buffer is too small, just
Thank you for your whole work, firstly :-).
And your suggestion about testing (in our discussion) is also valuable
to me.
I need start LTP in q4. After referenced your suggestion, my first step
for using/learning LTP is not mainly for finding kernel issues, but for
testing kernel (to improve
On 09/25/2013 04:49 AM, Russ Knize wrote:
> From: Russ Knize
>
> f2fs_initxattrs() is called internally from within F2FS and should
> not call functions that are used by VFS handlers. This avoids
> certain deadlocks:
>
> - vfs_create()
> - f2fs_create() <-- takes an fs_lock
> -
Hi Linus,
Please pull these 3 DT fixes for 3.12.
Rob
The following changes since commit 4a10c2ac2f368583138b774ca41fac4207911983:
Linux 3.12-rc2 (2013-09-23 15:41:09 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
for you to
On 09/24/13 at 05:12pm, H. Peter Anvin wrote:
> On 09/24/2013 07:56 AM, Borislav Petkov wrote:
> > On Tue, September 24, 2013 2:45 pm, Dave Young wrote:
> >> Think again about this, how about 1:1 map them from a base address
> >> like -64G phy_addr -> (-64G + phy_addr), in this way we can avoid
>
On Mon, 23 Sep 2013, Jianguo Wu wrote:
> Use more appropriate NUMA_NO_NODE instead of -1 in all archs' module_alloc()
>
> Signed-off-by: Jianguo Wu
> Acked-by: Ralf Baechle
Acked-by: David Rientjes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Mon, 23 Sep 2013, Ming Liu wrote:
> After selecting a task to kill, the oom killer iterates all processes and
> kills all other user threads that share the same mm_struct in different
> thread groups.
>
> But in some extreme cases, the selected task happens to be a vfork child
> of init
On 09/24/13 at 04:56pm, Borislav Petkov wrote:
> On Tue, September 24, 2013 2:45 pm, Dave Young wrote:
> > Think again about this, how about 1:1 map them from a base address
> > like -64G phy_addr -> (-64G + phy_addr), in this way we can avoid
> > depending on the previous region size.
>
> Right,
On Mon, 2013-09-23 at 14:45 +0530, Anshuman Khandual wrote:
> On 09/21/2013 12:25 PM, Stephane Eranian wrote:
> > On Tue, Sep 10, 2013 at 4:06 AM, Michael Ellerman
> > wrote:
> >> >
> >> > On Fri, 2013-08-30 at 09:54 +0530, Anshuman Khandual wrote:
> >>> > > This patchset is the re-spin of
On Tue, 24 Sep 2013, Rob Landley wrote:
> On 09/24/2013 04:48:00 PM, Russell King - ARM Linux wrote:
> > Now, if you feel strongly about this, we _could_ introduce a
> > CONFIG_OLD_BINUTILS and give everyone their cake - but it will be
> > fragile. Not everyone will remember to get that right,
From: Rob Herring
Enabling the ARM DCC console and using without a JTAG connection will
simply hang the system. Since distros like to turn on all options, this
is a reoccurring problem to debug. We can do better by checking if
anything is attached and handling characters. There is no way to
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/intel_display.c between commit 67c72a122541
("drm/i915: preserve pipe A quirk in i9xx_set_pipeconf") from the
drm-intel-fixes tree and commit cf532bb25592 ("drm/i915: Move double wide
mode handling into
From: "Paul E. McKenney"
The rcu_try_advance_all_cbs() function returns a bool saying whether or
not there are callbacks ready to invoke, but rcu_cleanup_after_idle()
rechecks this regardless. This commit therefore uses the value returned
by rcu_try_advance_all_cbs() instead of making
From: "Paul E. McKenney"
If a non-lazy callback arrives on a CPU that has previously gone idle
with no non-lazy callbacks, invoke_rcu_core() forces the RCU core to
run. However, it does not update the conditions, which could result
in several closely spaced invocations of the RCU core, which in
From: "Paul E. McKenney"
The rcu_try_advance_all_cbs() function is invoked on each attempted
entry to and every exit from idle. If this function determines that
there are callbacks ready to invoke, the caller will invoke the RCU
core, which in turn will result in a pair of context switches. If
From: "Paul E. McKenney"
There is currently no way for kernel code to determine whether it
is safe to enter an RCU read-side critical section, in other words,
whether or not RCU is paying attention to the currently running CPU.
Given the large and increasing quantity of code shared by the idle
From: "Paul E. McKenney"
Commit e6b80a3b (rcu: Detect illegal rcu dereference in extended
quiescent state) exported the pre-existing rcu_is_cpu_idle() function
using EXPORT_SYMBOL(). However, this is inconsistent with the remaining
exports from RCU, which are all EXPORT_SYMBOL_GPL(). The
From: "Paul E. McKenney"
The old rcu_is_cpu_idle() function is just __rcu_is_watching() with
preemption disabled. This commit therefore renames rcu_is_cpu_idle()
to rcu_is_watching.
Signed-off-by: Paul E. McKenney
---
include/linux/rcupdate.h | 18 +-
include/linux/rcutiny.h
Hello!
This series updates RCU's idle entry/exit processing:
1. Remove redundant code from rcu_cleanup_after_idle().
2. Throttle rcu_try_advance_all_cbs() execution to avoid kbuild
slowdowns.
3. Throttle non-lazy-callback-induced invoke_rcu_core() invocations.
4.
On 09/25/2013 09:14 AM, Tejun Heo wrote:
> On Wed, Sep 25, 2013 at 09:06:52AM +0800, Chen Gang wrote:
>> OK, I see, the 'root cause' is: "you are not the related maintainer
>> either", so it is really necessary for me to spend additional time
>> resource on it :-(.
>
> Yeah, at least partly.
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Maydell
commit 99f2b130370b904ca5300079243fdbcafa2c708b upstream.
The SMAP register offsets in the versatile PCI controller code were
all off by four. (This didn't have any observable
This is the start of the stable review cycle for the 3.0.97 release.
There are 28 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 Fri Sep 27 00:05:34 UTC 2013.
Anything
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit 230aef7a6a23b6166bd4003bfff5af23c9bd381f upstream.
Normally when we haven't implemented an alignment handler for
a load or store instruction the process will be
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit 77dbd7a95e4a4f15264c333a9e9ab97ee27dc2aa upstream.
crypto_larval_lookup should only return a larval if it created one.
Any larval created by another entity must be processed
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit a1c781bb20ac1e03280e420abd47a99eb8bbdd3b upstream.
They are not implemented, and accessing them might trigger errors
Signed-off-by: Felix Fietkau
Signed-off-by: John W.
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 026d5b07c03458f9c0ccd19c3850564a5409c325 upstream.
Otherwise in some cases, EAPOL frames might be filtered during the
initial handshake, causing delays and assoc failures.
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Roger Pau Monne
commit 5f338d9001094a56cf87bd8a280b4e7ff953bb59 upstream.
With the current implementation, the callback in the tail of the list
can be added twice, because the check done in
From: Peter Zijlstra
We're going to deprecate and remove set_need_resched() for it will do
the wrong thing. Make an exception for RCU and allow it to use
resched_cpu() which will do the right thing.
Signed-off-by: Peter Zijlstra
Signed-off-by: Paul E. McKenney
---
kernel/rcutree.c| 15
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 83f72151352791836a1b9c1542614cc9bf71ac61 upstream.
Toshiba Satellite C870 shows interrupt problems occasionally when
certain mixer controls like "Mic Switch" is toggled.
From: "Paul E. McKenney"
This commit adds event traces to track all of rcu_nocb_kthread()'s
blocking and awakening.
Signed-off-by: Paul E. McKenney
---
include/trace/events/rcu.h | 4
kernel/rcutree_plugin.h| 15 ++-
2 files changed, 18 insertions(+), 1 deletion(-)
diff
From: "Paul E. McKenney"
This commit applies ACCESS_ONCE() to an outside-of-lock access to
->gp_flags. Although it is hard to imagine any sane compiler messing
this particular case up, the documentation benefits are substantial.
Plus the definition of "sane compiler" grows ever looser.
From: "Paul E. McKenney"
The event-tracing macros do not like bool tracing arguments, so this
commit makes them be of type char. This change has the knock-on effect
of making it illegal to pass a pointer into one of these arguments, so
also change rcutiny's first call to trace_rcu_batch_end()
From: "Paul E. McKenney"
One way to distinguish between NOCB and non-NOCB rcu_callback trace
events is that the former always print zero for the lazy and non-lazy
queue lengths. Unfortunately, this also means that we cannot see the NOCB
queue lengths. This commit therefore accesses the NOCB
From: "Paul E. McKenney"
This commit adds tracing to the normal grace-period request points.
These are rcu_gp_cleanup(), which checks for the need for another
grace period at the end of the previous grace period, and
rcu_start_gp_advanced(), which restarts RCU's state machine after
an idle
From: "Paul E. McKenney"
This commit improves grace-period start logic by checking ->gp_flags
under the lock and by issuing a warning if a grace period is already
in progress.
Signed-off-by: Paul E. McKenney
---
kernel/rcutree.c | 17 -
1 file changed, 12 insertions(+), 5
From: "Paul E. McKenney"
This commit adds tracing to the rcu_gp_kthread() function in order to
help trace down hangs potentially involving this kthread.
Reported-by: Clark Williams
Reported-by: Carsten Emde
Signed-off-by: Paul E. McKenney
---
include/trace/events/rcu.h | 28
From: "Paul E. McKenney"
Spurious wakeups in the force-quiescent-state loop in rcu_gp_kthread()
cause the timeout to be recalculated, which would prevent rcu_gp_fqs()
from ever being called. This would in turn would prevent the grace period
from ever ending for as long as there was at least one
Hello!
This series contains updates to RCU's grace-period processsing, mostly
to improve debuggability of RCU itself.
1. Add consistency checks to the grace-period initialization logic.
2. Prevent spurious-wakeup DoS attack on rcu_gp_kthread.
3. Flag lockless accesses to
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Anand Avati
commit d331a415aef98717393dda0be69b7947da08eba3 upstream.
Calls like setxattr and removexattr result in updation of ctime.
Therefore invalidate inode attributes to force a refresh.
From: "Paul E. McKenney"
Lost wakeups from call_rcu() to the rcuo kthreads can result in hangs
that are difficult to diagnose. This commit therefore adds tracing to
help pin down the cause of these hangs.
Reported-by: Clark Williams
Reported-by: Carsten Emde
Signed-off-by: Paul E. McKenney
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Maxim Patlasov
commit 4a4ac4eba1010ef9a804569058ab29e3450c0315 upstream.
The patch fixes a race between ftruncate(2), mmap-ed write and write(2):
1) An user makes a page dirty via mmap-ed
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Shawn Nematbakhsh
commit c8476fb855434c733099079063990e5bfa7ecad6 upstream.
If a USB controller with XHCI_RESET_ON_RESUME goes to runtime suspend,
a reset will be performed upon runtime
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Libin
commit a8f531ebc33052642b4bd7b812eedf397108ce64 upstream.
In collapse_huge_page() there is a race window between releasing the
mmap_sem read lock and taking the mmap_sem write lock, so
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 2c4283ca7cdcc6605859c836fc536fcd83a4525f upstream.
In dt282x_ai_insn_read() we call this macro like:
wait_for(!mux_busy(), comedi_error(dev, "timeout\n"); return -ETIME;);
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sarah Sharp
commit 52fb61250a7a132b0cfb9f4a1060a1f3c49e5a25 upstream.
The xHCI platform driver calls into usb_add_hcd to register the irq for
its platform device. It does not want the xHCI
On Tue, Sep 24, 2013 at 08:36:56PM +0200, Thomas Meyer wrote:
> Is there such a thing?
In mainline, AFAIK no. The vserver patchset, on the other hand, adds a new
xattr, iunlink, that copies the whole file when needed. That works on most
filesystems.
That's quite a hack, though, and I think
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Shawn Nematbakhsh
commit c8476fb855434c733099079063990e5bfa7ecad6 upstream.
If a USB controller with XHCI_RESET_ON_RESUME goes to runtime suspend,
a reset will be performed upon runtime
1 - 100 of 1898 matches
Mail list logo
