4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Kleine-Budde
commit 200f5c49f7a2cd694436bfc6cb0662b794c96736 upstream.
This patch replaces the use of "struct can_frame::can_dlc" by "struct
canfd_frame::len" to access the frame's length
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Luca Coelho
commit 5d041c46ccb9b48acc110e214beff5e2789311df upstream.
We can't use SAR Geo if basic SAR is not enabled, since the SAR Geo
tables define offsets in relation to the basic SAR tab
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Amir Goldstein
commit b469e7e47c8a075cc08bcd1e85d4365134bdcdd5 upstream.
When an event is reported on a sub-directory and the parent inode has
a mark mask with FS_EVENT_ON_CHILD|FS_ISDIR, the
wt., 13 lis 2018 o 15:01 Bartosz Golaszewski napisał(a):
>
> From: Bartosz Golaszewski
>
> We want to add nvmem support for MTD. TI DaVinci is the first platform
> that will be using it, but only in non-DT mode. In order not to
> introduce any new interface to supporting of which we would have to
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Emmanuel Grumbach
commit ec484d03ef0df8d34086b95710e355a259cbe1f2 upstream.
The oldest firmware supported by iwlmvm do support getting
the average beacon RSSI. Enable the sta_statistics() call
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Oleksij Rempel
commit 55059f2b7f868cd43b3ad30e28e18347e1b46ace upstream.
Current CAN framework can't guarantee proper/chronological order
of RX and TX-ECHO messages. To make this possible, dri
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 14fdc2c5318ae420e68496975f48dc1dbef52649 upstream.
The Linux kernel security team has been accused of rejecting the idea of
security embargoes. This is incorrect, and could
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Oleksij Rempel
commit d788905f68fd4714c82936f6f7f1d3644d7ae7ef upstream.
Currently, in case of bus error, driver will generate error message and put
in the tail of the message queue. To avoid
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e39f9dd8206ad66992ac0e6218ef1ba746f2cce9 ]
If a bias is enabled on a pin of an Amlogic SoC, calling .pin_config_set()
with PIN_CONFIG_BIAS_DISABLE will not disable the bias. Instead
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit f8d294324598ec85bea2779512e48c94cbe4d7c6 ]
The addition of a spinlock in lpfc_debugfs_nodelist_data() introduced
a bug that lets us not skip NULL pointers correctly, as noticed by
gc
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit ed3a2b74f3eb34c84c8377353f4730f05acdfd05 ]
AO pull register definition is inverted between pull (up/down) and
pull enable. Fixing this allows to properly apply bias setting
through p
Hi folks,
I'm new to DRM and trying to understand the warning in
drivers/gpu/drm/drm_vblank.c during drm_vblank_cleanup().
WARN_ON(READ_ONCE(vblank->enabled) &&
drm_core_check_feature(dev, DRIVER_MODESET));
Is the drm driver responsible for making sure that !(vblank->enabled) in
the .unb
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e91b162d2868672d06010f34aa83d408db13d3c6 ]
AO pull register definition is inverted between pull (up/down) and
pull enable. Fixing this allows to properly apply bias setting
through p
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e34ff8edcae89922d187425ab0b82e6a039aa371 ]
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/scsi/hisi_sas/hisi_sas_v1_hw.c: In function 'start_delivery_v1_hw':
drivers/scsi/hi
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Oleksij Rempel
commit ed72bc8bcb9277061e753faf300b20f97323761c upstream.
Current flexcan driver will put TX-ECHO in regular unsorted way, in
this case TX-ECHO can come after the response to th
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit af31b04b67f4fd7f639fd465a507c154c46fc9fb ]
KASAN reports following global out of bounds access while
nfit_test is being loaded. The out of bound access happens
the following referenc
Hi Bjorn,
on 2018/11/29 4:00, Bjorn Helgaas wrote:
[+cc linux-pci]
Since you mention reports, are there URLs to mailing list archives you
can include?
OK, I will add it:
https://marc.info/?l=linux-kernel&m=153543887027997&w=2
- entry = alloc_msi_entry(&dev->dev, nvec, masks);
+ e
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 28c5bcf74fa07c25d5bd118d1271920f51ce2a98 ]
TRACE_INCLUDE_PATH and TRACE_INCLUDE_FILE are used by
, so like that #include, they should
be outside #ifdef protection.
They also need to
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit fbb974ba693bbfb4e24a62181ef16d4e45febc37 ]
When there is no IRQ configured for the RTC, the rtc-cmos code does not
support alarms, all alarm rtc_ops fail with -EIO / -EINVAL.
The rt
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 6ef28a04d1ccf718eee069b72132ce4aa1e52ab9 ]
Add return value check for voltage scale when ARM clock
rate change fail.
Signed-off-by: Anson Huang
Acked-by: Viresh Kumar
Signed-off-b
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 9bde0afb7a906f1dabdba37162551565740b862d ]
pcf2127_i2c_gather_write() allocates memory as local variable
for i2c_master_send(), after finishing the master transfer,
the allocated mem
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit de7b75d82f70c5469675b99ad632983c50b6f7e7 ]
LKP recently reported a hang at bootup in the floppy code:
[ 245.678853] INFO: task mount:580 blocked for more than 120 seconds.
[ 245.6
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit c10a8de0d32e95b0b8c7c17b6dc09baea5a5a899 ]
KabyLake and CoffeeLake CPUs have the same client uncore events as SkyLake.
Add the PCI IDs for the KabyLake Y, U, S processor lines and C
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit c469933e772132aad040bd6a2adc8edf9ad6f825 ]
A ~10% regression has been reported for UnixBench's execl throughput
test by Aaron Lu and Ye Xiaolong:
https://lkml.org/lkml/2018/10/30/
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 899a42f836678a595f7d2bc36a5a0c2b03d08cbc ]
Move lookup_processor_type() out of the __init section so it is callable
from (eg) the secondary startup code during hotplug.
Reviewed-by:
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver Hartkopp
commit a43608fa77213ad5ac5f75994254b9f65d57cfa0 upstream.
When the socket is CAN FD enabled it can handle CAN FD frame
transmissions. Add an additional check in raw_sendmsg()
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 43c6494fa1499912c8177e71450c0279041152a6 ]
Back in 2006 Ben added some workarounds for a misbehaviour in the
Spider IO bridge used on early Cell machines, see commit
014da7ff47b5 ("[
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 945aceb1db8885d3a35790cf2e810f681db52756 ]
Call the per-processor type check_bugs() method in the same way as we
do other per-processor functions - move the "processor." detail into
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e209950fdd065d2cc46e6338e47e52841b830cba ]
Allow the way we access members of the processor vtable to be changed
at compile time. We will need to move to per-CPU vtables to fix the
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e3d5e573a54dabdc0f9f3cb039d799323372b251 ]
Signed-off-by: Trond Myklebust
Signed-off-by: Sasha Levin
---
net/sunrpc/auth_generic.c | 8 +---
1 file changed, 1 insertion(+), 7
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 383fb3ee8024d596f488d2dbaf45e572897acbdb ]
In big.Little systems, some CPUs require the Spectre workarounds in
paths such as the context switch, but other CPUs do not. In order
to h
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit f157d411a9eb170d2ee6b766da7a381962017cc9 ]
Building kernel 4.20 for Fedora as RPM fails, because riscv is missing
vdso_install target in arch/riscv/Makefile.
Signed-off-by: David Ab
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit ca474b73896bf6e0c1eb8787eb217b0f80221610 ]
We need to copy the io priority, too; otherwise the clone will run
with a different priority than the original one.
Fixes: 43b62ce3ff0a ("
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit ef3a61406618291c46da168ff91acaa28d85944c ]
Fixes:
arch/riscv/kernel/module.c: In function 'apply_r_riscv_32_rela':
./include/linux/kern_levels.h:5:18: warning: format '%llx' expects
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 437ccdc8ce629470babdda1a7086e2f477048cbd ]
When VPHN function is not supported and during cpu hotplug event,
kernel prints message 'VPHN function not supported. Disabling
polling...'
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit c9a8e5fce009e3c601a43c49ea9dbcb25d1ffac5 upstream.
After we are done with the tty buffer, zero it out.
Reported-by: aszlig
Tested-by: Milan Broz
Tested-by: Daniel Zato
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastien Boisvert
commit 4d54954a197175c0dcb3c82af0c0740d0c5f827a upstream.
Tracing the event "fs_dax:dax_pmd_insert_mapping" with perf produces this
warning:
[fs_dax:dax_pmd_insert_ma
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 33412b8673135b18ea42beb7f5117ed0091798b6 ]
Commit:
3ea86495aef2 ("efi/arm: preserve early mapping of UEFI memory map longer for
BGRT")
deferred the unmap of the early mapping of
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Jacopo Mondi
commit bad1774ed41e98a43074e50e7d5ac9e1e848d99a upstream.
As of: commit 476dec012f4c ("media: ov5640: Add horizontal and vertical
totals") the timings parameters gets programmed s
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Michael J. Ruhl
commit a0e0cb82804a6a21d9067022c2dfdf80d11da429 upstream.
pq_update() can only be called in two places: from the completion
function when the complete (npkts) sequence of packe
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Erik Schmauss
commit 4abb951b73ff0a8a979113ef185651aa3c8da19b upstream.
The table load process omitted adding the operation region address
range to the global list. This omission is problemati
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Jacopo Mondi
commit aa4bb8b8838ffcc776a79f49a4d7476b82405349 upstream.
Rework the MIPI interface startup sequence with the following changes:
- Remove MIPI bus initialization from the initial
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Oleksij Rempel
commit 4530ec36bb1e0d24f41c33229694adacda3d5d89 upstream.
This function has nothing todo with error.
Signed-off-by: Oleksij Rempel
Cc: linux-stable
Signed-off-by: Marc Kleine
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Hugues Fruchet
commit c2c3f42df4dd9bb231d756bacb0c897f662c6d3c upstream.
ov5640_set_mode_exposure_calc() is checking binning value but
binning value read is buggy, fix this.
Rename ov5640_binn
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit b97b3d9fb57860a60592859e332de7759fd54c2e upstream.
If we are not echoing the data to userspace or the console is in icanon
mode, then perhaps it is a "secret" so we s
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Hugues Fruchet
commit a8f438c684eaa4cbe6c98828eb996d5ec53e24fb upstream.
When switching from auto to manual mode, V4L2 core is calling
g_volatile_ctrl() in manual mode in order to get the manu
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit c2b94c72d93d0929f48157eef128c4f9d2e603ce ]
gcc 8.1.0 warns with:
kernel/debug/kdb/kdb_support.c: In function ‘kallsyms_symbol_next’:
kernel/debug/kdb/kdb_support.c:239:4: warning: ‘
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Hugues Fruchet
commit dc29a1c187eedc1d498cb567c44bbbc832b009cb upstream.
Symptom was black image when capturing HD or 5Mp picture
due to manual exposure set to 1 while it was intended to
set a
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Hugues Fruchet
commit 3cca8ef5f774cbd61c8db05d9aa401de9bb59c66 upstream.
Ensure that auto gain and auto exposure are well restored
when changing mode.
Signed-off-by: Hugues Fruchet
Reviewed-
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Paul E. McKenney
commit 92aa39e9dc77481b90cbef25e547d66cab901496 upstream.
The per-CPU rcu_dynticks.rcu_urgent_qs variable communicates an urgent
need for an RCU quiescent state from the force
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Stein
commit cbffaf7aa09edbaea2bc7dc440c945297095e2fd upstream.
Essentially this patch moves the TX mailbox to position 63, regardless
of timestamp based offloading or RX FIFO. So ma
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Amir Goldstein
commit 007d1e8395eaa59b0e7ad9eb2b53a40859446a88 upstream.
FS_EVENT_ON_CHILD gets a special treatment in fsnotify() because it is
not a flag specifying an event type, but rather
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit ca0246bb97c23da9d267c2107c07fb77e38205c9 ]
Reclaim and free can race on an object which is basically fine but in
order for reclaim to be able to map "freed" object we need to encode
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e39d8a186ed002854196668cb7562ffdfbc6d379 ]
If the server sends a CB_GETATTR or a CB_RECALL while the filesystem is
being unmounted, then we can Oops when releasing the inode in
nfs4_
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 9d789c62c1a81129b76d2a6ecbc4655e1597 ]
Page state checks are racy. Under a heavy memory workload (e.g. stress
-m 200 -t 2h) it is quite easy to hit a race window when the page
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Matthew Wilcox
commit 25bbe21bf427a81b8e3ccd480ea0e1d940256156 upstream.
After calling get_unlocked_entry(), you have to call
put_unlocked_entry() to avoid subsequent waiters losing wakeups.
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit c63ae43ba53bc432b414fd73dd5f4b01fcb1ab43 ]
Konstantin has noticed that kvmalloc might trigger the following
warning:
WARNING: CPU: 0 PID: 6676 at mm/vmstat.c:986 __fragmentation_i
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 1a413646931cb14442065cfc17561e50f5b5bb44 ]
Other filesystems such as ext4, f2fs and ubifs all return ENXIO when
lseek (SEEK_DATA or SEEK_HOLE) requests a negative offset.
man 2 lsee
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Kleine-Budde
commit e05237f9da42ee52e73acea0bb082d788e111229 upstream.
The previous patch changes the TX path to always use the last mailbox
regardless of the used offload scheme (rx-fifo
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit c837243ff4017f493c7d6f4ab57278d812a86859 ]
The bug limits the IH ring wptr address to 40bit. When the system memory
is bigger than 1TB, the bus address is more than 40bit, this cause
Hi Srinivas,
if there are no objections - can you Ack this patch for Greg to pick
up into char-misc?
Patch is fine for me. I normally send all the nvmem patches just before rc5.
--srini
Bart
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Gruenbacher
commit c26b5aa8ef0d46035060fded475e6ab957b9f69f upstream.
GFS2 passes the inode buffer head (dibh) from gfs2_iomap_begin to
gfs2_iomap_end in iomap->private. It sets that
On 18-11-18, 12:01, Bjorn Andersson wrote:
> This finalizes the definition of the BLSP UART, I2C and SPI devices found in
> the QCS404 SoC.
Reviewed-by: Vinod Koul
--
~Vinod
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Lukas Wunner
commit f164d0204b1156a7e0d8d1622c1a8d25752befec upstream.
If the hi3110 shares the SPI bus with another traffic-intensive device
and packets are received in high volume (by a sepa
On Sat 2018-11-24 23:28:36, Tetsuo Handa wrote:
> Since /sys/module/printk/parameters/time can change from N to Y between
> "msg_print_text() called print_prefix() with buf == NULL" and
> "msg_print_text() again calls print_prefix() with buf != NULL", it is not
> safe for print_time() to unconditio
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 508a1c4df085a547187eed346f1bfe5e381797f1 ]
The simd wrapper's skcipher request context structure consists
of a single subrequest whose size is taken from the subordinate
skcipher. Ho
czw., 29 lis 2018 o 15:32 Srinivas Kandagatla
napisał(a):
>
>
> >
> > Hi Srinivas,
> >
> > if there are no objections - can you Ack this patch for Greg to pick
> > up into char-misc?
>
> Patch is fine for me. I normally send all the nvmem patches just before rc5.
>
> --srini
> >
> > Bart
> >
Bori
On Sun, Nov 25, 2018 at 07:33:33PM +0100, Thomas Gleixner wrote:
> If enhanced IBRS is active, STIBP is redundant for mitigating Spectre v2
> user space exploits from hyperthread sibling.
>
> Disable STIBP when enhanced IBRS is used.
Reviewed-by: Konrad Rzeszutek Wilk
Thank you!
>
> Signed-off-
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit a1705f02704cd8a24d434bfd0141ee8142ad277a ]
AO pull register definition is inverted between pull (up/down) and
pull enable. Fixing this allows to properly apply bias setting
through p
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 4bc51e1e350cd4707ce6e551a93eae26d40b9889 ]
AO pull register definition is inverted between pull (up/down) and
pull enable. Fixing this allows to properly apply bias setting
through p
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Emmanuel Grumbach
commit 82715ac71e6b94a2c2136e31f3a8e6748e33aa8c upstream.
When the firmware starts, it doesn't have any regulatory
information, hence it uses the world wide limitations. The
On Sun, Nov 25, 2018 at 07:33:31PM +0100, Thomas Gleixner wrote:
> Signed-off-by: Tim Chen
> Signed-off-by: Thomas Gleixner
Reviewed-by: Konrad Rzeszutek Wilk
Thank you!
>
> ---
> arch/x86/kernel/cpu/bugs.c |5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> --- a/arch/x86/ker
On Sun, Nov 25, 2018 at 07:33:32PM +0100, Thomas Gleixner wrote:
> The Spectre V2 printout in cpu_show_common() handles conditionals for the
> various mitigation methods directly in the sprintf() argument list. That's
> hard to read and will become unreadable if more complex decisions need to
> be
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Zimmermann
commit 5478ad10e7850ce3d8b7056db05ddfa3c9ddad9a upstream.
If vesafb attaches to the AST device, it configures the framebuffer memory
for uncached access by default. When ast.
On Sun, Nov 25, 2018 at 07:33:34PM +0100, Thomas Gleixner wrote:
> During context switch, the SSBD bit in SPEC_CTRL MSR is updated according
> to changes of the TIF_SSBD flag in the current and next running task.
>
> Currently, only the bit controlling speculative store bypass disable in
> SPEC_CT
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Aneesh Kumar K.V
commit ff09d7ec9786be4ad7589aa987d7dc66e2dd9160 upstream.
We clear the pte temporarily during read/modify/write update of the pte.
If we take a page fault while the pte is cle
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Andrew Price
commit 4c62bd9cea7bcf10292f7e4c57a2bca332942697 upstream.
When alloc_percpu() fails, sdp gets freed but sb->s_fs_info still points
to the same address. Move the assignment after t
On Thu, Nov 29, 2018 at 05:37:39AM -0800, Andy Lutomirski wrote:
>
>
> > On Nov 29, 2018, at 1:42 AM, Peter Zijlstra wrote:
> >
> > On Wed, Nov 28, 2018 at 10:05:54PM -0800, Andy Lutomirski wrote:
> >
> +static void static_call_bp_handler(struct pt_regs *regs, void *_data)
> +{
> >>>
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Keerthy
commit 622fecbccfe86a8052dea6b512d3821dcce29994 upstream.
_get_optimal_vdd_voltage call provides new_supply_vbb->u_volt
as the reference voltage while it should be really new_supply_vd
On Sun, Nov 25, 2018 at 07:33:30PM +0100, Thomas Gleixner wrote:
> Remove the unnecessary 'else' statement in spectre_v2_parse_cmdline()
> to save an indentation level.
>
> Signed-off-by: Tim Chen
> Signed-off-by: Thomas Gleixner
Reviewed-by: Konrad Rzeszutek Wilk
Thank you!
>
> ---
> arch/x
This is the start of the stable review cycle for the 4.19.6 release.
There are 110 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 Sat Dec 1 13:58:54 UTC 2018.
Anything receiv
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Shevchenko
commit 08fd9a82fda86529bb2f2af3c2f7cb657b4d3066 upstream.
If dwc3_core_init_mode() fails with deferred probe,
next probe fails on sysfs with
sysfs: cannot create duplicate fil
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Thinh Nguyen
commit ba3a51ac32ebcf8d0a54b37f1af268ad8a31c52f upstream.
Current check for the last extra TRB for zero and unaligned transfers
does not account for isoc OUT. The last TRB of the
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Rodrigo Rivas Costa
commit 385a4886778f6d6e61eff1d4d295af332d7130e1 upstream.
Previously, when a HID client such as the Steam Client was running, this
driver disabled its input device to avoid
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mimi Zohar
commit e2598077dc6a26c9644393e5c21f22a90dbdccdb upstream.
Intermittently security.ima is not being written for new files. This
patch re-initializes the new slab iint->atomic_flags
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Janosch Frank
commit 1843abd03250115af6cec0892683e70cf2297c25 upstream.
Userspace could have munmapped the area before doing unmapping from
the gmap. This would leave us with a valid vmaddr, b
On Thu, 29 Nov 2018, Peter Zijlstra wrote:
> > int3 isn’t IST anymore, so the int3 instruction conditionally
> > subtracts 8 from RSP and then pushes SS, etc. So my email was
> > obviously wrong wrt “cs”, but you’re still potentially overwriting the
> > int3 IRET frame.
>
> ARGH!..
>
> can't
On Sun, Nov 25, 2018 at 07:33:35PM +0100, Thomas Gleixner wrote:
> The logic to detect whether there's a change in the previous and next
> task's flag relevant to update speculation control MSRs are spread out
> across multiple functions.
>
> Consolidate all checks needed for updating speculation
Since now all crypto stats are on their own structures, it is now
useless to have the algorithm name in the err_cnt member.
Signed-off-by: Corentin Labbe
---
crypto/algapi.c | 38 -
crypto/crypto_user_stat.c | 18
include/lin
Like for userspace, this patch splits stats into multiple structures,
one for each algorithm class.
Signed-off-by: Corentin Labbe
---
crypto/algapi.c | 108 +++
crypto/crypto_user_stat.c | 82 -
include/linux/crypto.h| 180 +++
All crypto_stats functions use the struct xxx_request for feeding stats,
but in some case this structure could already be freed.
For fixing this, the needed parameters (len and alg) will be stored
before the request being executed.
Fixes: cac5818c25d0 ("crypto: user - Implement a generic crypto st
It is cleaner to have each stat in their own structures.
Signed-off-by: Corentin Labbe
---
crypto/crypto_user_stat.c | 20 +++
include/uapi/linux/cryptouser.h | 100
2 files changed, 72 insertions(+), 48 deletions(-)
diff --git a/crypto/crypto_user_st
On Thu, Nov 29, 2018 at 9:25 AM Rob Clark wrote:
>
> On Thu, Nov 29, 2018 at 9:14 AM Christoph Hellwig wrote:
> >
> > On Thu, Nov 29, 2018 at 07:33:15PM +0530, Vivek Gautam wrote:
> > > dma_map_sg() expects a DMA domain. However, the drm devices
> > > have been traditionally using unmanaged iommu
This patch add the crypto_stats_init() function.
This will permit to remove some ifdef from __crypto_register_alg().
Signed-off-by: Corentin Labbe
---
crypto/algapi.c| 10 +++---
include/linux/crypto.h | 3 +++
2 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/crypto/a
Hello
This patchset fixes all reported problem by Eric biggers.
Regards
Changes since v4:
- Inlined functions when !CRYPTO_STATS
Changes since v3:
- Added a crypto_stats_init as asked vy Neil Horman
- Fixed some checkpatch complaints
Changes since v2:
- moved all crypto_stats functions from he
On 29-11-2018 14:38, David Laight wrote:
> From: Jose Abreu
>> Sent: 29 November 2018 14:29
>>
>> Some ARC CPU's do not support unaligned loads/stores. Currently, generic
>> implementation of reads{b/w/l}()/writes{b/w/l}() is being used with ARC.
>> This can lead to misfunction of some drivers as g
Hi Dan,
On 29/11/18 12:21, Dan Carpenter wrote:
> Hi Enric,
>
> I love your patch! Perhaps something to improve:
>
> url:
> https://github.com/0day-ci/linux/commits/Enric-Balletbo-i-Serra/mfd-cros_ec-use-devm_mfd_add_devices/20181123-025253
>
> smatch warnings:
> drivers/platform/chrome/cro
On Thu, 29 Nov 2018 15:35:58 +0100
Bartosz Golaszewski wrote:
> czw., 29 lis 2018 o 15:32 Srinivas Kandagatla
> napisał(a):
> >
> >
> > >
> > > Hi Srinivas,
> > >
> > > if there are no objections - can you Ack this patch for Greg to pick
> > > up into char-misc?
> >
> > Patch is fine for me.
On Sun, Nov 25, 2018 at 07:33:36PM +0100, Thomas Gleixner wrote:
> Currently the 'sched_smt_present' static key is enabled when at CPU bringup
> SMT topology is observed, but it is never disabled. However there is demand
> to also disable the key when the topology changes such that there is no SMT
On Thu, Nov 29, 2018 at 3:26 PM Rob Clark wrote:
>
> On Thu, Nov 29, 2018 at 9:14 AM Christoph Hellwig wrote:
> >
> > On Thu, Nov 29, 2018 at 07:33:15PM +0530, Vivek Gautam wrote:
> > > dma_map_sg() expects a DMA domain. However, the drm devices
> > > have been traditionally using unmanaged iommu
601 - 700 of 1374 matches
Mail list logo
