4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Mastykin
commit 02e389e63e3523828fc3832f27e0341885f60f6f upstream.
When using mcp23s08 module with gpio-keys, often (50% of boots)
it fails to get irq numbers with message:
"gpio-keys k
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Max Filippov
commit ca47480921587ae30417dd234a9f79af188e3666 upstream.
Return 0 if the operation was successful, not the userspace memory
value. Check that userspace value equals passed oldval
On Thu, Feb 15, 2018 at 6:43 AM, Greg KH wrote:
> On Wed, Feb 14, 2018 at 11:12:24PM +0100, Arnd Bergmann wrote:
>> On Wed, Dec 6, 2017 at 4:08 PM, Dave Hansen
>> wrote:
>>
>> I also saw another warning:
>>
>> /git/arm-soc/arch/x86/mm/kaiser.c: In function 'kaiser_init':
>> /git/arm-soc/arch/x8
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Kai-Heng Feng
commit 7d06d5895c159f64c46560dc258e553ad8670fe0 upstream.
This reverts commit fd865802c66bc451dc515ed89360f84376ce1a56.
This commit causes a regression on some QCA ROME chips. T
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans Verkuil
commit a751be5b142ef6bcbbb96d9899516f4d9c8d0ef4 upstream.
put_v4l2_window32() didn't copy back the clip list to userspace.
Drivers can update the clip rectangles, so this should b
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans Verkuil
commit d83a8243aaefe62ace433e4384a4f077bed86acb upstream.
Some ioctls need to copy back the result even if the ioctl returned
an error. However, don't do this for the error code -
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans Verkuil
commit 8ed5a59dcb47a6f76034ee760b36e089f3e82529 upstream.
The struct v4l2_plane32 should set m.userptr as well. The same
happens in v4l2_buffer32 and v4l2-compliance tests for thi
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans Verkuil
commit b8c601e8af2d08f733d74defa8465303391bb930 upstream.
ctrl_is_pointer just hardcoded two known string controls, but that
caused problems when using e.g. custom controls that u
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans Verkuil
commit 169f24ca68bf0f247d111aef07af00dd3a02ae88 upstream.
There is nothing wrong with using an unknown buffer type. So
stop spamming the kernel log whenever this happens. The kern
On 15/02/18 04:17, Tomasz Figa wrote:
[...]
Could you elaborate on what kind of locking you are concerned about?
As I explained before, the normally happening fast path would lock
dev->power_lock only for the brief moment of incrementing the runtime
PM usage counter.
My bad, that's not even it.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 9903a91c763ecdae333a04a9d89d79d2b8966503 upstream.
With pipe-user-pages-hard set to 'N', users were actually only allowed up
to 'N - 1' buffers; and likewise for pipe-user-
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit a1be1f3931bfe0a42b46fef77a04593c2b136e7f upstream.
This reverts commit ba62bafe942b ("kernel/relay.c: fix potential memory leak").
This commit introduced a double free bug
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 3cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e upstream.
A typical code fragment was copied across many dvb-frontend drivers and
causes large stack frames when built with with C
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Rasmus Villemoes
commit 4f7e988e63e336827f4150de48163bed05d653bd upstream.
This reverts commit 92266d6ef60c ("async: simplify lowest_in_progress()")
which was simply wrong: In the case where d
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit d0290bc20d4739b7a900ae37eb5d4cc3be2b393f upstream.
Commit df04abfd181a ("fs/proc/kcore.c: Add bounce buffer for ktext
data") added a bounce buffer to avoid hardened userc
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit e7c52b84fb18f08ce49b6067ae6285aca79084a8 upstream.
We get a lot of very large stack frames using gcc-7.0.1 with the default
-fsanitize-address-use-after-scope --param asan
On 15/02/18 17:39, Tim Harvey wrote:
> Add support for the TDA1997x HDMI receivers.
>
> Cc: Hans Verkuil
> Signed-off-by: Tim Harvey
> ---
> v12:
> - fix coccinelle warnings
Did you post the right version? I still see the owner being set and the
other kbuild warning ('note: in expansion of mac
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans Verkuil
commit 486c521510c44a04cd756a9267e7d1e271c8a4ba upstream.
These helper functions do not really help. Move the code to the
__get/put_v4l2_format32 functions.
Signed-off-by: Hans V
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit 9893b905e743ded332575ca04486bd586c0772f7 upstream.
The XC2028_I2C_FLUSH only needs to be implemented on a few
devices. Others can safely ignore it.
That prevents
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Liu Bo
commit 0198e5b707cfeb5defbd1b71b1ec6e71580d7db9 upstream.
Bio iterated by set_bio_pages_uptodate() is raid56 internal one, so it
will never be a BIO_CLONED bio, and since this is called
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: John Keeping
commit c66234cfedfc3e6e3b62563a5f2c1562be09a35d upstream.
When restoring registers during runtime resume, we must not write to
I2S_TXDR which is the transmit FIFO as this queues u
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Kaiser
commit 0be267255cef64e1c58475baa7b25568355a3816 upstream.
When the watchdog device is suspended, its timeout is set to the maximum
value. During resume, the previously set timeou
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: James Morse
commit 58d6b15e9da5042a99c9c30ad725792e4569150e upstream.
cpu_pm_enter() calls the pm notifier chain with CPU_PM_ENTER, then if
there is a failure: CPU_PM_ENTER_FAILED.
When KVM r
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Mackerras
commit 36ee41d161c67a6fcf696d4817a0da31f778938c upstream.
Running with CONFIG_DEBUG_ATOMIC_SLEEP reveals that HV KVM tries to
read guest memory, in order to emulate guest instru
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit eff84b379089cd8b4e83599639c1f5f6e34ef7bf upstream.
The SHA-512 multibuffer code keeps track of the number of blocks pending
in each lane. The minimum of these values is us
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans Verkuil
commit 3ee6d040719ae09110e5cdf24d5386abe5d1b776 upstream.
The result of the VIDIOC_PREPARE_BUF ioctl was never copied back
to userspace since it was missing in the switch.
Signed
We are currently only checking for the first entry in the table while
we should check them all. Usual no-idle-on-init is together with
no-reset-on-init, so this has gone unnoticed.
Fixes: 566a9b05e1fa ("bus: ti-sysc: Handle module quirks based dts
configuration")
Signed-off-by: Tony Lindgren
---
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans Verkuil
commit 273caa260035c03d89ad63d72d8cd3d9e5c5e3f1 upstream.
If the device is of type VFL_TYPE_SUBDEV then vdev->ioctl_ops
is NULL so the 'if (!ops->vidioc_query_ext_ctrl)' check wou
On Thu, Feb 15, 2018 at 9:04 AM, Mark Rutland wrote:
> Hi,
>
> While fuzzing arm64 v4.16-rc1 with Syzkaller, I've been hitting a
> misaligned atomic in __skb_clone:
>
> atomic_inc(&(skb_shinfo(skb)->dataref));
>
> .. where dataref doesn't have the required natural alignment, and the
> atom
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: LEROY Christophe
commit 87a81dce53b1ea61acaeefa5191a0376a2d1d721 upstream.
Performing the hash of an empty file leads to a kernel Oops
[ 44.504600] Unable to handle kernel paging request fo
From: Ingo Molnar
__tasklet_schedule() and __tasklet_hi_schedule() are almost identical.
Move the common code from both function into __tasklet_schedule_common()
and let both functions invoke it with different arguments.
Signed-off-by: Ingo Molnar
Signed-off-by: Steven Rostedt
Signed-off-by: T
From: Ingo Molnar
tasklet_action() + tasklet_hi_action() are almost identical.
Move the common code from both function into __tasklet_schedule_common()
and let both functions invoke it with different arguments.
Signed-off-by: Ingo Molnar
Signed-off-by: Steven Rostedt
Signed-off-by: Thomas Glei
Ingo made a RT patch a few years back called "tasklet: Prevent tasklets
from going into infinite spin in RT" [0]. I ripped the non-RT pieces out
of it and here they are. I kept him as the original Author.
[0]
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/tree/patches/taskl
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 9e343e87d2c4c707ef8fae2844864d4dde3a2d13 upstream.
The map_word_() functions, dating back to linux-2.6.8, try to perform
bitwise operations on a 'map_word' structure. This
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit ded4c39e93f3 upstream.
Function identifiers are a 32bit, unsigned quantity. But we never
tell so to the compiler, resulting in the following:
4ac: b26187e0mov
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans Verkuil
commit b2469c814fbc8f1f19676dd4912717b798df511e upstream.
Don't duplicate the buffer type checks in enum/g/s/try_fmt.
The check_fmt function does that already.
It is hard to keep
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 9fa68f620041be04720d0cbfb1bd3ddfc6310b24 upstream.
Currently, almost none of the keyed hash algorithms check whether a key
has been set before proceeding. Some algorithms
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit e78eef554a91 upstream.
Since PSCI 1.0 allows the SMCCC version to be (indirectly) probed,
let's do that at boot time, and expose the version of the calling
convention as p
The patch
ASoC: uniphier: remove redundant check of blk_id
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit a208fa8f33031b9e0aba44c7d1b7e68eb0cbd29e upstream.
We need to consistently enforce that keyed hashes cannot be used without
setting the key. To do this we need a reliable
On Thu, Feb 15, 2018 at 9:20 AM, Eric Dumazet wrote:
>
> Yes, it seems tun.c breaks the assumptions.
>
> If it really wants to provide arbitrary fragments and alignments, it
> should use a separate
Sorry, I have sent the message to soon.
tun.c should use a private 'struct page_frag_cache' to del
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit fa59b92d299f2787e6bae1ff078ee0982e80211f upstream.
When the mcryptd template is used to wrap an unkeyed hash algorithm,
don't install a ->setkey() method to the mcryptd ins
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 841a3ff329713f796a63356fef6e2f72e4a3f6a3 upstream.
When the cryptd template is used to wrap an unkeyed hash algorithm,
don't install a ->setkey() method to the cryptd insta
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit 09a8d6d48499 upstream.
In order to call into the firmware to apply workarounds, it is
useful to find out whether we're using HVC or SMC. Let's expose
this through the psci
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit cd6ed77ad5d223dc6299fb58f62e0f5267f7e2ba upstream.
Templates that use an shash spawn can use crypto_shash_alg_has_setkey()
to determine whether the underlying algorithm req
On Wed, Feb 14, 2018 at 01:48:27PM +0100, Geert Uytterhoeven wrote:
> Hi Jacopo,
>
> Thanks for your patch!
>
> On Tue, Feb 13, 2018 at 10:45 AM, Jacopo Mondi
> wrote:
> > Add support for R-Car M3-N (r8a77965) power areas and reset.
> > M3-N power areas are identical to M3-W ones, so just copy a
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ivan Vecera
commit ba87977a49913129962af8ac35b0e13e0fa4382d upstream.
Commit b7ce40cff0b9 ("kernfs: cache atomic_write_len in
kernfs_open_file") changes type of local variable 'len' from ssize
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit 998008b779e424bd7513c434d0ab9c1268459009 upstream.
Add PCI ids for Intel Bay Trail, Cherry Trail and Apollo Lake AHCI
SATA controllers. This commit is a preparation patch
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 49686cbbb3ebafe42e63868222f269d8053ead00 upstream.
nfs_idmap_legacy_upcall() is supposed to be called with 'aux' pointing
to a 'struct idmap', via the call to request_key_w
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 8634ef5e05311f32d7f2aee06f6b27a8834a3bd6 upstream.
The LOOKUPP operation was inserted into the nfs4_procedures array
rather than being appended, which put /proc/net/rpc/
The patch
ASoC: TSCS42xx: make const array norm_addrs static, reduces object code size
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 7f1bda447c9bd48b415acedba6b830f61591601f upstream.
The commit list can get very large, and so we need a cond_resched()
in nfs_commit_release_pages() in order to ensure w
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Scott Mayhew
commit ba4a76f703ab7eb72941fdaac848502073d6e9ee upstream.
Currently when falling back to doing I/O through the MDS (via
pnfs_{read|write}_through_mds), the client frees the nfs_pg
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Bradley Bolen
commit 7f29ae9f977bcdc3654e68bc36d170223c52fd48 upstream.
This fixes a race with idr_alloc where gd->first_minor can be set to the
same value for two simultaneous calls to ubiblo
On 14/02/18 19:26, Stefano Stabellini wrote:
> Hi all,
>
> this small series introduces a per socket refcount to increase the
> efficiency on socket release operations, and makes releasing passive
> sockets safe.
>
> Cheers,
>
> Stefano
>
>
> Changes in v3:
> - remove pointless initializers
>
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Clay McClure
commit a51a0c8d213594bc094cb8e54aad0cb6d7f7b9a6 upstream.
Similar to commit 714fb87e8bc0 ("ubi: Fix race condition between ubi
device creation and udev"), we should make the volum
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Miquel Raynal
commit f4c6cd1a7f2275d5bc0e494b21fff26f8dde80f0 upstream.
When the requested ECC strength does not exactly match the strengths
supported by the ECC engine, the driver is selectin
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Miquel Raynal
commit 87e89ce8d0d14f573c068c61bec2117751fb5103 upstream.
Starting from commit 041e4575f034 ("mtd: nand: handle ECC errors in
OOB"), nand_do_read_oob() (from the NAND core) did r
On 15/02/18 16:08, Lukas Senger wrote:
@@ -20,18 +21,20 @@
target = <&gpio>;
__overlay__ {
pps_pins: pps_pins@12 {
- brcm,pins = <18>;
- brcm,function = <0>;// in
-
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Kamal Dasu
commit f953f0f89663c39f08f4baaa8a4a881401b65654 upstream.
Brcm nand controller prefetch feature needs to be disabled
by default. Enabling affects performance on random reads as
well
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit 6167ec5c9145 upstream.
A new feature of SMCCC 1.1 is that it offers firmware-based CPU
workarounds. In particular, SMCCC_ARCH_WORKAROUND_1 provides
BP hardening for CVE-20
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
Commit 669474e772b9 upstream.
For CPUs capable of data value prediction, CSDB waits for any outstanding
predictions to architecturally resolve before allowing speculative executio
On Thu, Feb 15, 2018 at 07:22:46AM -0800, Tejun Heo wrote:
> On Wed, Feb 14, 2018 at 10:40:43AM -0600, Josh Poimboeuf wrote:
> > The jump_label code doesn't patch init code, so this tracepoint can
> > never be enabled. Remove it.
> >
> > Cc: Tejun Heo
> > Signed-off-by: Josh Poimboeuf
>
> Appl
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
Commit f167211a93ac upstream.
We don't fully understand the Cavium ThunderX erratum, but it appears
that mapping the kernel as nG can lead to horrible consequences such as
attempt
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
Commit 4e6020565596 upstream.
Break-before-make is not needed when transitioning from Global to
Non-Global mappings, provided that the contiguous hint is not being used.
Signed-o
On Thu, Feb 15, 2018 at 02:49:44AM +, Kuninori Morimoto wrote:
>
> Hi Stephen
>
> Thank you for reporting.
> It is my fault, this patch might cause other issue.
> I'm asking to Mark to remove it from his branch.
Dropped.
signature.asc
Description: PGP signature
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit 6dc52b15c4a4 upstream.
Cavium ThunderX's erratum 27456 results in a corruption of icache
entries that are loaded from memory that is mapped as non-global
(i.e. ASID-tagged
On Thu, Feb 15, 2018 at 09:24:36AM -0800, Eric Dumazet wrote:
> On Thu, Feb 15, 2018 at 9:20 AM, Eric Dumazet wrote:
> >
> > Yes, it seems tun.c breaks the assumptions.
> >
> > If it really wants to provide arbitrary fragments and alignments, it
> > should use a separate
>
> Sorry, I have sent th
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
Commit f992b4dfd58b upstream.
Defaulting to global mappings for kernel space is generally good for
performance and appears to be necessary for Cavium ThunderX. If we
subsequently
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit 84684fecd7ea upstream.
Instead of open coding the accesses to the various registers,
let's add explicit SMCCC accessors.
Reviewed-by: Christoffer Dall
Tested-by: Ard Bie
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit 90348689d500 upstream.
For those CPUs that require PSCI to perform a BP invalidation,
going all the way to the PSCI code for not much is a waste of
precious cycles. Let's
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit f5115e8869e1 upstream.
When handling an SMC trap, the "preferred return address" is set
to that of the SMC, and not the next PC (which is a departure from
the behaviour of
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit 58e0b2239a4d upstream.
PSCI 1.0 can be trivially implemented by providing the FEATURES
call on top of PSCI 0.2 and returning 1.0 as the PSCI version.
We happily ignore ev
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jayachandran C
Commit f3d795d9b360 upstream.
Use PSCI based mitigation for speculative execution attacks targeting
the branch predictor. We use the same mechanism as the one used for
Cortex-A
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
Commit 41acec624087 upstream.
To allow systems which do not require kpti to continue running with
global kernel mappings (which appears to be a requirement for Cavium
ThunderX due
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Shanker Donthineni
Commit ec82b567a74f upstream.
Falkor is susceptible to branch predictor aliasing and can
theoretically be attacked by malicious code. This patch
implements a mitigation for
On Thu, Feb 15, 2018 at 02:22:39PM +, Will Deacon wrote:
> Assuming others agree with this diagnosis, I'm not sure how to fix it.
> It's basically not safe to set current->mm = NULL with preemption enabled.
One thing we could try would be to leave current->mm alone and just do the
mmdrop in fi
On Sun, Feb 04, 2018 at 04:50:58PM +, JackStocker wrote:
> Following on from this patch: https://lkml.org/lkml/2017/11/3/516,
> Corsair K70 RGB keyboards also require the DELAY_INIT quirk to
> start correctly at boot.
>
> Device ids found here:
> usb 3-3: New USB device found, idVendor=1b1c, i
Platform drivers need make a lot of resource state requests at the same
time, say, at the start or end of an usecase. It can be quite
inefficient to send each request separately. Instead they can give the
RPMH library a batch of requests to be sent and wait on the whole
transaction to be complete.
Allow sleep and wake commands to be cleared from the respective TCSes,
so that they can be re-populated.
Signed-off-by: Lina Iyer
---
drivers/soc/qcom/rpmh-internal.h | 1 +
drivers/soc/qcom/rpmh-rsc.c | 46
2 files changed, 47 insertions(+)
diff -
Changes in v2:
- Added sleep/wake, async and batch requests support
- Addressed Bjorn's comments
- Private FTRACE for drivers/soc/qcom as suggested by Steven
- Sparse checked on these patches
- Use SPDX license commenting sytle
This set of patches add the ability for platform drivers to make use o
Some RSCs may only have sleep and wake TCS, i.e, there is no dedicated
TCS for active mode request, but drivers may still want to make active
requests from these RSCs. In such cases re-purpose the wake TCS to send
active state requests.
The requirement for this is that the driver is aware that the
Log sent RPMH requests and interrupt responses in FTRACE.
Cc: Steven Rostedt
Signed-off-by: Lina Iyer
---
drivers/soc/qcom/Makefile | 1 +
drivers/soc/qcom/rpmh-rsc.c | 6 +++
drivers/soc/qcom/trace-rpmh.h | 89 +++
3 files changed, 96 insertions(
Dave Hansen wrote:
> On 02/15/2018 08:36 AM, Nadav Amit wrote:
>> As long as PTI is disabled, it is possible to use global pages, as long
>> as we remove them once PTI is enabled again. To do so, return the global
>> bit to __supported_pte_mask and disable global pages using CR4.
>>
>> Signed-of
Platform drivers that want to send a request but do not want to block
until the RPMH request completes have now a new API -
rpmh_write_async().
The API allocates memory and send the requests and returns the control
back to the platform driver. The tx_done callback from the controller is
handled in
On Wed, Feb 14, 2018 at 07:40:50PM -0800, Matthew Wilcox wrote:
> > a_foo = kvzalloc_struct_buf(struct foo, struct bar, nr_bars);
> >
> > or, of course.
> >
> > a_foo = kvzalloc_struct_buf(typeof(*a_foo), typeof(a_foo->bar[0]),
> > nr_bars);
> >
> > or wha
Active state requests are sent immediately to the mailbox controller,
while sleep and wake state requests are cached in this driver to avoid
taxing the mailbox controller repeatedly. The cached values will be sent
to the controller when the rpmh_flush() is called.
Generally, flushing is a system P
On Mon, Feb 12, 2018 at 12:15:03PM -0800,
sathyanarayan.kuppusw...@linux.intel.com wrote:
> From: Dominik Bozek
>
> ACM driver may accept data to transmit while system is not fully
> resumed. In this case ACM driver buffers data and prepare URBs
> on usb anchor list.
> There is a little chance t
Acked-by: Steve Longerbeam
On 02/15/2018 01:25 AM, Parthiban Nallathambi wrote:
This is a cleanup patch to fix line length issue found
by checkpatch.pl script.
In this patch, line 144 have been wrapped.
Signed-off-by: Parthiban Nallathambi
---
Changes in v2:
- Changed commit message
driv
Add device binding documentation for Qualcomm Technology Inc's RPMH RSC
driver. The hardware block is used for communicating resource state
requests for shared resources.
Cc: devicet...@vger.kernel.org
Signed-off-by: Lina Iyer
---
.../devicetree/bindings/arm/msm/rpmh-rsc.txt | 146
Add controller driver for QCOM SoCs that have hardware based shared
resource management. The hardware IP known as RSC (Resource State
Coordinator) houses multiple Direct Resource Voter (DRV) for different
execution levels. A DRV is a unique voter on the state of a shared
resource. A Trigger Control
Sending RPMH requests and waiting for response from the controller
through a callback is common functionality across all platform drivers.
To simplify drivers, add a library functions to create RPMH client and
send resource state requests.
rpmh_write() is a synchronous blocking call that can be us
Sleep and wake requests are sent when the application processor
subsystem of the SoC is entering deep sleep states like in suspend.
These requests help lower the system power requirements when the
resources are not in use.
Sleep and wake requests are written to the TCS slots but are not
triggered
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
Commit a65d219fe5dc upstream.
Hook up MIDR values for the Cortex-A72 and Cortex-A75 CPUs, since they
will soon need MIDR matches for hardening the branch predictor.
Signed-off-by
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
Commit 0f15adbb2861 upstream.
Aliasing attacks against CPU branch predictors can allow an attacker to
redirect speculative control flow on some CPUs and potentially divulge
inform
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
Commit 30d88c0e3ace upstream.
It is possible to take an IRQ from EL0 following a branch to a kernel
address in such a way that the IRQ is prioritised over the instruction
abort. W
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit a8e4c0a919ae upstream.
We call arm64_apply_bp_hardening() from post_ttbr_update_workaround,
which has the unexpected consequence of being triggered on every
exception retu
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit 6840bdd73d07 upstream.
Now that we have per-CPU vectors, let's plug then in the KVM/arm64 code.
Signed-off-by: Marc Zyngier
Signed-off-by: Will Deacon
Signed-off-by: Ca
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
Commit 95e3de3590e3 upstream.
We will soon need to invoke a CPU-specific function pointer after changing
page tables, so move post_ttbr_update_workaround out into C code to make
t
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
Commit d68e3ba5303f upstream.
Entry into recent versions of ARM Trusted Firmware will invalidate the CPU
branch predictor state in order to protect against aliasing attacks.
This
801 - 900 of 1436 matches
Mail list logo
