Disallows O_CREAT open missing the O_EXCL flag, in world or
group writable directories, even if the file doesn't exist yet.
With few exceptions (e.g. shared lock files based on flock())
if a program tries to open a file, in a sticky directory,
with the O_CREAT flag and without the O_EXCL, it
This patch-set introduces two separate features aimed at restricting
dangerous open in world or group writable sticky directories.
The purpose is to prevent exploitable bugs in user-space programs
that don't access sticky directories in the proper way.
The first patch prevents the O_CREAT open of
Disallows open of FIFOs or regular files not owned by the user in world
writable sticky directories, unless the owner is the same as that of
the directory or the file is opened without the O_CREAT flag.
The purpose is to make data spoofing attacks harder.
This protection can be turned on and off
On Wed, Nov 22, 2017 at 11:11:36AM +0530, Aneesh Kumar K.V wrote:
> "Kirill A. Shutemov" writes:
>
> > With 5-level paging, we have 56-bit virtual address space available for
> > userspace. But we don't want to expose userspace to addresses above
> > 47-bits,
On Wed, Nov 22, 2017 at 4:24 AM, 冯锐 wrote:
> Dear all:
>
> I checked the file ".config", I found " CONFIG_MMC_REALTEK_USB=y " but its
> dependence MISC_RTSX_USB is not selected, so compile errors occurred.
> What should I do to fix it?
The problem is this bit in the
Hi,
On Wed, Nov 22, 2017 at 09:33:06AM +0800, Yong wrote:
> > On Thu, Jul 27, 2017 at 01:01:35PM +0800, Yong Deng wrote:
> > > Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface
> > > and CSI1 is used for parallel interface. This is not documented in
> > > datasheet but by
Previously, we use free nid list to manage free nid entry, so during nid
allocation, we can just pick up one entry from list header, which has
quite low overhead.
But sadly, during initialization of free nid list, we should do lookup
combining with lots of different inner caches, including NAT
This is the start of the stable review cycle for the 4.13.16 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 made by Fri Nov 24 10:11:25 UTC 2017.
Anything
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Huacai Chen
[ Upstream commit cc54c1d32e6a4bb3f116721abf900513173e4d02 ]
This patch try to fix the building error on MIPS. The reason is MIPS
has already defined the LONG
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
[ Upstream commit 7c8a61d9ee1df0fb4747879fa67a99614eb62fec ]
Alexandar Potapenko while testing the kernel with KMSAN and syzkaller
discovered that
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
[ Upstream commit 93824c80bf47ebe087414b3a40ca0ff9aab7d1fb ]
Due to a documentation mistake, the IPG length was set to 0x12 while it
should have been
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Guillaume Nault
[ Upstream commit 8f7dc9ae4a7aece9fbc3e6637bdfa38b36bcdf09 ]
Using l2tp_tunnel_find() in l2tp_ip_recv() is wrong for two reasons:
* It doesn't take a
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Suravee Suthikulpanit
commit 2b83809a5e6d619a780876fcaf68cdc42b50d28c upstream.
For systems with X86_FEATURE_TOPOEXT, current logic uses the APIC ID
to
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Lyle
commit 62530ed8b1d07a45dec94d46e521c0c6c2d476e6 upstream.
A new field was introduced in 74d46992e0d9, bi_partno, instead of using
bdev->bd_contains and encoding
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jaewon Kim
commit e492080e640c2d1235ddf3441cae634cfffef7e1 upstream.
online_page_ext() and page_ext_init() allocate page_ext for each
section, but they do not
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Harkes
commit d337b66a4c52c7b04eec661d86c2ef6e168965a2 upstream.
When an application called fsync on a file in Coda a small request with
just the file identifier was
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit 8bff3685a4bbf175a96bc6a528f13455d8d38244 ]
Commit f1fb08f6337c ("vxlan: fix ND proxy when skb doesn't have transport
header offset") removed
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: "Jason A. Donenfeld"
[ Upstream commit 0642840b8bb008528dbdf929cec9f65ac4231ad0 ]
The way people generally use netlink_dump is that they fill in the skb
as much as possible,
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Corey Minyard
commit 392a17b10ec4320d3c0e96e2a23ebaad1123b989 upstream.
When I set the timeout to a specific value such as 500ms, the timeout
event will not happen in
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: alex chen
commit 28f5a8a7c033cbf3e32277f4cc9c6afd74f05300 upstream.
we should wait dio requests to finish before inode lock in
ocfs2_setattr(), otherwise the following
Hi Josh,
On Wed, Nov 22, 2017 at 4:31 AM, Josh Poimboeuf wrote:
> - Make your feature conflict with CONFIG_FRAME_POINTER on x86_64. The
> ORC unwinder is now the default anyway for 4.15, and we renamed the
> configs, so most people will be actively switching to ORC.
>
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 3b11775033dc87c3d161996c54507b15ba26414a ]
Christoph Paasch sent a patch to address the following issue :
tcp_make_synack() is leaving
On Wed, Nov 22, 2017 at 09:29:26AM +0800, Jin, Yao wrote:
>
>
> On 11/21/2017 11:17 PM, Jiri Olsa wrote:
> > On Mon, Nov 20, 2017 at 10:43:38PM +0800, Jin Yao wrote:
> >
> > SNIP
> >
> > > +static void init_saved_rblist(struct rblist *rblist)
> > > +{
> > > + rblist__init(rblist);
> > > +
Hello Corentin,
On 22 November 2017 at 08:08, Corentin Labbe wrote:
> When a cipher fail
fails
> to register in aes_init(), the error path go thought
goes through
> aes_exit() then crypto_unregister_skciphers().
> Since aes_exit calls also crypto_unregister_skcipher,
On Mon 20-11-17 21:18:55, Zi Yan wrote:
> From: Zi Yan
>
> In [1], Andrea reported that during memory hotplug/hot remove
> prep_transhuge_page() is called incorrectly on non-THP pages for
> migration, when THP is on but THP migration is not enabled.
> This leads to a bad
On Tue 21-11-17 16:27:38, Mike Kravetz wrote:
> On 11/21/2017 11:59 AM, Roman Gushchin wrote:
[...]
> > What we can do, is to rename "count" into "nr_huge_pages", like:
> >
> > for_each_hstate(h) {
> > unsigned long nr_huge_pages = h->nr_huge_pages;
> >
> > total +=
The upstream kernel currently has no core rail suspend support (LP0/SC7)
on Tegras - in general the downstream kernel (used e.g. in L4T) is the
reference that has the most functionality on Tegra.
IIRC the MMC subsystem and Tegra MMC driver between upstream and
downstream are currently quite
2017-11-11 0:14 GMT+08:00 Arnd Bergmann :
> Could you move ioremap_nocache/ioremap_uc/ioremap_wc/ioremap_wt
> out of that #ifdef, or would that break other architectures?
>
It seems ok. I just tried arm64, x86 and nds32.
#endif /* CONFIG_MMU */
#ifndef ioremap_nocache
void __iomem
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: "Jason A. Donenfeld"
[ Upstream commit 0642840b8bb008528dbdf929cec9f65ac4231ad0 ]
The way people generally use netlink_dump is that they fill in the skb
as much as possible,
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Inbar Karmy
[ Upstream commit 2e50b2619538ea0224c037f6fa746023089e0654 ]
Currently, when dma mapping fails, put_page is called,
but the page is not set to null. Later,
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit df80cd9b28b9ebaa284a41df611dbf3a2d05ca74 ]
Now when peeling off an association to the sock in another netns, all
transports in this assoc are
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Yuchung Cheng
[ Upstream commit 0eb96bf754d7fa6635aa0b0f6650c74b8a6b1cc9 ]
This patch fixes the cause of an WARNING indicatng TCP has pending
retransmission in Open state
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
[ Upstream commit 7c8a61d9ee1df0fb4747879fa67a99614eb62fec ]
Alexandar Potapenko while testing the kernel with KMSAN and syzkaller
discovered that
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/dev
head: b151f93a71fc9fecb560e823a92402d882516483
commit: b151f93a71fc9fecb560e823a92402d882516483 [62/62] torture: Eliminate
torture_runnable
reproduce:
# apt-get install sparse
git checkout
On Wed, Nov 22, 2017 at 11:10:37AM +0800, Jin, Yao wrote:
>
>
> On 11/21/2017 11:18 PM, Jiri Olsa wrote:
> > On Mon, Nov 20, 2017 at 10:43:39PM +0800, Jin Yao wrote:
> >
> > SNIP
> >
> > > if (num == 0)
> > > diff --git a/tools/perf/util/stat.c b/tools/perf/util/stat.c
> > > index
On Monday 20 November 2017 12:12:56 Karel Zak wrote:
> On Sun, Nov 19, 2017 at 01:44:40PM +0100, Pali Rohár wrote:
> > On Thursday 09 November 2017 22:21:31 Pali Rohár wrote:
> > > So from all tests and discussion I would propose new unification:
> > >
> > > 1. Read label only from the root
On 11/21/2017 09:29 PM, Roberts, William C wrote:
[snip]
>>>
>>> Do you agree with Jason's suggestion to send a synthesized TPM command
>>> in the that the command isn't supported?
>>
>> Nope.
>
> We should update the elf loader to make sure that ELF files don't contain
> Incorrect
On Fri, Nov 17, 2017 at 02:33:05PM -0600, Tom Zanussi wrote:
> Add an 'onmatch(matching.event).(param list)'
> hist trigger action which is invoked with the set of variables or
> event fields named in the 'param list'. The result is the generation
> of a synthetic event that consists of the
On Wed, Nov 22, 2017 at 09:39:39AM +1100, Tobin C. Harding wrote:
> There is currently very little documentation in the kernel on maintainer
> level tasks. In particular there are no documents on creating pull
> requests to submit to Linus.
>
> Quoting Greg Kroah-Hartman on LKML:
>
> Anyway,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 3b11775033dc87c3d161996c54507b15ba26414a ]
Christoph Paasch sent a patch to address the following issue :
tcp_make_synack() is leaving
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Konstantin Khlebnikov
[ Upstream commit 4eebff27ca4182bbf5f039dd60d79e2d7c0a707e ]
Average RTT could become zero. This happened in real life at least twice.
This
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ye Yin
[ Upstream commit 2b5ec1a5f9738ee7bf8f5ec0526e75e00362c48f ]
When run ipvs in two different network namespace at the same host, and one
ipvs transport network
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 7ec318feeed10a64c0359ec4d10889cb4defa39a ]
When a GSO skb of truesize O is segmented into 2 new skbs of truesize N1
and N2, we want to
This is the start of the stable review cycle for the 4.9.65 release.
There are 25 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 Nov 24 10:11:07 UTC 2017.
Anything
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Corey Minyard
commit 392a17b10ec4320d3c0e96e2a23ebaad1123b989 upstream.
When I set the timeout to a specific value such as 500ms, the timeout
event will not happen in time
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Huy Nguyen
[ Upstream commit d2aa060d40fa060e963f9a356d43481e43ba3dac ]
After the panic teardown firmware command, health_care detects the error
in PCI bus and calls the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Changwei Ge
commit 1c01967116a678fed8e2c68a6ab82abc8effeddc upstream.
When a node dies, other live nodes have to choose a new master for an
existed lock resource mastered
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: alex chen
commit 28f5a8a7c033cbf3e32277f4cc9c6afd74f05300 upstream.
we should wait dio requests to finish before inode lock in
ocfs2_setattr(), otherwise the following
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Andrey Konovalov
[ Upstream commit 8f5624629105589bcc23d0e51cc01bd8103d09a5 ]
When asix_suspend() is called dev->driver_priv might not have been
assigned a value, so
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andrey Konovalov
[ Upstream commit 8f5624629105589bcc23d0e51cc01bd8103d09a5 ]
When asix_suspend() is called dev->driver_priv might not have been
assigned a value, so we
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit 8bff3685a4bbf175a96bc6a528f13455d8d38244 ]
Commit f1fb08f6337c ("vxlan: fix ND proxy when skb doesn't have transport
header offset") removed
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Roberto Sassu
commit 020aae3ee58c1af0e7ffc4e2cc9fe4dc630338cb upstream.
Commit b65a9cfc2c38 ("Untangling ima mess, part 2: deal with counters")
moved the call of
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Steffen
commit ee70bc1e7b63ac8023c9ff9475d8741e397316e7 upstream.
tpm_transmit() does not offer an explicit interface to indicate the number
of valid
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit 373c4557d2aa362702c4c2d41288fb1e54990b7c upstream.
This matters at least for the mincore syscall, which will otherwise copy
uninitialized memory from the
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Ji-Ze Hong (Peter Hong)
commit fd97e66c5529046e989a0879c3bb58fddb592c71 upstream.
The SuperIO will be configured at boot time by BIOS, but some BIOS
will not deactivate the
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Neeraj Upadhyay
commit 135bd1a230bb69a68c9808a7d25467318900b80a upstream.
The pending-callbacks check in rcu_prepare_for_idle() is backwards.
It should accelerate if
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Harkes
commit d337b66a4c52c7b04eec661d86c2ef6e168965a2 upstream.
When an application called fsync on a file in Coda a small request with
just the file identifier was
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hangbin Liu
[ Upstream commit b5f862180d7011d9575d0499fa37f0f25b423b12 ]
After commit 07f4c90062f8 ("tcp/dccp: try to not exhaust ip_local_port_range
in connect()"), we
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Wang
[ Upstream commit 052d41c01b3a2e3371d66de569717353af489d63 ]
After refcnt reaches zero, vlan_vid_del() could free
dev->vlan_info via RCU:
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hangbin Liu
[ Upstream commit b5f862180d7011d9575d0499fa37f0f25b423b12 ]
After commit 07f4c90062f8 ("tcp/dccp: try to not exhaust ip_local_port_range
in connect()"), we
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Pavel Tatashin
commit d135e5750205a21a212a19dbb05aeb339e2cbea7 upstream.
In reset_deferred_meminit() we determine number of pages that must not
be deferred. We
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Barnhill <0xeff...@gmail.com>
[ Upstream commit 18129a24983906eaf2a2d448ce4b83e27091ebe2 ]
FRA_L3MDEV is defined as U8, but is being added as a U32 attribute. On
big endian architecture,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: "Jason A. Donenfeld"
[ Upstream commit 0642840b8bb008528dbdf929cec9f65ac4231ad0 ]
The way people generally use netlink_dump is that they fill in the skb
as much as possible,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit df80cd9b28b9ebaa284a41df611dbf3a2d05ca74 ]
Now when peeling off an association to the sock in another netns, all
transports in this assoc are
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: "Jason A. Donenfeld"
[ Upstream commit 0642840b8bb008528dbdf929cec9f65ac4231ad0 ]
The way people generally use netlink_dump is that they fill in the skb
as much as possible,
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit df80cd9b28b9ebaa284a41df611dbf3a2d05ca74 ]
Now when peeling off an association to the sock in another netns, all
transports in this assoc are
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Wang
[ Upstream commit 052d41c01b3a2e3371d66de569717353af489d63 ]
After refcnt reaches zero, vlan_vid_del() could free
dev->vlan_info via RCU:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Pavel Tatashin
commit d135e5750205a21a212a19dbb05aeb339e2cbea7 upstream.
In reset_deferred_meminit() we determine number of pages that must not
be deferred. We
On Wed, Nov 22, 2017 at 02:57:12PM +0800, Jin, Yao wrote:
>
>
> On 11/22/2017 2:31 PM, Ravi Bangoria wrote:
> >
> > On 11/20/2017 08:13 PM, Jin Yao wrote:
> > > @@ -76,6 +97,17 @@ static struct rb_node *saved_value_new(struct
> > > rblist *rblist __maybe_unused,
> > > return >rb_node;
> >
After commit 723288836628bc1c08 ("of: restrict DMA configuration"),
of_dma_configure doesn't configure the coherent_dma_mask/dma_mask
of endpoint function device (since it doesn't have a dt node associated
with and hence no dma-ranges property), resulting in dma_alloc_coherent
(used in
->get_msi() now checks MSI_EN bit in the MSI CAPABILITY register to
find whether the host supports MSI instead of using the
MSI ADDRESS in the MSI CAPABILITY register.
This fixes the issue with the following sequence
'modprobe pci_endpoint_test' enables MSI
'rmmod pci_endpoint_test' disables
On Wed, Nov 22, 2017 at 10:43 AM, Liran Alon wrote:
>
>
> On 22/11/17 11:31, Wanpeng Li wrote:
>>
>> 2017-11-22 17:07 GMT+08:00 Liran Alon :
>>>
>>>
>>>
>>> On 22/11/17 10:45, Liran Alon wrote:
On 22/11/17 09:56, Wanpeng Li
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ji-Ze Hong (Peter Hong)
commit fd97e66c5529046e989a0879c3bb58fddb592c71 upstream.
The SuperIO will be configured at boot time by BIOS, but some BIOS
will not deactivate the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Barnhill <0xeff...@gmail.com>
[ Upstream commit 18129a24983906eaf2a2d448ce4b83e27091ebe2 ]
FRA_L3MDEV is defined as U8, but is being added as a U32 attribute. On
big endian architecture,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Adam Wallis
commit a9df21e34b422f79d9a9fa5c3eff8c2a53491be6 upstream.
Commit adfa543e7314 ("dmatest: don't use set_freezable_with_signal()")
introduced a bug (that is
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Roberto Sassu
commit 020aae3ee58c1af0e7ffc4e2cc9fe4dc630338cb upstream.
Commit b65a9cfc2c38 ("Untangling ima mess, part 2: deal with counters")
moved the call of
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ye Yin
[ Upstream commit 2b5ec1a5f9738ee7bf8f5ec0526e75e00362c48f ]
When run ipvs in two different network namespace at the same host, and one
ipvs transport network
This is the start of the stable review cycle for the 4.4.101 release.
There are 16 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 Nov 24 10:11:01 UTC 2017.
Anything
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Huacai Chen
[ Upstream commit cc54c1d32e6a4bb3f116721abf900513173e4d02 ]
This patch try to fix the building error on MIPS. The reason is MIPS
has already defined the LONG
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hangbin Liu
[ Upstream commit b5f862180d7011d9575d0499fa37f0f25b423b12 ]
After commit 07f4c90062f8 ("tcp/dccp: try to not exhaust ip_local_port_range
in connect()"), we
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Harkes
commit d337b66a4c52c7b04eec661d86c2ef6e168965a2 upstream.
When an application called fsync on a file in Coda a small request with
just the file identifier was
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
[ Upstream commit 7c8a61d9ee1df0fb4747879fa67a99614eb62fec ]
Alexandar Potapenko while testing the kernel with KMSAN and syzkaller
discovered that
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 12d41a023efb01b846457ccdbbcbe2b65a87d530 upstream.
When setting the secret with the software Diffie-Hellman implementation,
if allocating 'g' failed
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
[ Upstream commit 7c8a61d9ee1df0fb4747879fa67a99614eb62fec ]
Alexandar Potapenko while testing the kernel with KMSAN and syzkaller
discovered that
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tudor-Dan Ambarus
commit ee34e2644a78e2561742bea8c4bdcf83cabf90a7 upstream.
setkey can be called multiple times during the existence
of the transformation object.
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Lukas Wunner
commit 2a71de2f7366fb1aec632116d0549ec56d6a3940 upstream.
Commit 348f9bb31c56 ("serial: omap: Fix RTS handling") sought to enable
auto RTS upon manual RTS
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Changwei Ge
commit 1c01967116a678fed8e2c68a6ab82abc8effeddc upstream.
When a node dies, other live nodes have to choose a new master for an
existed lock resource mastered
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Huacai Chen
[ Upstream commit cc54c1d32e6a4bb3f116721abf900513173e4d02 ]
This patch try to fix the building error on MIPS. The reason is MIPS
has already defined the LONG
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
[ Upstream commit 7c8a61d9ee1df0fb4747879fa67a99614eb62fec ]
Alexandar Potapenko while testing the kernel with KMSAN and syzkaller
discovered that
alloc_nid_failed and scan_nat_page can be called at the same time,
and we haven't protected add_free_nid and update_free_nid_bitmap
with the same nid_list_lock. That could lead to
Thread AThread B
- __build_free_nids
- scan_nat_page
When a cipher fail to register in aes_init(), the error path go thought
aes_exit() then crypto_unregister_skciphers().
Since aes_exit calls also crypto_unregister_skcipher, this trigger a
refcount_t: underflow; use-after-free.
Signed-off-by: Corentin Labbe
---
Hi Peter,
> So it seems it's actually working fine albeit the strange mac addr, no
> idea what I was trying before, although there's an error about loading
> firmware:
>
> [ 31.035291] Bluetooth: hci0: BCM: chip id 94
> [ 31.035801] Bluetooth: hci0: BCM: features 0x2e
> [ 31.037483]
On Wed, Nov 22, 2017 at 11:42:05AM +0800, Jin, Yao wrote:
>
>
> On 11/21/2017 11:18 PM, Jiri Olsa wrote:
> > On Mon, Nov 20, 2017 at 10:43:43PM +0800, Jin Yao wrote:
> >
> > SNIP
> >
> > > - if ((stat_config.aggr_mode == AGGR_THREAD) &&
> > > !target__has_task()) {
> > > -
Hi Fabio,
On 21/11/2017 17:54, Fabio Estevam wrote:
> On Tue, Nov 21, 2017 at 2:28 PM, Neil Armstrong
> wrote:
>
>> + reg_wl18xx_vmmc: regulator-wl18xx {
>> + compatible = "regulator-fixed";
>> + regulator-name = "vwl1807";
>> +
On Tue, Nov 21, 2017 at 05:18:21PM +0100, Marc Haber wrote:
> On the affected host, VMs freeze at a rate about two or three per day.
> They just stop dead in their tracks, console and serial console become
> unresponsive, ping stops, they don't react to virsh shutdown, only to
> virsh destroy.
I
If either uartclk or baud are 0, avoid calculating and setting a divisor
based on them since the output will almost certainly be garbage.
This also allows platforms such as the MIPS generic kernel, which has no
way to know a valid BASE_BASE for the board it is actually booted on at
compile time,
Add a custom serial.h header for MIPS, allowing platforms to override
the asm-generic version if required.
The generic platform uses this header to set BASE_BAUD to 0. The
generic platform supports multiple boards, which may have different
UART clocks. Also one of the boards supported is the
Add a variant of rbtree_replace_node() that maintains the leftmost
cache of struct rbtree_root_cached when replacing nodes within the
rbtree.
As drm_mm is the only rb_replace_node() being used on an interval tree,
the mistake looks fairly self-contained. Furthermore the only user of
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Roberto Sassu
commit 020aae3ee58c1af0e7ffc4e2cc9fe4dc630338cb upstream.
Commit b65a9cfc2c38 ("Untangling ima mess, part 2: deal with counters")
moved the call of
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Ye Yin
[ Upstream commit 2b5ec1a5f9738ee7bf8f5ec0526e75e00362c48f ]
When run ipvs in two different network namespace at the same host, and one
ipvs transport network
1 - 100 of 2184 matches
Mail list logo