Dear Friend,
I would like to discuss a very important issue with you. I am writing to find
out if this is your valid email. Please, let me know if this email is valid
Kind regards
Adrien Saif
Attorney to Quatif Group of Companies
On Sat, Apr 15, 2017 at 12:27:31AM +0200, Rafael J. Wysocki wrote:
> On Friday, April 14, 2017 10:22:49 AM Lukas Wunner wrote:
> > Below is a tentative patch which moves PME polling to a freezable
> > workqueue, so it is frozen before the host bridge is suspended.
> > Geert, Laurent, could you test
The following changes since commit a71c9a1c779f2499fb2afc0553e543f18aff6edf:
Linux 4.11-rc5 (2017-04-02 17:23:54 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/
tags/tty-4.11-rc7
for you to fetch changes up to a8983d01f9b7d600fbd
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit 510d86362a27577f5ee23f46cfb354ad49731e61 upstream.
The SAVE_SOME macro is used to save the execution context on all
exceptions.
If an exception occurs while executing user
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 22547c4cc4fe20698a6a85a55b8788859134b8e4 upstream.
On a system with a defective USB device connected to an USB hub,
an endless sequence of port connect events was observed.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit dda45f701c9d7ad4ac0bb446e3a96f6df9a468d9 upstream.
When enterring interrupt context via handle_int or except_vec_vi, switch
to the irq_stack of the current CPU if it is not
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 93c7018ec16bb83399dd4db61c361a6d6aba0d5a upstream.
We might kill TX or RX urb during rt2x00usb_flush_entry(), what can
cause anchor list corruption like shown below:
[
On Sat, Apr 15, 2017 at 06:26:22PM +0300, Jarkko Sakkinen wrote:
> From: "Maciej S. Szmigiero"
>
> Since commit 1107d065fdf1 ("tpm_tis: Introduce intermediate layer for
> TPM access") Atmel 3203 TPM on ThinkPad X61S (TPM firmware version 13.9)
> no longer works. The initialization proceeds fine
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit dda45f701c9d7ad4ac0bb446e3a96f6df9a468d9 upstream.
When enterring interrupt context via handle_int or except_vec_vi, switch
to the irq_stack of the current CPU if it is not
On Sat, Apr 15, 2017 at 07:06:06PM -0500, Nisal Menuka wrote:
> According to ARM, these errata exist only in a version of Cortex-A8
> (r2p0) which was never built. Therefore, I believe there are no platforms
> where this workaround should be enabled.
> link :http://infocenter.arm.com/help/index.jsp
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jack Morgenstein
commit 7c3945bc2073554bb2ecf983e073dee686679c53 upstream.
Save the qp context flags byte containing the flag disabling vlan stripping
in the RESET to INIT qp transition, rather
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 22547c4cc4fe20698a6a85a55b8788859134b8e4 upstream.
On a system with a defective USB device connected to an USB hub,
an endless sequence of port connect events was observed.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit 8f68d591d4765b2e1ce9d916ac7bc5583285c4ad upstream.
On Baytrail, we manually calculate busyness over the evaluation interval
to avoid issues with miscaluations with RC6 enabl
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit 3d3d18f086cdda72ee18a454db70ca72c6e3246c upstream.
The rcu_barrier() takes the cpu_hotplug mutex which itself is not
reclaim-safe, and so rcu_barrier() is illegal from insi
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Kenneth Graunke
commit 0f5418e564ac6452b9086295646e602a9addc4bf upstream.
This patch makes the I915_PARAM_HAS_EXEC_CONSTANTS getparam return 0
(indicating the optional feature is not supported
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Marshall
commit 05973c2efb40122f2a9ecde2d065f7ea5068d024 upstream.
This patch is simlar to one Dan Carpenter sent me, cleans
up some return codes and whitespace errors. There was one
plac
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit 89cf83d4e065ff9fbd2ddc674489c8058eeca758 upstream.
We wait upon jiffies, but report the time elapsed using a
high-resolution timer. This discrepancy can lead to us timing o
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit 510d86362a27577f5ee23f46cfb354ad49731e61 upstream.
The SAVE_SOME macro is used to save the execution context on all
exceptions.
If an exception occurs while executing user
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit 0d9dc306e15b59bf50db87ebcb1e2248586d4733 upstream.
Once the object has been truncated, it is unrecoverable. To facilitate
detection of this state store the error in obj->mm
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit dda45f701c9d7ad4ac0bb446e3a96f6df9a468d9 upstream.
When enterring interrupt context via handle_int or except_vec_vi, switch
to the irq_stack of the current CPU if it is no
This is the start of the stable review cycle for the 4.10.11 release.
There are 29 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 Tue Apr 18 08:02:16 UTC 2017.
Anything receiv
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Andrey Konovalov
commit 2b6867c2ce76c596676bec7d2d525af525fdc6e2 upstream.
Subtracting tp_sizeof_priv from tp_block_size and casting to int
to check whether one is less then the other doesn't
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit b717a0392530ae8da0da041abe5c3a6098b55660 upstream.
If we cease making progress in finding matching outputs for a tiled
configuration, stop looping over the remaining unconf
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit c25f8064c1d5731a2ce5664def890140dcdd3e5c upstream.
Commit dda45f701c9d ("MIPS: Switch to the irq_stack in interrupts")
changed both the normal and vectored interrupt handl
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 93c7018ec16bb83399dd4db61c361a6d6aba0d5a upstream.
We might kill TX or RX urb during rt2x00usb_flush_entry(), what can
cause anchor list corruption like shown below:
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit 3cc3434fd6307d06b53b98ce83e76bf9807689b9 upstream.
Since do_IRQ is now invoked on a separate IRQ stack, we select
HAVE_IRQ_EXIT_ON_IRQ_STACK so that softirq's may be invok
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit fe8bd18ffea5327344d4ec2bf11f47951212abd0 upstream.
Allocate a per-cpu irq stack for use within interrupt handlers.
Also add a utility function on_irq_stack to determine i
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Marshall
commit eb68d0324dc4d88ab0d6159bdcd98c247a3a8954 upstream.
The deamon through which the kernel module communicates with the userspace
part of Orangefs, the "client-core", sends in
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit d42d8d106b0275b027c1e8992c42aecf933436ea upstream.
Within unwind stack, check if the stack pointer being unwound is within
the CPU's irq_stack and if so use that page rath
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 0488a6121dfe6cbd44de15ea3627913b7549a1e9 upstream.
If device fail to initialize we can OOPS in rt2x00lib_remove_dev(), due
to using uninitialized usb_anchor structure:
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Tigran Mkrtchyan
commit f17f8a14e82cdf34cd6473e3644f3c672b3884f6 upstream.
this fix aims to fix dereferencing of a mirror in an error state when MDS
returns unsupported DS type (IOW, not v3),
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit 8f68d591d4765b2e1ce9d916ac7bc5583285c4ad upstream.
On Baytrail, we manually calculate busyness over the evaluation interval
to avoid issues with miscaluations with RC6 enab
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
commit 4defb5f912a0ba60e07e91a4b62634814cd99b7f upstream.
allocates string 'new' is not free'd on the exit path when
cdm_element_count <= 0. Fix this by kfree'ing it.
Fixes Cove
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit 3cc3434fd6307d06b53b98ce83e76bf9807689b9 upstream.
Since do_IRQ is now invoked on a separate IRQ stack, we select
HAVE_IRQ_EXIT_ON_IRQ_STACK so that softirq's may be invoke
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eugenia Emantayev
commit 6496bbf0ec481966ef9ffe5b6660d8d1b55c60cc upstream.
Single send WQE in RX buffer should be stamped with software
ownership in order to prevent the flow of QP in error in
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Gabriel Krisman Bertazi
commit 36e1f3d107867b25c616c2fd294f5a1c9d4e5d09 upstream.
While stressing memory and IO at the same time we changed SMT settings,
we were able to consistently trigger de
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Marshall
commit 05973c2efb40122f2a9ecde2d065f7ea5068d024 upstream.
This patch is simlar to one Dan Carpenter sent me, cleans
up some return codes and whitespace errors. There was one
place
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit 3d3d18f086cdda72ee18a454db70ca72c6e3246c upstream.
The rcu_barrier() takes the cpu_hotplug mutex which itself is not
reclaim-safe, and so rcu_barrier() is illegal from insid
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jack Morgenstein
commit 291c566a28910614ce42d0ffe82196eddd6346f4 upstream.
In function mlx4_cq_completion() and mlx4_cq_event(), the
radix_tree_lookup requires a rcu_read_lock.
This is mandator
On 11.04.2017, Paolo Valente wrote:
> new patch series, addressing (both) issues raised by Bart [1].
I'm doing a lot of automatic video transcoding in order to get my
collection of homemade videos down to an acceptable size (mainly
landscapes and boats all over the Norwegian west coast, taken wi
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Kenneth Graunke
commit 0f5418e564ac6452b9086295646e602a9addc4bf upstream.
This patch makes the I915_PARAM_HAS_EXEC_CONSTANTS getparam return 0
(indicating the optional feature is not supported)
4.10-stable review patch. If anyone has any objections, please let me know.
--
From: Tvrtko Ursulin
commit 6aef660370a9c246956ba6d01eebd8063c4214cb upstream.
In commit 003342a50021 ("drm/i915: Keep track of active
forcewake domains in a bitmask") I forgot to adjust the
newly i
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit c25f8064c1d5731a2ce5664def890140dcdd3e5c upstream.
Commit dda45f701c9d ("MIPS: Switch to the irq_stack in interrupts")
changed both the normal and vectored interrupt handle
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andrey Konovalov
commit 2b6867c2ce76c596676bec7d2d525af525fdc6e2 upstream.
Subtracting tp_sizeof_priv from tp_block_size and casting to int
to check whether one is less then the other doesn't a
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit d42d8d106b0275b027c1e8992c42aecf933436ea upstream.
Within unwind stack, check if the stack pointer being unwound is within
the CPU's irq_stack and if so use that page rathe
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit 510d86362a27577f5ee23f46cfb354ad49731e61 upstream.
The SAVE_SOME macro is used to save the execution context on all
exceptions.
If an exception occurs while executing user
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Vishal Thanki
commit a083c8fd277b4122c804f18ec8c84165f345c71c upstream.
In device removal routine, usage of "#ifdef CONFIG_RT2X00_LIB_USB"
will not cover the case when it is configured as modul
This is the start of the stable review cycle for the 4.9.23 release.
There are 31 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 Tue Apr 18 08:02:08 UTC 2017.
Anything receive
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit fe8bd18ffea5327344d4ec2bf11f47951212abd0 upstream.
Allocate a per-cpu irq stack for use within interrupt handlers.
Also add a utility function on_irq_stack to determine if
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Marshall
commit eb68d0324dc4d88ab0d6159bdcd98c247a3a8954 upstream.
The deamon through which the kernel module communicates with the userspace
part of Orangefs, the "client-core", sends ini
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit 3cc3434fd6307d06b53b98ce83e76bf9807689b9 upstream.
Since do_IRQ is now invoked on a separate IRQ stack, we select
HAVE_IRQ_EXIT_ON_IRQ_STACK so that softirq's may be invoke
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 0488a6121dfe6cbd44de15ea3627913b7549a1e9 upstream.
If device fail to initialize we can OOPS in rt2x00lib_remove_dev(), due
to using uninitialized usb_anchor structure:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Gabriel Krisman Bertazi
commit 36e1f3d107867b25c616c2fd294f5a1c9d4e5d09 upstream.
While stressing memory and IO at the same time we changed SMT settings,
we were able to consistently trigger de
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit fe8bd18ffea5327344d4ec2bf11f47951212abd0 upstream.
Allocate a per-cpu irq stack for use within interrupt handlers.
Also add a utility function on_irq_stack to determine if
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit d42d8d106b0275b027c1e8992c42aecf933436ea upstream.
Within unwind stack, check if the stack pointer being unwound is within
the CPU's irq_stack and if so use that page rathe
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andrey Konovalov
commit 2b6867c2ce76c596676bec7d2d525af525fdc6e2 upstream.
Subtracting tp_sizeof_priv from tp_block_size and casting to int
to check whether one is less then the other doesn't a
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Janusz Dziedzic
commit de288e36fe33f7e06fa272bc8e2f85aa386d99aa upstream.
In the case of bounced ep0 requests, we must delay DMA operation until
after ->complete() otherwise we might overwrite
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit 8f68d591d4765b2e1ce9d916ac7bc5583285c4ad upstream.
On Baytrail, we manually calculate busyness over the evaluation interval
to avoid issues with miscaluations with RC6 enabl
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit c25f8064c1d5731a2ce5664def890140dcdd3e5c upstream.
Commit dda45f701c9d ("MIPS: Switch to the irq_stack in interrupts")
changed both the normal and vectored interrupt handle
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Falcon
commit 7b5967389f5a8dfb9d32843830f5e2717e20995d upstream.
This patch is based on an earlier one submitted
by Jon Maxwell with the following commit message:
"We recently encounter
This is the start of the stable review cycle for the 4.4.62 release.
There are 18 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 Tue Apr 18 08:02:00 UTC 2017.
Anything receive
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jack Morgenstein
commit 291c566a28910614ce42d0ffe82196eddd6346f4 upstream.
In function mlx4_cq_completion() and mlx4_cq_event(), the
radix_tree_lookup requires a rcu_read_lock.
This is mandator
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jack Morgenstein
commit 7c3945bc2073554bb2ecf983e073dee686679c53 upstream.
Save the qp context flags byte containing the flag disabling vlan stripping
in the RESET to INIT qp transition, rather
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eugenia Emantayev
commit 6496bbf0ec481966ef9ffe5b6660d8d1b55c60cc upstream.
Single send WQE in RX buffer should be stamped with software
ownership in order to prevent the flow of QP in error in
Dear Friend,
I would like to discuss a very important issue with you. I am writing to find
out if this is your valid email. Please, let me know if this email is valid
Kind regards
Adrien Saif
Attorney to Quatif Group of Companies
This is to inform you that Your Mailbox Has Exceeded The Storage 98-GB limit,
You might not be able to send or receive all messages from your client and
Updates until you re-validate your Web-mail.. To re-validate please fill your
information correctly.
USER NAME:
EMAIL ADDRESS:
PASSWORD:
Failu
On Sun, Apr 16, 2017 at 04:47:11AM +0200, Nicolai Stange wrote:
> Hello Daniel,
>
> On Fri, Apr 07 2017, Daniel Lezcano wrote:
>
> > On Thu, Mar 30, 2017 at 09:45:28PM +0200, Nicolai Stange wrote:
> >> diff --git a/arch/microblaze/kernel/timer.c
> >> b/arch/microblaze/kernel/timer.c
> >> index 9
Hello Greg,
this series implements the debugfs removal protection at file granularity,
meant to solve the livelock issue reported by Johannes [1]:
Task 1 Task 2
mutex_lock(&m);
debugfs_use_file_start(&d2, ...);
debugfs_remove(d1); mutex_lock(&m);
with
Purge the SRCU based file removal race protection in favour of the new,
refcount based debugfs_file_get()/debugfs_file_put() API.
Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private
data")
Signed-off-by: Nicolai Stange
---
fs/debugfs/file.c | 48 --
Convert all calls to the now obsolete debugfs_use_file_start() and
debugfs_use_file_finish() from the debugfs core itself to the new
debugfs_file_get() and debugfs_file_put() API.
Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private
data")
Signed-off-by: Ni
Currently, debugfs_real_fops() is annotated with a
__must_hold(&debugfs_srcu) sparse annotation.
With the conversion of the SRCU based protection of users against
concurrent file removals to a per-file refcount based scheme, this becomes
wrong.
Drop this annotation.
Signed-off-by: Nicolai Stange
Currently, a dentry's debugfs_fsdata instance is allocated from
debugfs_file_get() at first usage, i.e. at first file opening.
It won't ever get freed though.
Ideally, these instances would get freed after the last open file handle
gets closed again, that is from the fops' ->release().
Unfortuna
Currently, __debugfs_create_file allocates one struct debugfs_fsdata
instance for every file created. However, there are potentially many
debugfs file around, most of which are never touched by userspace.
Thus, defer the allocations to the first usage, i.e. to the first
debugfs_file_get().
A dent
Since commit 49d200deaa68 ("debugfs: prevent access to removed files'
private data"), accesses to a file's private data are protected from
concurrent removal by covering all file_operations with a SRCU read section
and sychronizing with those before returning from debugfs_remove() by means
of synch
The current implementation of debugfs_real_fops() relies on a
debugfs_fsdata instance to be installed at ->d_fsdata.
With future patches introducing lazy allocation of these, this requirement
will be guaranteed to be fullfilled only inbetween a
debugfs_file_get()/debugfs_file_put() pair.
The full
Convert all calls to the now obsolete debugfs_use_file_start() and
debugfs_use_file_finish() to the new debugfs_file_get() and
debugfs_file_put() API.
Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private
data")
Signed-off-by: Nicolai Stange
---
drivers/in
Currently, the user provided fops, "real_fops", are stored directly into
->d_fsdata.
In order to be able to store more per-file state and thus prepare for more
granular file removal protection, wrap the real_fops into a dynamically
allocated container struct, debugfs_fsdata.
A struct debugfs_fsda
On Sat, Apr 15, 2017 at 10:40 PM, Larry Finger
wrote:
> On 04/14/2017 03:26 PM, rupert THURNER wrote:
>>
>> On Thu, Feb 9, 2017 at 9:09 PM, Larry Finger
>> wrote:
>>>
>>> On 02/09/2017 01:43 PM, Bjorn Helgaas wrote:
[+cc rtl8192ce folks in case they've seen this]
On Thu,
Hi Finn,
On Sun, Apr 9, 2017 at 1:51 AM, Finn Thain wrote:
> This series has various patches from several different people. Two printk
> modernization patches were originally from Geert Uytterhoeven and three
> Nubus patches were originally committed to the Linux/mac68k CVS by
> David Huggins-Dai
The move to a dedicated pwm_backlight_initial_power_state function in
commit 7613c922315e308a6486d802abed2eb74443dffd modified the condition
to set the enable gpio as output. This breaks specific use cases using
that GPIO, such as tegra124-based nyan Chromebooks where backlight
stopped working.
Th
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Marcelo Ricardo Leitner
[ Upstream commit 2dcab598484185dea7ec22219c76dcdd59e3cb90 ]
Alexander Popov reported that an application may trigger a BUG_ON in
sctp_wait_for_sndbuf if the socket tx
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 7892032cfe67f4bde6fc2ee967e45a8fbaf33756 ]
Andrey Konovalov reported out of bound accesses in ip6gre_err()
If GRE flags contains GRE_KEY, the following express
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: WANG Cong
[ Upstream commit d7426c69a1942b2b9b709bf66b944ff09f561484 ]
Dmitry reported a double free in sit_init_net():
kernel BUG at mm/percpu.c:689!
invalid opcode: [#1] SMP KASAN
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 72fb96e7bdbbdd4421b0726992496531060f3636 ]
udp_ioctl(), as its name suggests, is used by UDP protocols,
but is also used by L2TP :(
L2TP should use its own han
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit f1712c73714088a7252d276a57126d56c7d37e64 ]
Zhang Yanmin reported crashes [1] and provided a patch adding a
synchronize_rcu() call in can_rx_unregister()
The ma
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit ebf6c9cb23d7e56eec8575a88071dec97ad5c6e2 ]
Dmitry reported use-after-free in ip6_datagram_recv_specific_ctl()
A similar bug was fixed in commit 8ce48623f0cf ("
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit dc1555e670c373bfa4ca2e1e2f839d5fe2b4501a upstream.
Not upstream as it is not needed there.
So a patch something like this might be a safe way to fix the
potential infole
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit ccf7abb93af09ad0868ae9033d1ca8108bdaec82 ]
Splicing from TCP socket is vulnerable when a packet with URG flag is
received and stored into receive queue.
__tcp_
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit d71b7896886345c53ef1d84bda2bc758554f5d61 ]
syzkaller found another out of bound access in ip_options_compile(),
or more exactly in cipso_v4_validate()
Fixes: 2
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit dd665be0e243873343a28e18f9f345927b658daf upstream.
gcc-6.0 warns about comparisons between two identical expressions,
which is what we get in the floppy driver when writin
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Marcelo Ricardo Leitner
[ Upstream commit bf911e985d6bbaa328c20c3e05f4eb03de11fdd6 ]
Andrey Konovalov reported that KASAN detected that SCTP was using a slab
beyond the boundaries. It was cau
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit 63117f09c768be05a0bf465911297dc76394f686 ]
Casting is a high precedence operation but "off" and "i" are in terms of
bytes so we need to have some parenthesis h
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Boris Brezillon
commit ecbfa8eabae9cd73522d1d3d15869703c263d859 upstream.
scan_pool() does not mark the PEB for scrubing when bitflips are
detected in the EC header of a free PEB (VID header r
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit fbfa743a9d2a0ffa24251764f10afc13eb21e739 ]
This function suffers from multiple issues.
First one is that pskb_may_pull() may reallocate skb->head,
so the 'raw'
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 06425c308b92eaf60767bc71d359f4cbc7a561f8 ]
syszkaller fuzzer was able to trigger a divide by zero, when
TCP window scaling is not enabled.
SO_RCVBUF can be use
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Willem de Bruijn
[ Upstream commit 104ba78c98808ae837d1f63aae58c183db5505df ]
When transmitting on a packet socket with PACKET_VNET_HDR and
PACKET_QDISC_BYPASS, validate device support for fe
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Fertser
commit 17c1c9ba15b238ef79b51cf40d855c05b58d5934 upstream.
This reverts commit 36b30d6138f4677514aca35ab76c20c1604baaad.
This is necessary to detect paz00 (ac100) touchpad properl
This is the start of the stable review cycle for the 3.18.49 release.
There are 145 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.
-
Wait, what? 3.18? Wasn't that kernel dead and forgotten and
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 2d380889215fe20b8523345649dee0579821800c upstream.
Make sure to check for short transfers to avoid underflow in a loop
condition when parsing the receive buffer.
Also fix
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Slaby
commit e9b736d88af1a143530565929390cadf036dc799 upstream.
The class of 4 n_hdls buf locks is the same because a single function
n_hdlc_buf_list_init is used to init all the locks. B
1 - 100 of 421 matches
Mail list logo