On Mon, Aug 19, 2019 at 4:48 PM syzbot
wrote:
Hello,
syzbot found the following crash on:
HEAD commit:d0847550 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=136553ba60
On Mon, Aug 19, 2019 at 4:48 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d0847550 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=1365
On Thu, Sep 19, 2019 at 8:48 PM Linus Torvalds
wrote:
>
> No problem. I'm used to merges, and I appreciate the heads-up.
Heh. The Kbuild merge turns out to be painful for other trees too. I
suspect the module tree isn't going to be any worse than the
DEBUG_INFO_BTF conflict.
Linus
When building with ppc64_defconfig, the compiler reports
that these 2 variables are not used:
warning: unused variable 'core99_l2_cache' [-Wunused-variable]
warning: unused variable 'core99_l3_cache' [-Wunused-variable]
They are only used when CONFIG_PPC64 is not defined. Move
them into a
It is not allowed to sleep to early in the boot process and this may lead
to kernel issues if the bootloader didn't prepare the slow clock and main
clock.
This results in the following error and dump stack on the AriettaG25:
bad: scheduling from the idle thread!
Ensure it is possible to sleep,
On Mon, Aug 19, 2019 at 4:48 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d0847550 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=14ff
On Mon, Aug 19, 2019 at 4:48 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d0847550 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=1160
On 12/09/2019 10:44, Sverdlin, Alexander (Nokia - DE/Ulm) wrote:
> From: Alexander Sverdlin
>
> irq_domain_associate() is the only place where irq_find_mapping() can be
> used reliably (under irq_domain_mutex) to make a decision if the mapping
> shall be created or not. Other calls to irq_find_ma
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/riscv/include/asm/pgtable.h
between commit:
b6f2b2e600a27b798 ("RISC-V: Fix building error when
CONFIG_SPARSEMEM_MANUAL=y")
from the risc-v-fixes tree and commit:
e10b0ff68eee9f59 ("mm: consolidate pgtab
On Mon, Sep 16, 2019 at 3:29 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=11ca
On Mon, Sep 16, 2019 at 3:29 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=176a
On Mon, Jul 29, 2019 at 1:48 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:6a3599ce usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=1408
> netdev is closed at the moment for patch.
I wonder about this information.
> Please repost once it reopens, in about 2 weeks time.
I hope that the presented change possibilities can be integrated
in the near future also without a repetition of this small patch series.
https://lore.kernel.org/
On Fri, 20 Sep 2019 16:54:18 +0200
"H. Nikolaus Schaller" wrote:
> > Am 20.09.2019 um 16:20 schrieb Tony Lindgren :
> >
> > * H. Nikolaus Schaller [190920 09:19]:
> >>> Am 20.09.2019 um 10:55 schrieb Linus Walleij :
> >>> I suggest to go both way:
> >>> apply this oneliner and tag for stable
On Fri, Sep 20, 2019 at 10:13:53PM +0800, Xiaoming Ni wrote:
> 1. drivers/mtd/mtdsuper.c
> mount_mtd_aux() {
>
> /* jffs2_sb_info is allocated in jffs2_fill_super, */
> ret = fill_super(sb, data, flags & SB_SILENT ? 1 : 0);
> if (ret < 0) {
> deactivate_locked_super(sb); /*
On Fri, 2019-09-20 at 19:57 +0800, Kefeng Wang wrote:
> On 2019/9/20 17:28, Robert Richter wrote:
> > On 20.09.19 14:25:19, Kefeng Wang wrote:
> > > As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
> > > pr_warning"), removing pr_warning so all logging messages use a
> > > consisten
Hello Mark,
> On Thu, Sep 19, 2019 at 07:23:50PM +0200, Alexandre Belloni wrote:
>> On 19/09/2019 17:03:15+0100, Mark Brown wrote:
>
>> > This is going to break any system where we use both a GPIO chip select
>> > and chip select 0. Ideally we'd try to figure out an unused chip select
>> > to use
This patch implements the feature that the tracing_max_latency file,
e.g. /sys/kernel/debug/tracing/tracing_max_latency will receive
notifications through the fsnotify framework when a new latency is
available.
One particularly interesting use of this facility is when enabling
threshold tracing, t
This is a tool that is intended to work around the fact that the
preemptoff, irqsoff, and preemptirqsoff tracers only work in
overwrite mode. The idea is to act randomly in such a way that we
do not systematically lose any latencies, so that if enough testing
is done, all latencies will be captured
This burst feature enables the user to generate a burst of
preempt/irqsoff latencies. This makes it possible to test whether we
are able to detect latencies that systematically occur very close to
each other.
The maximum burst size is 10. We also create 10 identical test
functions, so that we get
This new trace option "console-latency" will enable the latency
tracers to trace the console latencies. Previously this has always been
implicitely disabled. I guess this is because they are considered
to be well known and unavoidable.
However, for some organizations it may nevertheless be desirab
Hello all,
There are not many changes this time. I mainly changed my email address,
tweaked a commit message and removed the cluttering of a copyright message.
Changes in v7:
- [PATCH 1/4]:
* I have added some reasons to end of the commit message why I believe that
it makes sense to create
On Tue, Sep 17, 2019 at 11:10:37AM +0530, Kishon Vijay Abraham I wrote:
>
> On 16/09/19 4:52 PM, Lorenzo Pieralisi wrote:
> > On Mon, Sep 16, 2019 at 10:06:30AM +0800, Hillf Danton wrote:
> >>
> >> On Sun, 15 Sep 2019 09:34:37 -0700
> >>>
> >>> Kernel is 5.3-rc8 on x86_64.
> >>>
> >>> Loading and
On Fri, Sep 20, 2019 at 04:07:14PM +0100, Andrew Murray wrote:
> On Fri, Sep 20, 2019 at 04:55:05PM +0200, Arnd Bergmann wrote:
> > Without this, we can run into a build failure:
> >
> > drivers/pci/controller/dwc/pcie-tegra194.c:1394:8: error: implicit
> > declaration of function 'pinctrl_pm_sel
On Fri, Sep 20, 2019 at 06:39:25PM +0800, YueHaibing wrote:
> Fix build error without CONFIG_PINCTRL
>
> drivers/pci/controller/dwc/pcie-tegra194.c: In function tegra_pcie_config_rp:
> drivers/pci/controller/dwc/pcie-tegra194.c:1394:8: error: implicit
> declaration of function pinctrl_pm_select_d
Hi Thomas,
As a heads-up, I'm going to be away next week, and I likely won't have
the chance to look at this in detail before October.
On Thu, Sep 19, 2019 at 05:03:14PM +0200, Thomas Gleixner wrote:
> When working on a way to move out the posix cpu timer expiry out of the
> timer interrupt conte
On Fri, Sep 20, 2019 at 04:25:53PM +0200, Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 20 Sep 2019 16:17:18 +0200
>
> Two update suggestions were taken into account
> from static source code analysis.
Hi Markus
netdev is closed at the moment for patch. Please repost once it
reopens
To address a major procedural concern on Linus's part the keyrings needs
a co-maintainer.
Cc: Linus Torvalds
Suggested-by: David Howells
Signed-off-by: Jarkko Sakkinen
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c76be7aaaf74..4e8ff0af9580
On Fri, Sep 20, 2019 at 04:28:00PM +0200, Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 20 Sep 2019 15:23:39 +0200
>
> Simplify this function implementation by using a known wrapper function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elf
On Fri, Sep 20, 2019 at 04:30:13PM +0200, Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 20 Sep 2019 16:07:07 +0200
>
> * Return an error code without storing it in an intermediate variable.
>
> * Delete the local variable “ret” which became unnecessary
> with this refactoring.
>
>
On Fri, Sep 20, 2019 at 04:55:05PM +0200, Arnd Bergmann wrote:
> Without this, we can run into a build failure:
>
> drivers/pci/controller/dwc/pcie-tegra194.c:1394:8: error: implicit
> declaration of function 'pinctrl_pm_select_default_state'
> [-Werror,-Wimplicit-function-declaration]
>
> Fixe
On Tue, Sep 17, 2019 at 11:54:03PM +0300, Vanya Lazeev wrote:
> On Tue, Sep 17, 2019 at 10:10:13PM +0300, Jarkko Sakkinen wrote:
> > On Mon, Sep 16, 2019 at 11:00:30PM +0300, Vanya Lazeev wrote:
> > > On Mon, Sep 16, 2019 at 08:51:30AM +0300, Jarkko Sakkinen wrote:
> > > > On Sat, Sep 14, 2019 at 0
Now that the hwspin_lock_timeout_in_atomic() API is available use it.
Signed-off-by: Fabien Dessenne
---
drivers/irqchip/irq-stm32-exti.c | 65 +---
1 file changed, 20 insertions(+), 45 deletions(-)
diff --git a/drivers/irqchip/irq-stm32-exti.c b/drivers/irqc
Hi,
On 9/19/19 9:56 PM, Maximilian Luz wrote:
When registering a serdev controller, ACPI needs to be checked for
devices attached to it. Currently, all immediate children of the ACPI
node of the controller are assumed to be UART client devices for this
controller. Furthermore, these devices are
On 9/19/19 6:57 PM, Alex Williamson wrote:
> On Fri, 6 Sep 2019 20:13:51 -0400
> Matthew Rosato wrote:
>
>> From: Pierre Morel
>>
>> We define a new configuration entry for VFIO/PCI, VFIO_PCI_ZDEV
>>
>> When the VFIO_PCI_ZDEV feature is configured we initialize
>> a new device region, VFIO_REGI
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+0243cb250a51eeefb...@syzkaller.appspotmail.com
Tested on:
commit: e0bd8d79 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasa
Without CONFIG_OF, there is no reference to the apcs_clk_match_table[]
array, causing a harmless warning:
drivers/mailbox/qcom-apcs-ipc-mailbox.c:57:28: error: unused variable
'apcs_clk_match_table' [-Werror,-Wunused-variable]
const struct of_device_id apcs_clk_match_table[] = {
Move the
Without this, we can run into a build failure:
drivers/pci/controller/dwc/pcie-tegra194.c:1394:8: error: implicit declaration
of function 'pinctrl_pm_select_default_state'
[-Werror,-Wimplicit-function-declaration]
Fixes: ab2a50e7602b ("PCI: tegra: Add support to configure sideband pins")
Signed
> Am 20.09.2019 um 16:20 schrieb Tony Lindgren :
>
> * H. Nikolaus Schaller [190920 09:19]:
>>> Am 20.09.2019 um 10:55 schrieb Linus Walleij :
>>> I suggest to go both way:
>>> apply this oneliner and tag for stable so that GTA04 works
>>> again.
>>>
>>> Then for the next kernel think about a
From: Thierry Reding
Hi,
this puts together the two patches from this thread:
http://patchwork.ozlabs.org/patch/1146705/
there hasn't been any activity there for a couple of weeks, so I thought
I'd just throw them together and update the second patch to work on top
of the first one.
T
From: Adrian Hunter
Add host operation ->set_dma_mask() so that drivers can define their own
DMA masks.
Signed-off-by: Adrian Hunter
Signed-off-by: Thierry Reding
---
drivers/mmc/host/sdhci.c | 12
drivers/mmc/host/sdhci.h | 1 +
2 files changed, 5 insertions(+), 8 deletions(-)
From: Nicolin Chen
The SDHCI controller on Tegra186 supports 40-bit addressing, which is
usually enough to address all of system memory. However, if the SDHCI
controller is behind an IOMMU, the address space can go beyond. This
happens on Tegra186 and later where the ARM SMMU has an input address
On Fri, Sep 20, 2019 at 7:36 AM Andy Lutomirski wrote:
>
> This makes two major semantic changes to Linux's random APIs:
Hmm. I have at least two issues in here that need fixing:
- getrandom() can warn. Whoops.
- Repeatedly calling getentropy in GRND_INSECURE mode will interfere
will CRNG i
On Fri, 20 Sep 2019 at 03:36, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.3.1 release.
> There are 21 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.
>
> Respo
On Fri, 20 Sep 2019 at 03:36, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.2.17 release.
> There are 124 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.
>
> Res
On Fri, Sep 20, 2019 at 4:14 PM Xiaoming Ni wrote:
> I still think this is easier to understand:
> Free the memory allocated by the current function in the failed branch
Please note that jffs2 is in "odd fixes only" maintenance mode.
Therefore patches like this cannot be processed.
On my never
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 0e633f97162c1c74c68e2eb20bbd9259dce87cd9 upstream.
clang warns about a possible variable use that gcc never
complained about:
drivers/media/platform/davinci/isif.c:982:32
On Fri, Aug 09, 2019 at 01:24:04PM -0700, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit:e96407b4 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.co
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Stefan Mätje
commit 4ec73791a64bab25cabf16a6067ee478692e506d upstream.
Due to an erratum in some Pericom PCIe-to-PCI bridges in reverse mode
(conventional PCI on primary side, PCIe on downstre
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit c794d24ec9eb6658909955772e70f34bef5b5b91 upstream.
If module initialization fails after the character device has been
registered, unregister the character device. Additi
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Gustavo A. R. Silva"
commit 76497732932f15e7323dc805e8ea8dc11bb587cf upstream.
The use of zero-sized array causes undefined behaviour when it is not
the last member in a structure. As it happ
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Sergei Trofimovich
commit 46ca3f735f345c9d87383dd3a09fa5d43870770e upstream.
The bug manifests as an attempt to access deallocated memory:
BUG: unable to handle kernel paging request at f
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Stefan Mätje
commit 86fa6a344209d9414ea962b1f1ac6ade9dd7563a upstream.
Factor out pcie_retrain_link() to use for Pericom Retrain Link quirk. No
functional change intended.
Signed-off-by: Ste
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Noralf Trønnes
commit 65a102f68005891d7f39354cfd79099908df6d51 upstream.
For each enabled crtc the functions sets dpms on all registered connectors.
Limit this to only doing it once and on the
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 608f729c31d4caf52216ea00d20092a80959256d upstream.
Clang -Wuninitialized notices that on is_qla40XX we never allocate any DMA
memory in get_fw_boot_info() but attempt to f
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: YueHaibing
commit c8f191282f819ab4e9b47b22a65c6c29734cefce upstream.
pr->tx_bytes should be assigned to tx_bytes other than
rx_bytes.
Reported-by: Hulk Robot
Fixes: ce45b873028f ("ehea: Fixi
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Vincenzo Frascino
commit d263119387de9975d2acba1dfd3392f7c5979c18 upstream.
Currently, compat tasks running on arm64 can allocate memory up to
TASK_SIZE_32 (UL(0x1)).
This means that
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Wolfram Sang
commit c48cadf5bf4becefcd0751b97995d2350aa9bb57 upstream.
The mentioned function pointer is long gone since early 2011. Remove the
reference in the comment and reword it slightly.
Signed-off-by: Andy Lutomirski
---
drivers/char/random.c | 11 +--
include/uapi/linux/random.h | 2 ++
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/drivers/char/random.c b/drivers/char/random.c
index d152612e08fc..acabb870f222 100644
--- a/drivers/char/random.c
+
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jiufei Xue
commit 742b06b5628f2cd23cb51a034cb54dc33c6162c5 upstream.
We hit a BUG at fs/buffer.c:3057 if we detached the nbd device
before unmounting ext4 filesystem.
The typical chain of eve
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 73e6ff71a7ea924fb7121d576a2d41e3be3fc6b5 upstream.
Super-IO accesses may fail on a system with no or unmapped LPC bus.
Unable to handle kernel paging request at virtual a
It has no effect any more, so remove it. We can revert this if
there is some user code that expects to be able to set this sysctl.
Signed-off-by: Andy Lutomirski
---
drivers/char/random.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
diff --git a/drivers/char/random.
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit e95fd518d05bfc087da6fcdea4900a57cfb083bd upstream.
Super-IO accesses may fail on a system with no or unmapped LPC bus.
Also, other drivers may attempt to access the LPC b
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
commit 98e2630284ab741804bd0713e932e725466f2f84 upstream.
Currently the kfree of output.pointer can be potentially freeing
an uninitalized pointer in the case where out_data is
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit d6410408ad2a798c4cc685252c1baa713be0ad69 upstream.
Super-IO accesses may fail on a system with no or unmapped LPC bus.
Also, other drivers may attempt to access the LPC b
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit f8e579f3ca0973daef263f513da5edff520a6c0d upstream.
We had intended to update *pos, but the current code is a no-op.
Fixes: 1a0adaf37c30 ("V4L/DVB (5345): ivtv driver for
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit a147faa96f832f76e772b1e448e94ea84c774081 upstream.
This fixes the various compiler warnings when building the msgque
selftest. The primary change is using sys/msg.h instead of
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit edaf28e996af69222b2cb40455dbb5459c2b875a upstream.
If the user-provided IV needs to be aligned to the algorithm's
alignmask, then skcipher_walk_virt() copies the IV into a
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: James Prestwood
commit 6afb7e26978da5e86e57e540fdce65c8b04f398a upstream.
When using PCI passthrough with this device, the host machine locks up
completely when starting the VM, requiring a ha
The separate blocking pool is going away. Start by ignoring
GRND_RANDOM in getentropy(2).
This should not materially break any API. Any code that worked
without this change should work at least as well with this change.
Signed-off-by: Andy Lutomirski
---
drivers/char/random.c | 3 ---
i
This patch changes the read semantics of /dev/random to be the same
as /dev/urandom except that reads will block until the CRNG is
ready.
None of the cleanups that this enables have been done yet. As a
result, this gives a warning about an unused function.
Signed-off-by: Andy Lutomirski
---
dr
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Janusz Krzysztofik
commit 933c1320847f5ed6b61a7d10f0a948aa98ccd7b0 upstream.
After removal of clock_start() from before soc_camera_init_i2c() in
soc_camera_probe() by commit 9aea470b399d ("[me
There is no pool that pulls, so it was just dead code.
Signed-off-by: Andy Lutomirski
---
drivers/char/random.c | 40
1 file changed, 40 deletions(-)
diff --git a/drivers/char/random.c b/drivers/char/random.c
index 4521138231ed..99fea5cc29a8 100644
--- a
There is no longer any interface to read data from the blocking
pool, so remove it.
This enables quite a bit of code deletion, much of which will be
done in subsequent patches.
Signed-off-by: Andy Lutomirski
---
drivers/char/random.c | 106 --
1 file chan
crng_init_wait is only used to wayt for crng_init to be set to 2, so
there's no point to waking it when crng_init is set to 1. Remove the
unnecessary wake_up_interruptible() call.
Signed-off-by: Andy Lutomirski
---
drivers/char/random.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers
This makes two major semantic changes to Linux's random APIs:
It adds getentropy(..., GRND_INSECURE). This causes getentropy to
always return *something*. There is no guarantee whatsoever that
the result will be cryptographically random or even unique, but the
kernel will give the best quality r
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 8c0826756744c0ac1df600a5e4cca1a341b13101 upstream.
Super-IO accesses may fail on a system with no or unmapped LPC bus.
Also, other drivers may attempt to access the LPC b
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Julia Lawall
commit 4df2cb633b5b22ba152511f1a55e718efca6c0d9 upstream.
Add an of_node_put() when a tested device node is not available.
Fixes: c026c98739c7e ("powerpc/83xx: Do not configure o
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Yu Wang
commit 79c92ca42b5a3e0ea172ea2ce8df8e125af237da upstream.
When receiving a deauthentication/disassociation frame from a TDLS
peer, a station should not disconnect the current AP, but o
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit dec3d0b1071a0f3194e66a83d26ecf4aa8c5910e upstream.
The ->digest() method of crct10dif-pclmul reads the current CRC value
from the shash_desc context. But this value is uni
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit c1ced46c7b49ad7bc064e68d966e0ad303f917fb upstream.
The ctrl_check_input() function is called from pvr2_ctrl_range_check().
It's supposed to validate user supplied input an
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 755a9b0f8aaa5639ba5671ca50080852babb89ce upstream.
Super-IO accesses may fail on a system with no or unmapped LPC bus.
Also, other drivers may attempt to access the LPC b
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 6ae865615fc43d014da2fd1f1bba7e81ee622d1b upstream.
The __put_user() macro evaluates it's @ptr argument inside the
__uaccess_begin() / __uaccess_end() region. While this w
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 14b97ba5c20056102b3dd22696bf17b057e60976 upstream.
Super-IO accesses may fail on a system with no or unmapped LPC bus.
Also, other drivers may attempt to access the LPC b
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 767f015ea0b7ab9d60432ff6cd06b664fd71f50f upstream.
If the user-provided IV needs to be aligned to the algorithm's
alignmask, then skcipher_walk_virt() copies the IV into a
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Coly Li
commit 1bee2addc0c8470c8aaa65ef0599eeae96dd88bc upstream.
In journal_reclaim() ja->cur_idx of each cache will be update to
reclaim available journal buckets. Variable 'int n' is used t
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: YueHaibing
commit 09ac2694b0475f96be895848687ebcbba97eeecf upstream.
Syzkaller report this:
[ 1213.468581] BUG: unable to handle kernel paging request at fbfff83bf338
[ 1213.469530] #PF e
On Fri, 20 Sep 2019 at 03:53, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.194 release.
> There are 56 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.
>
> Res
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 307508d1072979f4435416f87936f87eaeb82054 upstream.
The ->digest() method of crct10dif-generic reads the current CRC value
from the shash_desc context. But this value is un
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
commit d4645d30b50d1691c26ff0f8fa4e718b08f8d3bb upstream.
The test robot reported a wrong assignment of a per-CPU variable which
it detected by using sparse and sent
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Karthik D A
commit 113630b581d6d423998d2113a8e892ed6e6af6f9 upstream.
While copying the vendor_ie obtained from the cfg80211_find_vendor_ie()
to the struct mwifiex_types_wmm_info, length/size
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Wen Huang
commit 7caac62ed598a196d6ddf8d9c121e12e082cac3a upstream.
mwifiex_update_vs_ie(),mwifiex_set_uap_rates() and
mwifiex_set_wmm_params() call memcpy() without checking
the destination s
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 579bebe5dd522580019e7b10b07daaf500f9fb1e upstream.
The USB-serial driver init_termios callback is used to override the
default initial terminal settings provided by USB-ser
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 588f7d39b3592a36fb7702ae3b8bdd9be4621e2f upstream.
When receiving a robust management frame, drop it if we don't have
rx->sta since then we don't have a security associati
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Pan Bian
commit 8149069db81853570a665f5e5648c0e526dc0e43 upstream.
The function p54p_probe takes an extra reference count of the PCI
device. However, the extra reference count is not dropped w
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dave Chinner
commit c9fbd7bbc23dbdd73364be4d045e5d3612cf6e82 upstream.
We recently had an oops reported on a 4.14 kernel in
xfs_reclaim_inodes_count() where sb->s_fs_info pointed to garbage
an
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit ef4bb63dc1f7213c08e13f6943c69cd27f69e4a3 upstream.
We forgot to set "ret" on this error path.
Fixes: e8454ff7b9a4 ("[media] drivers:media:radio: wl128x: FM Driver Common
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Bob Peterson
commit 36e4ad0316c017d5b271378ed9a1c9a4b77fab5f upstream.
Before this patch, function read_rindex_entry would set a rgrp
glock's gl_object pointer to itself before inserting the r
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Wenwen Wang
commit cb5173594d50c72b7bfa14113dfc5084b4d2f726 upstream.
In parse_audio_selector_unit(), the string array 'namelist' is allocated
through kmalloc_array(), and each string pointer
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Loic Poulain
commit 84cb3df02aea4b00405521e67c4c67c2d525c364 upstream.
HCI_UART_PROTO_SET flag is set before hci_uart_set_proto call. If we
receive data from tty layer during this procedure, p
401 - 500 of 883 matches
Mail list logo
