On Thu, 2014-03-20 at 12:01 -0300, Glauber Costa wrote:
> On Wed, Mar 19, 2014 at 6:42 AM, wrote:
> > In consolidated environments, when there are multiple virtual machines (VMs)
> > running on one CPU core, timekeeping will be a problem to the guest OS.
> > Here, I report my findings about
Xiubo Li (3):
pwm: ftm-pwm: Clean up the code.
pwm: ftm-pwm: Convert to direct regmap API usage.
pwm: ftm-pwm: Add big-endian support
drivers/pwm/pwm-fsl-ftm.c | 96 ++-
1 file changed, 53 insertions(+), 43 deletions(-)
--
1.8.4
--
To
Signed-off-by: Xiubo Li
---
drivers/pwm/pwm-fsl-ftm.c | 83 +--
1 file changed, 44 insertions(+), 39 deletions(-)
diff --git a/drivers/pwm/pwm-fsl-ftm.c b/drivers/pwm/pwm-fsl-ftm.c
index 4a4ad58..5d999c1 100644
--- a/drivers/pwm/pwm-fsl-ftm.c
+++
Now for the following scenarios:
SoC | CPU | FTM-PWM | 'big-endian' property is needed?
-||-|-
Vybird | LE| LE| No
LS1 | LE| BE| Yes
LS2 | LE| LE| No
Signed-off-by: Xiubo Li
---
drivers/pwm/pwm-fsl-ftm.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/drivers/pwm/pwm-fsl-ftm.c b/drivers/pwm/pwm-fsl-ftm.c
index 420169e..4a4ad58 100644
--- a/drivers/pwm/pwm-fsl-ftm.c
+++ b/drivers/pwm/pwm-fsl-ftm.c
@@ -21,11
This fix the fsl usb gadget driver in a way that the usb device
will be only "pulled up" on requests only when vbus is powered
Signed-off-by: Suresh Gupta
---
Changes from previous version:
* fixed checkpatch error
drivers/usb/gadget/fsl_udc_core.c | 4
1 file changed, 4 insertions(+)
On 03/20/2014 05:02 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.13.7 release.
There are 149 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
cpufreq_notify_transition() and cpufreq_notify_post_transition() shouldn't be
called directly by cpufreq drivers anymore and so these should be marked static.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 6 ++
include/linux/cpufreq.h | 4
2 files changed, 2
From: "Srivatsa S. Bhat"
Whenever we change the frequency of a CPU, we call the PRECHANGE and POSTCHANGE
notifiers. They must be serialized, i.e. PRECHANGE and POSTCHANGE notifiers
should strictly alternate, thereby preventing two different sets of PRECHANGE or
POSTCHANGE notifiers from
CPUFreq core has new infrastructure that would guarantee serialized calls to
target() or target_index() callbacks. These are called
cpufreq_freq_transition_begin() and cpufreq_freq_transition_end().
This patch converts existing drivers to use these new set of routines.
Signed-off-by: Viresh
Whenever we change the frequency of a CPU, we call the PRECHANGE and POSTCHANGE
notifiers. They must be serialized, i.e. PRECHANGE and POSTCHANGE notifiers
should strictly alternate, thereby preventing two different sets of PRECHANGE or
POSTCHANGE notifiers from interleaving arbitrarily.
The
于 2014年03月19日 21:23, y...@karo-electronics.de 写道:
+ /* Set up swap_block_mark, must be set before the gpmi_set_geometry() */
+ if (!of_property_read_bool(this->dev->of_node, "fsl,no-blockmark-swap"))
+ this->swap_block_mark = !GPMI_IS_MX23(this);
Our ROM guy had
On Thu, Mar 20, 2014 at 09:13:59AM +0100, Jan Kara wrote:
> On Thu 20-03-14 10:09:54, Minchan Kim wrote:
> > Hello,
> >
> > On Wed, Mar 19, 2014 at 11:12:02AM +0100, Jan Kara wrote:
> > > On Wed 19-03-14 09:49:18, Minchan Kim wrote:
> > > > On Tue, Mar 18, 2014 at 11:07:50AM -0700, John Stultz
On 03/20/2014 05:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.34 release.
There are 85 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
Hi Linus,
Some final few intel fixes, all regressions, all stable cc, and one exynos
oops fixer, the biggest is probably the intel display error irqs one, but
it seems to fix a few crashes on startup, and one use after free in drm
core.
Dave.
The following changes since commit
On 03/20/2014 05:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.84 release.
There are 35 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 Thu, Mar 20, 2014 at 9:55 PM, Srikar Dronamraju
wrote:
>
> I reverted commits 99b60ce6 and b0c29f79. Then applied the patches in
> the above url. The last one had a reject but it was pretty
> straightforward to resolve it. After this, specjbb completes.
>
> So reverting and applying v3 3/4 and
On Thu, 20 Mar 2014 11:54:58 +0100, Tomasz Figa wrote:
> On 20.03.2014 11:22, Cho KyongHo wrote:
> > On Wed, 19 Mar 2014 16:14:57 +0100, Tomasz Figa wrote:
> >> On 19.03.2014 14:20, Tomasz Figa wrote:
> >>> On 19.03.2014 01:39, Cho KyongHo wrote:
> On Tue, 18 Mar 2014 15:26:48 +0100, Tomasz
After the following commit:
commit b75ef8b44b1cb95f5a26484b0e2fe37a63b12b44
Author: Mathieu Desnoyers
Date: Wed Aug 10 15:18:39 2011 -0400
Tracepoint: Dissociate from module mutex
The following functions became unnecessary:
- tracepoint_probe_register_noupdate,
-
Register/unregister tracepoint probes with struct tracepoint pointer
rather than tracepoint name.
This change, which vastly simplifies tracepoint.c, has been proposed by
Steven Rostedt.
>From this point on, the tracers need to pass a struct tracepoint pointer
to probe register/unregister. A
Here is v7 of the tracepoint register/unregister API simplification,
submitted for 3.15.
Changes since v1:
- Adapt ftrace/perf callers,
- Update tracepoint.h macro,
- Build tested.
Changes since v2:
- Introduce for_each_tracepoint() iterator to allow listing the
currently loaded tracepoints,
On Thu, 20 Mar 2014, Naoya Horiguchi wrote:
> On Thu, Mar 20, 2014 at 09:47:04PM -0400, Sasha Levin wrote:
> > On 02/10/2014 04:44 PM, Naoya Horiguchi wrote:
> > >swapin_walk_pmd_entry() is defined as pmd_entry(), but it has no code
> > >about pmd handling (except
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, March 20, 2014 9:33 PM
> To: Gupta Suresh-B42813
> Cc: ba...@ti.com; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2] USB: Gadget: fsl driver pullup fix
>
> On
If the glibc xattr.h header is included after the uapi header,
compilation fails due to an enum re-using a #define from the
uapi header. Protect against this by guarding the define and
enum inclusions against each other.
(See https://lists.debian.org/debian-glibc/2014/03/msg00029.html
and
>
> Ok, so a big reason why this patch doesn't apply cleanly after reverting
> is because *most* of the changes were done at the top of the file with
> regards to documenting the ordering guarantees, the actual code changes
> are quite minimal.
>
> I reverted commits 99b60ce6 (documentation) and
Add remove_linear_migration_ptes_from_nonlinear(), to fix an interesting
little include/linux/swapops.h:131 BUG_ON(!PageLocked) found by trinity:
indicating that remove_migration_ptes() failed to find one of the
migration entries that was temporarily inserted.
The problem comes from
On Thu, 20 Mar 2014 11:44:50 +0100, Tomasz Figa wrote:
> On 20.03.2014 11:03, Cho KyongHo wrote:
> > On Wed, 19 Mar 2014 13:08:42 +0100, Tomasz Figa wrote:
> >> On 19.03.2014 10:01, Sachin Kamat wrote:
> >>> On 19 March 2014 14:29, Cho KyongHo wrote:
> On Tue, 18 Mar 2014 16:14:53 +0100,
On Thu, 20 Mar 2014, Sasha Levin wrote:
> On 03/20/2014 09:51 AM, Dave Jones wrote:
> > On Wed, Mar 19, 2014 at 10:00:29PM -0700, Hugh Dickins wrote:
> >
> > > > This might be collateral damage from the swapops thing, I guess we
> > won't know until
> > > > that gets fixed, but I thought I'd
fix some coding style in drivers/staging/iio.
Signed-off-by: Jimmy Li
---
drivers/staging/iio/accel/adis16220_core.c |3 ++-
drivers/staging/iio/accel/sca3000_core.c |3 ++-
drivers/staging/iio/adc/ad7192.c |3 ++-
drivers/staging/iio/adc/ad7606_core.c |2 +-
2014-03-21 13:27 GMT+09:00 Greg KH :
> On Fri, Mar 21, 2014 at 01:15:23PM +0900, Daeseok Youn wrote:
>>
>> Replace OS_kmalloc/OS_kfree with kmalloc/kfree.
>
> You should replace it with kzalloc, not kmalloc, as OS_kmalloc() zeroed
> out the allocated data:
I think some case does not need to get
On Fri, Mar 21, 2014 at 01:15:23PM +0900, Daeseok Youn wrote:
>
> Replace OS_kmalloc/OS_kfree with kmalloc/kfree.
You should replace it with kzalloc, not kmalloc, as OS_kmalloc() zeroed
out the allocated data:
> -static inline void *
> -OS_kmalloc (size_t size)
> -{
> -char *ptr =
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/x86/kernel/cpu/perf_event_intel_uncore.c between commit 2c666adacc9e
("x86, intel, uncore: Fix CPU hotplug callback registration") from Linus'
tree and commit 411cf180fa00 ("perf/x86/uncore: fix initialization of
cpumask")
Replace OS_kmalloc/OS_kfree with kmalloc/kfree.
And also some allocation doesn't need to use GFP_DMA
so just use GFP_KERNEL.
c4_new() function is never called, remove it.
Signed-off-by: Daeseok Youn
---
v2: fix subject and comment correctly.
I'm not sure what GFP_DMA use correctly for
On 21/03/2014 11:51, Suravee Suthikulpanit wrote:
Bjorn,
On a typical AMD system, there are two types of host bridges:
* PCI Root Complex Host bridge (e.g. RD890, SR56xx, etc.)
* CPU Host bridge
Here is an example from a 2 sockets system:
$ lspci
[]
The host bridge 00:00.0 is basically the
Bjorn,
On a typical AMD system, there are two types of host bridges:
* PCI Root Complex Host bridge (e.g. RD890, SR56xx, etc.)
* CPU Host bridge
Here is an example from a 2 sockets system:
$ lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI RD890 PCI to PCI
bridge (external gfx0
On 03/10/2014 04:42 PM, Sudeep Holla wrote:
> Hi Anshuman,
>
> On 07/03/14 06:14, Anshuman Khandual wrote:
>> On 03/07/2014 09:36 AM, Anshuman Khandual wrote:
>>> On 02/19/2014 09:36 PM, Sudeep Holla wrote:
From: Sudeep Holla
This patch removes the redundant sysfs cacheinfo code
On 21/03/2014 06:07, Bjorn Helgaas wrote:
[+cc linux-pci, Myron, Suravee, Kim, Aravind]
On Thu, Mar 13, 2014 at 5:43 AM, Daniel J Blueman wrote:
For systems with multiple servers and routed fabric, all northbridges get
assigned to the first server. Fix this by also using the node reported
Commit-ID: 9e6f450f946d35d585798da268d45c679632fe05
Gitweb: http://git.kernel.org/tip/9e6f450f946d35d585798da268d45c679632fe05
Author: Andy Lutomirski
AuthorDate: Thu, 20 Mar 2014 18:57:18 -0700
Committer: H. Peter Anvin
CommitDate: Thu, 20 Mar 2014 20:20:08 -0700
x86, vdso: Move more
Commit-ID: 3c1b63b9e4862fb16352a0646439c2dd6d9e0e5c
Gitweb: http://git.kernel.org/tip/3c1b63b9e4862fb16352a0646439c2dd6d9e0e5c
Author: Andy Lutomirski
AuthorDate: Thu, 20 Mar 2014 18:57:19 -0700
Committer: H. Peter Anvin
CommitDate: Thu, 20 Mar 2014 20:20:18 -0700
x86, vdso: Finish
Currently when an empty PT_NOTE is detected, vmcore initialization
fails. It sounds too harsh. Because PT_NOTE could be empty, for example,
one offlined a cpu but never restarted kdump service, and after crash,
PT_NOTE program header is there but no data contains. It's better to
warn about the
On Thu, 20 Mar 2014 13:39:44 -0700
Sebastian Hesselbarth wrote:
> This is a small patch set for SMP support on Marvell Berlin BG2
> and recently provided BG2Q. Nothing spectacular, as it basically
> copies SMP holding pen mechanism from mach-prima2 and plat-versatile
> with minor Berlin specific
Linus,
Vaibhav Nagarnaik discovered that since 3.10 a clean up patch made the
array index in the trace event format bogus. He supplied an elegant solution
that uses __stringify() and also removes the need for the event_storage
and event_storage_mutex that cuts off a few K of overhead from
the
Hi Mark Brown,
On 03/20/2014 09:47 PM, Mark Brown wrote:
On Thu, Mar 20, 2014 at 10:37:53AM +0800, Bo Shen wrote:
For this, in my mind, I think we need add following parameters in DT.
1. sysclk_src_from_fll --> we need do nothing.
No, how would this work? If nothing else the FLL needs
On 2014/03/20, 11:51 AM, "Oleg Nesterov" wrote:
>On 03/19, Oleg Nesterov wrote:
>>
>> OK, I'll try to test/cleanup/resend tomorrow.
>
>Cough. Still un-tested, sorry. I will test it somehow and report,
>but I'd like to send this for review right now.
>
>Because I simply can't decide what the new
Yes. It was already noticed by Joe Perches.
I will send it again.
Thanks.
Daeseok Youn.
2014-03-21 11:35 GMT+09:00, Greg KH :
> On Fri, Mar 21, 2014 at 10:41:39AM +0900, Daeseok Youn wrote:
>>
>> Replace kmalloc/kfree with OS_kmalloc/OS_kfree.
>
> I think you mean this the other way around,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Rafael,
Here goes bugfix devfreq patch.
Recent patchset of device-tree support / exynos driver updates is omitted in
this pull request
as there could be further updates on the patchset.
Cheers,
MyungJoo
The following changes since commit
On Fri, Mar 21, 2014 at 10:41:39AM +0900, Daeseok Youn wrote:
>
> Replace kmalloc/kfree with OS_kmalloc/OS_kfree.
I think you mean this the other way around, right?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Commit 5df529d440("regulator: core: Reduce busy-wait looping")
can also be used in regulator_do_set_voltage.
Signed-off-by: Jonghwan Choi
---
drivers/regulator/core.c | 39 +--
1 file changed, 33 insertions(+), 6 deletions(-)
diff --git
于 2014年03月21日 01:02, Jay Vosburgh 写道:
> Zheng Li wrote:
>
>> Except bond mode 1, in other bond modes, inactive slaves should keep
>> inactive flag to 1 to refuse to receive broadcast packets. Now, active
>> slave send broadcast packets (for example ARP requests) which will
>> arrive inactive
On Thu, 20 Mar 2014 17:02:39 -0400
Jeff Layton wrote:
> Eventually the server should just allow the read to complete even if
> the client doesn't respond to the oplock break. It has to since clients
> can suddenly drop off the net while holding an oplock. That should
> allow everything to
Hi Tomi,
Today's linux-next merge of the omap_dss2 tree got a conflict in
drivers/video/Makefile between commit f167a64e9d67 ("video / output: Drop
display output class support") from the pm tree and commit 844901baede6
("video: move fbdev to drivers/video/fbdev") from the omap_dss2 tree.
I
On Thu, 20 Mar 2014 19:53:46 -0400
Jeff Layton wrote:
> Wait...why does the work running on CPU1 end up blocked on down_read()?
> Is it really getting stuck on the down_write you mention?
>
rwsems are fair locks. Readers will not block on a reader lock unless
there's a writer waiting. That's
some more help to
> debug this. I built aa11fc58dc with the config you supplied and
> booted it on qemu with no real issues (it didn't boot all the way
> because the config doesn't include a driver for my root disk, but
> that's to be expected).
>
> The dmesg you supplie
Hi Ben,
On 03/21/2014 12:30 AM, Benjamin LaHaise wrote:
> On Thu, Mar 20, 2014 at 10:32:07AM -0400, Dave Jones wrote:
>> On Thu, Mar 20, 2014 at 01:46:25PM +0800, Gu Zheng wrote:
>>
>> > diff --git a/fs/aio.c b/fs/aio.c
>> > index 88ad40c..e353085 100644
>> > --- a/fs/aio.c
>> > +++
This patch introduces fi->i_sem to protect fi's info that includes xattr_ver,
pino, i_nlink.
This enables to remove i_mutex during f2fs_sync_file, resulting in performance
improvement when a number of fsync calls are triggered from many concurrent
threads.
Signed-off-by: Jaegeuk Kim
---
This patch should resolve the following possible bug.
RECLAIM_FS-ON-W at:
mark_held_locks+0xb9/0x140
lockdep_trace_alloc+0x85/0xf0
__kmalloc+0x53/0x1d0
read_all_xattrs+0x3d1/0x3f0 [f2fs]
f2fs_getxattr+0x4f/0x100 [f2fs]
f2fs_get_acl+0x4c/0x290 [f2fs]
get_acl+0x4f/0x80
If multiple redundant fsync calls are triggered, we don't need to write its
node pages with fsync mark continuously.
So, this patch adds FI_NEED_FSYNC to track whether the latest node block is
written with the fsync mark or not.
If the mark was set, a new fsync doesn't need to write a node block.
It's a declaration of a nonexistent symbol. We can get rid of the
64-bit versions, too, but that's more intrusive.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/vdso.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/include/asm/vdso.h b/arch/x86/include/asm/vdso.h
index
Patch 1 fixes the Xen build. Patch 2 fixes an embarrassment.
Andy Lutomirski (2):
x86: Move more vdso definitions into vdso.h
x86: Finish removing VDSO32_PRELINK
arch/x86/include/asm/vdso.h | 38 +-
arch/x86/vdso/vdso.S | 2 +-
This fixes the Xen build and gets rid of a silly header file.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/vdso.h | 38 ++
arch/x86/vdso/vdso.S | 2 +-
arch/x86/vdso/vdso32-setup.c | 7 ---
arch/x86/vdso/vdso32.S | 2 +-
omm: trinity-c61 Tainted: GW
3.14.0-rc7-next-20140320-sasha-00015-gd752393-dirty #261
[ 2857.039854] task: 88080f91b000 ti: 8807fd106000 task.ti:
8807fd106000
[ 2857.040328] RIP: 0010:[] []
munlock_vma_pages_range+0x93/0x1d0
[ 2857.040328] RSP: :8807fd107e08 EFL
() as swapin_walk_pte_entry().
Signed-off-by: Naoya Horiguchi
This patch seems to generate:
[ 305.267354] =
[ 305.268051] [ INFO: inconsistent lock state ]
[ 305.268678] 3.14.0-rc7-next-20140320-sasha-00015-gd752393-dirty #261
Tainted: GW
[ 305.269992
Quoting Sylwester Nawrocki (2014-03-20 05:42:33)
> Hi Maxime,
>
> On 06/03/14 14:45, Maxime Coquelin wrote:
> > Hi Sylwester,
> >
> > I like the principle of your implementation, but I have two questions:
> > 1 - How can we manage PM with this solution, as the parent/rate will
> >
Replace kmalloc/kfree with OS_kmalloc/OS_kfree.
And also some allocation doesn't need to use GFP_DMA
so just use GFP_KERNEL.
c4_new() function is never called, remove it.
Signed-off-by: Daeseok Youn
---
I'm not sure what GFP_DMA use correctly for km{,z}alloc().
Please review this.
And this
Hi,
I've got kernel panic on my box which works as FibreChannel initiator.
I was able to reproduce this panic by setting dev_loss_tmo=2 and
enabling/disabling ports every 5 seconds on the switch in 5 minutes. I
added some debug points in the kernel code and that's what I've got so far:
1.
On 03/14/2014 04:11 PM, Stanislav Meduna wrote:
Hi,
following scenario:
- a Freescale i.MX28 machine
- RS232 AUART looped back Rx - Tx or two different ports cross-connected
- a test program sending data in one thread and receiving in the other:
thread A periodically sends "Quick brown fox
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Weiner
commit 27329369c9ecf37771b2a65202cbf5578cff3331 upstream.
Jan Stancek reports manual page migration encountering allocation
failures after some pages when there is still
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit f5ddcbbb40aa0ba7fbfe22355d287603dbeeaaac ]
This patch fixes two bugs in fastopen :
1) The tcp_sendmsg(..., @size) argument was ignored.
Code was relying
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 15c34a760630ca2c803848fba90ca0646a9907dd upstream.
Global quota files are accessed from different nodes. Thus we cannot
cache offset of quota structure in the quota file
This is the start of the stable review cycle for the 3.13.7 release.
There are 149 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 Sun Mar 23 00:03:54 UTC 2014.
Anything
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Vlastimil Babka
commit 9050d7eba40b3d79551668f54e68fd6f51945ef3 upstream.
Daniel Borkmann reported a VM_BUG_ON assertion failing:
[ cut here ]
kernel BUG at
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
commit ce48225fe3b1b0d1fc9fceb96ac3d8a879e45114 upstream.
Commit 0eef615665ed ("memcg: fix css reference leak and endless loop in
mem_cgroup_iter") got the interaction with the
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 1b56e98990bcdbb20b9fab163654b9315bf158e8 upstream.
Signed-off-by: Al Viro
Signed-off-by: Greg Kroah-Hartman
---
fs/ocfs2/file.c |8
1 file changed, 4
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Minchan Kim
commit db5d711e2db776f18219b033e5dc4fb7e4264dd7 upstream.
zram_meta_alloc could fail so caller should check it. Otherwise, your
system will hang.
Signed-off-by: Minchan Kim
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandre Bounine
commit 04379dffdd4da820d51a1566ad2e86f3b1ad97ed upstream.
This patch is a modification of the patch originally proposed by
Xiaotian Feng :
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Fernando Luis Vazquez Cao
[ Upstream commit 6671b2240c54585d4afb5286a29f1569fe5e40a8 ]
Even though only the outer vlan tag can be HW accelerated in the transmission
path, in the TUN/TAP
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Vlad Yasevich
[ Upstream commit 8b4703e9bd1172a5f8244276ebb94302e6153e26 ]
Macvlan currently inherits all of its features from the lower
device. When lower device disables offload support,
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Duan Jiong
[ Upstream commit feff9ab2e7fa773b6a3965f77375fe89f7fd85cf ]
If the neigh table's entries is less than gc_thresh1, the function
will return directly, and the reachabletime will not
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Toshiaki Makita
[ Upstream commit 8d0d21f4053c07714802cbe8b1fe26913ec296cc ]
Even if we create a stacked vlan interface such as veth0.10.20, it sends
single tagged frames (tagged with only
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Emmanuel Grumbach
commit 1d147bfa64293b2723c4fec50922168658e613ba upstream.
There is a race between the TX path and the STA wakeup: while
a station is sleeping, mac80211 buffers frames until
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: George McCollister
commit 791c9e0292671a3bfa95286bb5c08129d8605618 upstream.
dequeue_entity() is called when p->on_rq and sets se->on_rq = 0
which appears to guarentee that the !se->on_rq
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 1bf4bbb4024dcdab5e57634dd8ae1072d42a53ac upstream.
Improves reliability of wifi connections with WPA, since authentication
frames are prioritized over normal traffic and
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit 91a48a2e85a3b70ce10ead34b4ab5347f8d215c9 ]
Currently the UFO fragmentation process does not correctly handle inner
UDP frames.
(The following tcpdumps
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Edward Cree
[ Upstream commit 8f355e5cee63c2c0c145d8206c4245d0189f47ff ]
If we receive a PTP event from the NIC when we haven't set up PTP state
in the driver, we attempt to read through a
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit 916e4cf46d0204806c062c8c6c4d1f633852c5b6 ]
Currently we generate a new fragmentation id on UFO segmentation. It
is pretty hairy to identify the correct
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit cb664981607a6b5b3d670ad57bbda893b2528d96 upstream.
When a VHT network uses 20 or 40 MHz as per the HT operation
information, the channel center frequency segment 0 field
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 963a1852fbac4f75a2d938fa2e734ef1e6d4c044 upstream.
The MLME code in mac80211 must track whether or not the AP changed
bandwidth, but if there's no change while tracking
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hiroaki SHIMODA
[ Upstream commit 724b9e1d75ab3401aaa081bd4efb440c1b3509db ]
The allocated child qdisc is not freed in error conditions.
Defer the allocation after user configuration turns
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit 10ddceb22bab11dab10ba645c7df2e4a8e7a5db5 ]
when ip_tunnel process multicast packets, it may check if the packet is looped
back packet though
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jason Wang
[ Upstream commit 0e7ede80d929ff0f830c44a543daa1acd590c749 ]
We should alloc big buffers also when guest can receive UFO
packets to let the big packets fit into guest rx buffer.
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hans Schillstrom
[ Upstream commit accfe0e356327da5bd53da8852b93fc22de9b5fc ]
The commit 9195bb8e381d81d5a315f911904cdf0cfcc919b8 ("ipv6: improve
ipv6_find_hdr() to skip empty routing
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Chan
[ Upstream commit d7b95315cc7f441418845a165ee56df723941487 ]
Redefine the RXD_ERR_MASK to include only relevant error bits. This fixes
a customer reported issue of randomly
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Vineet Gupta
commit b053940df41808f0f27568eb36820d10a8a987f8 upstream.
This fixes a subtle issue with cache flush which could potentially cause
random userspace crashes because of stale
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Avinash Patil
commit 4f7ba432202c8330cc03ab959c6228d0de5dc4a3 upstream.
Write io memory to clean PCIe buffer only when PCIe device is
present else this results into crash because of invalid
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
[ Upstream commit ec0223ec48a90cb605244b45f7c62de856403729 ]
RFC4895 introduced AUTH chunks for SCTP; during the SCTP
handshake RANDOM; CHUNKS; HMAC-ALGO are negotiated
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Sujith Manoharan
commit b3050248c167871ca52cfdb2ce78aa2460249346 upstream.
The minimum CCA power threshold values have to be adjusted
for existing cards to be in compliance with new
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 21f8aaee0c62708654988ce092838aa7df4d25d8 upstream.
We check tid->sched without a lock taken on ath_tx_aggr_sleep(). That
is race condition which can result of doing
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Amitkumar Karwar
commit c99b1861c232e1f641f13b8645e0febb3712cc71 upstream.
While preparing association request, intersection of device's HT
capability information and corresponding fields
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Amitkumar Karwar
commit 1c97560f6d751a620978504a4a888c631192b71a upstream.
We are sending sleep confirm done interrupt in the middle of
sleep handshake. There is a corner case when Tx done
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Bing Zhao
commit adb07df1e039e9fe43e66aeea8b4771f83659dbb upstream.
As many Surface Pro I & II users have found out, the mwifiex_usb
doesn't support usb autosuspend, and it has caused some
1 - 100 of 2032 matches
Mail list logo
