4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Ren
[ Upstream commit 439a36b8ef38657f765b80b775e2885338d72451 ]
We are in the situation that we have to avoid recursive cluster locking,
but there is no way to check if a cluster lock ha
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Edward Cree
[ Upstream commit e67b8a685c7c984e834e3181ef4619cd7025a136 ]
Neither ___bpf_prog_run nor the JITs accept it.
Also adds a new test case.
Fixes: 17a5267067f3 ("bpf: verifier (add ve
On Tue, 26 Sep 2017, Thomas Gleixner wrote:
> On Mon, 25 Sep 2017, Thomas Gleixner wrote:
>
> > On Thu, 7 Sep 2017, Paul Burton wrote:
> > > Up until now per_cpu_devid interrupts have not supported sharing. On
> > > MIPS we have some percpu interrupts which are shared in many systems -
> > > a sin
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Subash Abhinov Kasiviswanathan
[ Upstream commit 63ecc3d9436f8012e49dc846d6cb0a85a3433517 ]
While trying an ESP transport mode encryption for UDPv6 packets of
datagram size 1436 with MTU 1500,
On Sat, Oct 07, 2017 at 04:02:21PM +0200, Thomas Meyer wrote:
> Bool initializations should use true and false. Bool tests don't need
> comparisons.
>
> Signed-off-by: Thomas Meyer
Thanks Thomas,
applied to the configfs tree for 4.15.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit fa5f7b51fc3080c2b195fa87c7eca7c05e56f673 ]
This code causes a static checker warning because Smatch doesn't trust
anything that comes from skb->data. I've revi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Robbie Ko
[ Upstream commit 4dd9920d991745c4a16f53a8f615f706fbe4b3f7 ]
Under certain situations, an incremental send operation can fail due to a
premature attempt to create a new top level ino
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Emmanuel Grumbach
[ Upstream commit d98937f4ea713d21e0fcc345919f86c877dd8d6f ]
iwlwifi now supports RSS and can't let mac80211 track the
PS state based on the Rx frames since they can come out
Michael,
On (09/27/17 15:01), Michael Ellerman wrote:
> Sergey Senozhatsky writes:
>
> > On (09/22/17 16:48), Luck, Tony wrote:
> > [..]
> >> Tested patch series on ia64 successfully.
> >>
> >> Tested-by: Tony Luck
> >
> > thanks!
> >
> >> After this goes upstream, you should submit a patch to
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe JAILLET
[ Upstream commit ca1c39ef76376b67303d01f94fe98bb68bb3861a ]
Reorder error handling labels in order to match the way resources have
been allocated.
Signed-off-by: Christoph
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Franck Demathieu
[ Upstream commit b28ace12661fbcfd90959c1e84ff5a85113a82a1 ]
The max and entry variables are unsigned according to the dt-bindings.
Fix following 3 sparse issues (-Wtypesign):
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
[ Upstream commit ff4dd73dd2b4806419f8ff65cbce11d5019548d0 ]
Unfortunately, the nla policy was defined to have HWSIM_ATTR_RADIO_NAME
as an NLA_STRING, rather than NLA_NUL_STRING,
On 19/10/17 16:51, Boris Brezillon wrote:
> On Thu, 19 Oct 2017 11:41:29 +0300
> Roger Quadros wrote:
>
>> Since v4.12, NAND subpage writes were causing a NULL pointer
>> dereference on OMAP platforms (omap2-nand) using OMAP_ECC_BCH4_CODE_HW,
>> OMAP_ECC_BCH8_CODE_HW and OMAP_ECC_BCH16_CODE_HW.
>
On Thu, 7 Sep 2017, Paul Burton wrote:
>
> +static struct irqaction c0_perf_irqaction = {
> + .handler = mipsxx_pmu_handle_irq,
> + .flags = IRQF_PERCPU | IRQF_TIMER | IRQF_SHARED | IRQF_NOAUTOEN,
> + .name = "mips_perf_pmu",
> + .percpu_dev_id = &mipspmu,
> +};
> +
> static int
Hi Ingo,
I'm not sure if you saw the below ACK. In general, for objtool patches
which don't have you on CC, is it ok if I just add you to CC along with
the ACK? Or would you prefer I resend the patch to you with my SOB?
Or, would you rather I start queueing patches and doing pull requests
weekl
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Paasch
[ Upstream commit 9d538fa60bad4f7b23193c89e843797a1cf71ef3 ]
sk->sk_prot and sk->sk_prot_creator can differ when the app uses
IPV6_ADDRFORM (transforming an IPv6-socket to an
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Willem de Bruijn
[ Upstream commit 4971613c1639d8e5f102c4e797c3bf8f83a5a69e ]
Once a socket has po->fanout set, it remains a member of the group
until it is destroyed. The prot_hook must be co
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sabrina Dubroca
[ Upstream commit 62b982eeb4589b2e6d7c01a90590e3a4c2b2ca19 ]
If we try to delete the same tunnel twice, the first delete operation
does a lookup (l2tp_tunnel_get), finds the tu
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Kodanev
[ Upstream commit 36f6ee22d2d66046e369757ec6bbe1c482957ba6 ]
When running LTP IPsec tests, KASan might report:
BUG: KASAN: use-after-free in vti_tunnel_xmit+0xeee/0xff0 [ip_vti
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Potapenko
[ Upstream commit 2580c4c17aee3ad58e9751012bad278dd074ccae ]
KMSAN (https://github.com/google/kmsan) reported accessing uninitialized
skb->data[0] in the case the skb is em
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Meng Xu
[ Upstream commit 02388bf87f72e1d47174cd8f81c34443920eb5a0 ]
In isdn_ppp_write(), the header (i.e., protobuf) of the buffer is
fetched twice from userspace. The first fetch is used to
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
[ Upstream commit c6b0b656ca24ede6657abb4a2cd910fa9c1879ba ]
While we hold a reference to the dentry when build_dentry_path is
called, we could end up racing with a rename that cha
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
commit e88d62cd4b2f0b1ae55e9008e79c2794b1fc914d upstream.
As raw_cpu_generic_read() is a plain read from a raw_cpu_ptr() address,
it's possible (albeit unlikely) that the compiler
> > +/* Clear learned (non-static) entry on given port */
> > +static void alr_loop_cb_del_port_learned(struct lan9303 *chip, u32 dat0,
> > +u32 dat1, int portmap, void *ctx)
> > +{
> > + int *port = ctx;
>
> You can get the value directly to make the line bel
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Skeggs
[ Upstream commit 1894054dc1b6e4395048b2c0f28832a3f4320fd3 ]
Signed-off-by: Ben Skeggs
Signed-off-by: Sasha Levin
Signed-off-by: Greg Kroah-Hartman
---
drivers/gpu/drm/nouveau/n
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Madhavan Srinivasan
[ Upstream commit 8d911904f3ce412b20874a9c95f82009dcbb007c ]
PMC5 on POWER9 DD1 may not provide right counts in all
sampling scenarios, hence use PM_INST_DISP event instead
On Thu, 19 Oct 2017 11:41:29 +0300
Roger Quadros wrote:
> Since v4.12, NAND subpage writes were causing a NULL pointer
> dereference on OMAP platforms (omap2-nand) using OMAP_ECC_BCH4_CODE_HW,
> OMAP_ECC_BCH8_CODE_HW and OMAP_ECC_BCH16_CODE_HW.
>
> This is because for those ECC modes, omap_calcu
On Thu, 19 Oct 2017 16:36:46 +0300
Dan Carpenter wrote:
> On Thu, Oct 19, 2017 at 01:56:32PM +0200, Michal Suchánek wrote:
> >
> > I think a single cleanup section is better than many labels that
> > just avoid a single null check.
> >
>
> I am not a big advocate of churn, but one err style e
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Sanchez
[ Upstream commit b448bf9a0df6093dbadac36979a55ce4e012a677 ]
There are some memory allocation calls in hfi1_create_ctxtdata()
that do not use the numa function parameter. Thi
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: "Dmitry V. Levin"
[ Upstream commit 72aa107df6a275cf03359934ca5799a2be7a1bf7 ]
Include to fix the following linux/mroute6.h userspace
compilation errors:
/usr/include/linux/mroute6.h:80:22:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Easwar Hariharan
[ Upstream commit 39e2afa8d042a53d855137d4c5a689a6f5492b39 ]
After extended testing, it was found that the previous PCIe Gen
3 recipe, which used adaptive CTLE with Preset 4,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
[ Upstream commit 336a9cde10d641e70bac67d90ae91b3190c3edca ]
commit 82e88ff1ea94 ("hrtimer: Revert CLOCK_MONOTONIC_RAW support") removed
unfortunately a sanity check in the hrtime
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Javier Martinez Canillas
[ Upstream commit 3827b64dba27ebadb4faf51f2c91143e01ba1f6d ]
After commit 66d228a2bf03 ("regulator: core: Don't use regulators as
supplies until the parent is bound"),
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jeffy Chen
[ Upstream commit 9af02d86e11dc409e5c3de46e81c0a492ba58905 ]
It's much the same as what we did for mwifiex in:
b9da4d2 mwifiex: avoid double-disable_irq() race
"We have a race wher
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Yazen Ghannam
[ Upstream commit 75bf2f6478cab9b0c1d7f5f674a765d1e2ad530e ]
Currently, the IPID and Syndrome are printed on the same line as the
Address. There are cases when we can have a vali
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Vinod Koul
[ Upstream commit 126cfa2f5e15ae2ca7f70be71b07e6cd8d2b44d1 ]
Geminilake HDMI codec 0x280d is similar to previous platforms, so add it with
similar ops as previous.
Signed-off-by: S
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
[ Upstream commit ff4dd73dd2b4806419f8ff65cbce11d5019548d0 ]
Unfortunately, the nla policy was defined to have HWSIM_ATTR_RADIO_NAME
as an NLA_STRING, rather than NLA_NUL_STRING,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Lokesh Vutla
[ Upstream commit 08865514805d2de8e7002fa8149c5de3e391f412 ]
Commit 4a9d4b024a31 ("switch fput to task_work_add") implements a
schedule_work() for completing fput(), but did not g
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Franck Demathieu
[ Upstream commit b28ace12661fbcfd90959c1e84ff5a85113a82a1 ]
The max and entry variables are unsigned according to the dt-bindings.
Fix following 3 sparse issues (-Wtypesign):
Commit-ID: d240e4b79fedad1346796b045286fad5ca70ada9
Gitweb: https://git.kernel.org/tip/d240e4b79fedad1346796b045286fad5ca70ada9
Author: Arnd Bergmann
AuthorDate: Thu, 19 Oct 2017 12:57:06 +0200
Committer: Thomas Gleixner
CommitDate: Thu, 19 Oct 2017 15:41:18 +0200
x86: Convert x86_plat
On Thu, 19 Oct 2017 17:11:34 +0300
Roger Quadros wrote:
> On 19/10/17 16:51, Boris Brezillon wrote:
> > On Thu, 19 Oct 2017 11:41:29 +0300
> > Roger Quadros wrote:
> >
> >> Since v4.12, NAND subpage writes were causing a NULL pointer
> >> dereference on OMAP platforms (omap2-nand) using OMAP_
Commit-ID: 0cfe5b5fc0277463fa795dea312a3a2fd5e8bac2
Gitweb: https://git.kernel.org/tip/0cfe5b5fc0277463fa795dea312a3a2fd5e8bac2
Author: Jérémy Lefaure
AuthorDate: Sun, 1 Oct 2017 15:30:50 -0400
Committer: Thomas Gleixner
CommitDate: Thu, 19 Oct 2017 16:15:47 +0200
x86: Use ARRAY_SIZE
On Tue, Oct 17, 2017 at 04:32:29PM -0400, Nayna Jain wrote:
> The function wait_for_tpm_stat() is currently defined in
> tpm-interface file. It is a hardware specific function used
> only by tpm_tis and xen-tpmfront, so it is removed from
> tpm-interface.c and defined in respective driver files.
>
Commit-ID: 642e641cbea57e559720b9df09889ffcf525cf04
Gitweb: https://git.kernel.org/tip/642e641cbea57e559720b9df09889ffcf525cf04
Author: Bhumika Goyal
AuthorDate: Tue, 19 Sep 2017 16:40:43 +0530
Committer: Thomas Gleixner
CommitDate: Thu, 19 Oct 2017 16:15:47 +0200
x86/events/amd/iommu:
On Tue, Oct 17, 2017 at 04:32:32PM -0400, Nayna Jain wrote:
> Currently, tpm_msleep() uses delay_msec as the minimum value in
> usleep_range. However, that is the maximum time we want to wait.
> The function is modified to use the delay_msec as the maximum
> value, not the minimum value.
>
> After
From: James Hogan
When CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=n, the call path
hrtimer_reprogram -> clockevents_program_event ->
clockevents_program_min_delta will not retry if the clock event driver
returns -ETIME.
If the driver could not satisfy the program_min_delta for any reason,
the lack of
On Wed, Oct 18, 2017 at 06:24:47PM +0300, Jarkko Sakkinen wrote:
> On Tue, Oct 17, 2017 at 04:32:31PM -0400, Nayna Jain wrote:
> > The existing wait_for_tpm_stat() polls for the chip status after
> > 5msec sleep. As per TCG ddwg input, it is expected that tpm might
> > return status in few usec. So
On Tue, Oct 17, 2017 at 04:32:30PM -0400, Nayna Jain wrote:
> The TPM burstcount status indicates the number of bytes that can
> be sent to the TPM without causing bus wait states. Effectively,
> it is the number of empty bytes in the command FIFO.
>
> This patch optimizes the tpm_tis_send_data()
On 19/10/17 17:20, Boris Brezillon wrote:
> On Thu, 19 Oct 2017 17:11:34 +0300
> Roger Quadros wrote:
>
>> On 19/10/17 16:51, Boris Brezillon wrote:
>>> On Thu, 19 Oct 2017 11:41:29 +0300
>>> Roger Quadros wrote:
>>>
Since v4.12, NAND subpage writes were causing a NULL pointer
deref
Hi,
On 10/19/2017 12:18 AM, Tomasz Nowicki wrote:
On 18.10.2017 19:30, Jeremy Linton wrote:
On 10/18/2017 05:24 AM, Tomasz Nowicki wrote:
On 18.10.2017 07:39, Tomasz Nowicki wrote:
On 17.10.2017 17:22, Jeremy Linton wrote:
On 10/17/2017 08:25 AM, Tomasz Nowicki wrote:
On 12.10.2017 21:48,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
[ Upstream commit 24c149ad6914d349d8b64749f20f3f8ea5031fe0 ]
sparse says:
fs/ceph/ioctl.c:100:28: warning: cast to restricted __le64
preferred_osd is a __s64 so we don't need
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandre Belloni
[ Upstream commit e3ccc921b7d8fd1fcd10a00720e09823d8078666 ]
When going to suspend, the I2C registers may be lost because the power to
VDDcore is cut. Restore them when resum
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
[ Upstream commit 80d025ffede88969f6adf7266fbdedfd5641148a ]
This if block updates the dentry lease even in the case where
the MDS didn't grant one.
Signed-off-by: Jeff Layton
Re
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Sudarsana Reddy Kalluru
[ Upstream commit afe981d664aeeebc8d1bcbd7d2070b5432edaecb ]
Driver currently utilizes the same loop variable in two
nested loops.
Signed-off-by: Sudarsana Reddy Kallu
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ram Amrani
[ Upstream commit c5212b943d4b52a7d9e0d9f747e7ad59c50d31f1 ]
Currently the state is read only after the buffers are relesed.
Signed-off-by: Ram Amrani
Signed-off-by: Yuval Mintz
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Petazzoni
[ Upstream commit 36fb7435b6ac4d288a2d4deea8934f9456ab46b6 ]
The mvpp2_txq_bufs_free() function is called upon TX completion to DMA
unmap TX buffers, and free the correspondin
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Anoob Soman
[ Upstream commit 9f674e48c13dcbc31ac903433727837795b81efe ]
Allocation of new_hash, inside xenvif_new_hash(), always happen
in softirq context, so use GFP_ATOMIC instead of GFP_KE
tpm_ibmvtpm_probe() is an example of poor names. It has the generic
ones like "cleanup" which don't say *what* is cleaned and the come-from
ones like "init_irq_cleanup" which don't say anything useful at all:
647 rc = request_irq(vio_dev->irq, ibmvtpm_interrupt, 0,
648
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
[ Upstream commit 72cedf599fcebfd6cd2550274d7855838068d28c ]
We should not select drivers that depend on I2C when that is disabled,
as it results in a build error:
warning: (SND
On Thu, 19 Oct 2017, Josh Poimboeuf wrote:
> On Thu, Oct 19, 2017 at 03:24:51PM +0200, Miroslav Benes wrote:
> > On Thu, 19 Oct 2017, Josh Poimboeuf wrote:
> >
> > > On Wed, Oct 11, 2017 at 09:42:09AM -0300, Joao Moreira wrote:
> > > > > Sounds good! For klp-convert to be successful, we really n
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Yasuaki Ishimatsu
[ Upstream commit ddffe98d166f4a93d996d5aa628fd745311fc1e7 ]
To identify that pages of page table are allocated from bootmem
allocator, magic number sets to page->lru.next.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Ren
[ Upstream commit 439a36b8ef38657f765b80b775e2885338d72451 ]
We are in the situation that we have to avoid recursive cluster locking,
but there is no way to check if a cluster lock ha
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jaegeuk Kim
[ Upstream commit 86d54795c94532075d862aa0a79f0c981dab4bdd ]
Otherwise we can get livelock like below.
[79880.428136] dbench D0 18405 18404 0x
[79880.428139]
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Majd Dibbiny
[ Upstream commit 95f1ba9a24af9769f6e20dfe9a77c863f253f311 ]
In the VF driver, module parameter mlx4_log_num_mgm_entry_size was
mistakenly overwritten -- and in a manner which ove
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Robbie Ko
[ Upstream commit 4dd9920d991745c4a16f53a8f615f706fbe4b3f7 ]
Under certain situations, an incremental send operation can fail due to a
premature attempt to create a new top level ino
On Wed, Oct 18, 2017 at 5:34 PM, Frank Rowand wrote:
> On 10/18/17 13:16, Rob Herring wrote:
>> Use devicetree-compiler list for dtc issues please.
>>
>> On Wed, Oct 18, 2017 at 2:33 PM, Frank Rowand wrote:
>>> Hi Rob, Alan,
>>>
>>> On 10/18/17 08:58, Alan Tull wrote:
Hi Rob,
I've
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe JAILLET
[ Upstream commit ca1c39ef76376b67303d01f94fe98bb68bb3861a ]
Reorder error handling labels in order to match the way resources have
been allocated.
Signed-off-by: Christoph
On Thu, 21 Sep 2017, Allen Pais wrote:
> Use setup_timer function instead of initializing timer with the
> function and data fields.
>
> Signed-off-by: Allen Pais
> ---
> kernel/time/clocksource.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/kernel/time/cl
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Wanpeng Li
[ Upstream commit a499c3ead88ccf147fc50689e85a530ad923ce36 ]
This is triggered during boot when CONFIG_SCHED_DEBUG is enabled:
[ cut here ]
WARNING: CPU:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Zoran
[ Upstream commit 6cf1bf636a067eb308cb3a8322b9d6b1844a075d ]
The original github source allowed for the cache-line-size property
to be missing. Since recent firmwares also requi
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Emmanuel Grumbach
[ Upstream commit d98937f4ea713d21e0fcc345919f86c877dd8d6f ]
iwlwifi now supports RSS and can't let mac80211 track the
PS state based on the Rx frames since they can come out
On Fri, Oct 13, 2017 at 11:20:58AM +0530, Kamalesh Babulal wrote:
> On Friday 13 October 2017 10:36 AM, Josh Poimboeuf wrote:
> > On Fri, Oct 13, 2017 at 10:14:36AM +0530, Kamalesh Babulal wrote:
> > > On Thursday 12 October 2017 09:40 PM, Josh Poimboeuf wrote:
> > > > On Thu, Oct 12, 2017 at 02:32
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 47d3a07528ecbbccf53bc4390d70b4e3d1c04fcf ]
The cited commit makes a great job of finding optimal shift/multiplier
values assuming a 10 seconds wrap around, but f
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: "Mintz, Yuval"
[ Upstream commit 6f437d431930ff86e4a971d29321951faadb97c7 ]
Commit 653d2ffd6405 ("qed*: Fix link indication race") introduced another
race - one of the inner functions called f
On Wed, Oct 18, 2017 at 6:32 PM, Martin Kaiser wrote:
> Replace the two separate calls for clearing the irqchip's chained handler
> and its data with a single irq_set_chained_handler_and_data() call.
>
> Signed-off-by: Martin Kaiser
Patch applied.
Yours,
Linus Walleij
On Tue, Oct 17, 2017 at 10:28:09AM +0200, Greg KH wrote:
> On Tue, Oct 17, 2017 at 10:17:01AM +0200, Christoph Hellwig wrote:
> > Looks fine:
> >
> > Reviewed-by: Christoph Hellwig
> >
> > Greg, do you want to take this or should I queue it up in the
> > dma-mapping tree?
>
> You can take it, t
On Thu, Oct 19, 2017 at 09:31:37AM -0500, Josh Poimboeuf wrote:
> On Fri, Oct 13, 2017 at 11:20:58AM +0530, Kamalesh Babulal wrote:
> > On Friday 13 October 2017 10:36 AM, Josh Poimboeuf wrote:
> > > On Fri, Oct 13, 2017 at 10:14:36AM +0530, Kamalesh Babulal wrote:
> > > > On Thursday 12 October 20
On Thu, Oct 19, 2017 at 03:42:12PM +0200, Vlastimil Babka wrote:
> From b002266c1a826805a50087db851f93e7a87ceb2f Mon Sep 17 00:00:00 2001
> From: Vlastimil Babka
> Date: Tue, 17 Oct 2017 16:03:02 +0200
> Subject: [PATCH] mm, page_alloc: simplify list handling in rmqueue_bulk()
>
> The rmqueue_bul
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Redfearn
commit 5fdc66e046206306bf61ff2d626bfa52ca087f7b upstream.
Commit db8466c581cc ("MIPS: IRQ Stack: Unwind IRQ stack onto task
stack") erroneously set the initial stack pointer of th
Kalle Valo writes:
> Brian Norris wrote:
>
>> For devices where the FW supports WoWLAN but user-space has not
>> configured it, we don't do any PCI-specific suspend/resume operations,
>> because mac80211 doesn't call drv_suspend() when !wowlan. This has
>> particularly bad effects for some platf
Hello Ankur,
Am 05.10.2017 um 19:59 schrieb Ankur Arora:
> On 2017-10-05 06:20 AM, Konrad Rzeszutek Wilk wrote:
>> On Wed, Oct 04, 2017 at 08:26:27PM +0200, Philipp Hahn wrote:
...
>> Adding Ankur to this as I think he saw something similar.
>>
>> But in the meantime - do you see this with the lat
On 10/19/2017 02:19 PM, Ryder Lee wrote:
> Hi Matthias,
>
> Should I base on your changes and resend this patch series
> https://patchwork.kernel.org/patch/9980061/ ?
>
> I add a similar node - display_components, but your approach is better
> than mine.
>
You series should have the same issu
On Thu, 19 Oct 2017 17:23:24 +0300
Roger Quadros wrote:
> On 19/10/17 17:20, Boris Brezillon wrote:
> > On Thu, 19 Oct 2017 17:11:34 +0300
> > Roger Quadros wrote:
> >
> >> On 19/10/17 16:51, Boris Brezillon wrote:
> >>> On Thu, 19 Oct 2017 11:41:29 +0300
> >>> Roger Quadros wrote:
> >>>
> The first patch, although it is an i2c-core change, is really
> quite simple. I believe anyone can review it. But it does need
> someone other then me to take a proper look (and not just do
> a code only review) because it is a core change. Maybe there
> is another way to solve the problem (pers
Hi Alexandre,
On Thu, Sep 28, 2017 at 06:50:18PM +0900, Alexandre Courbot wrote:
> Hi everyone,
>
> Here is a new attempt at the "request" (which I propose to rename "jobs") API
> for V4L2, hopefully in a manner that can converge to something that will be
> merged. The core ideas should be easy t
On 19. okt. 2017 15:58, Vivien Didelot wrote:
Hi Egil,
Hi Vivien
Egil Hjelmeland writes:
Add DSA method port_fast_age as a step to STP support.
Add low level functions for accessing the lan9303 ALR (Address Logic
Resolution).
Added DSA method port_fdb_dump
Signed-off-by: Egil Hjelmeland
Based on the discussion about the signed character field for the year,
I went through all fields in the iso9660 and rockridge standards to see
whether they should used signed or unsigned characters. Only a single
8-bit value is defined as signed per 'section 7.1.2': the timezone
offset in a timesta
isofs uses a 'char' variable to load the number of years since
1900 for an inode timestamp. On architectures that use a signed
char type by default, this results in an invalid date for
anything beyond 2027.
This changes the function argument to a 'u8' array, which
is defined the same way on all ar
Provide a single call to allow kernel code to determine whether the system
should be locked down, thereby disallowing various accesses that might
allow the running kernel image to be changed including the loading of
modules that aren't validly signed with a key we recognise, fiddling with
MSR regis
m methods.
.RE
.P
The following facilities are restricted:
.P
.RS
Only validly signed modules may be loaded.
.P
Only validly signed binaries may be kexec'd.
.P
Only validly signed device firmware may be loaded.
.P
Unencrypted hibernation/suspend to swap are disallowed as the kernel image is
saved to a medium that can then be accessed.
.P
Use of debugfs is not permitted
From: Kyle McMartin
Make an option to provide a sysrq key that will lift the kernel lockdown,
thereby allowing the running kernel image to be accessed and modified.
On x86_64 this is triggered with SysRq+x, but this key may not be available
on all arches, so it is set by setting LOCKDOWN_LIFT_KE
From: Matthew Garrett
Allowing users to write to address space makes it possible for the kernel to
be subverted, avoiding module loading restrictions. Prevent this when the
kernel has been locked down.
Signed-off-by: Matthew Garrett
Signed-off-by: David Howells
---
drivers/char/mem.c |6
If the kernel is locked down, require that all modules have valid
signatures that we can verify.
Signed-off-by: David Howells
---
kernel/module.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/module.c b/kernel/module.c
index de66ec825992..3d9a3270c179 100644
--
From: Matthew Garrett
kexec permits the loading and execution of arbitrary code in ring 0, which
is something that lock-down is meant to prevent. It makes sense to disable
kexec in this situation.
This does not affect kexec_file_load() which can check for a signature on the
image to be booted.
From: Dave Young
Kexec reboot in case secure boot being enabled does not keep the secure
boot mode in new kernel, so later one can load unsigned kernel via legacy
kexec_load. In this state, the system is missing the protections provided
by secure boot.
Adding a patch to fix this by retain the s
On 19. okt. 2017 16:15, Andrew Lunn wrote:
+/* Clear learned (non-static) entry on given port */
+static void alr_loop_cb_del_port_learned(struct lan9303 *chip, u32 dat0,
+u32 dat1, int portmap, void *ctx)
+{
+ int *port = ctx;
You can get the value
From: Josh Boyer
There is currently no way to verify the resume image when returning
from hibernate. This might compromise the signed modules trust model,
so until we can work with signed hibernate images we disable it when the
kernel is locked down.
Signed-off-by: Josh Boyer
Signed-off-by: Da
From: Chun-Yi Lee
When KEXEC_VERIFY_SIG is not enabled, kernel should not loads image
through kexec_file systemcall if securelevel has been set.
This code was showed in Matthew's patch but not in git:
https://lkml.org/lkml/2015/3/13/778
Cc: Matthew Garrett
Signed-off-by: Chun-Yi Lee
Signed-of
From: Matthew Garrett
uswsusp allows a user process to dump and then restore kernel state, which
makes it possible to modify the running kernel. Disable this if the kernel
is locked down.
Signed-off-by: Matthew Garrett
Signed-off-by: David Howells
cc: linux...@vger.kernel.org
---
kernel/pow
From: Matthew Garrett
IO port access would permit users to gain access to PCI configuration
registers, which in turn (on a lot of hardware) give access to MMIO
register space. This would potentially permit root to trigger arbitrary
DMA, so lock it down by default.
This also implicitly locks down
501 - 600 of 1278 matches
Mail list logo