Remove CONFIG_ATL1C and CONFIG_QCOM_EMAC which are causing the KW
issues. These configs are anyway not required for any functionality
for SVM.
Change-Id: I64ecdda547760a00936e3cf9cbfc98cb24d6f39c
Signed-off-by: Murali Nalajala <mnalajal@codeaurora.org>
There is a use after free scenario while iterating through the servers
radix tree despite the ns being a single threaded process. This can
happen when the radix tree APIs are not synchronized with the
rcu_read_lock() APIs.
Convert the radix tree for servers to xarray to take advantage of the
built in rcu lock usage provided by xarray.
Change-Id: I1d9b017da4efba9d8fc72e4666253060cc7b87e3
Signed-off-by: Chris Lew <clew@codeaurora.org>
There is a use after free scenario while iterating through the servers
radix tree despite the ns being a single threaded process. This can
happen when the radix tree APIs are not synchronized with the
rcu_read_lock() APIs.
Convert the radix tree for nodes to xarray to take advantage of the
built in rcu lock usage provided by xarray.
Change-Id: If2f735abf911b7b47cd7cb07224751114a2bf943
Signed-off-by: Chris Lew <clew@codeaurora.org>
Add compatible string with offset value for sdxlemur.
Change-Id: Icf20202f1e603321dd9744e85426f08940cc8f68
Signed-off-by: Chris Lew <clew@codeaurora.org>
Disable SDCARD_FS for Android compliance for full switchover
to fusefs.
Change-Id: I54921f9651dec266b1aae51f075c95c71e670f34
Signed-off-by: David Ng <dave@codeaurora.org>
This ops is used to force off a clock when clk_disable() is called. CLK_DIS
bit can be used to force off respective clock.
Change-Id: Iec4204fe3bf24965d1603d0f86e74cc2818e3d1c
Signed-off-by: Vivek Aknurwar <viveka@codeaurora.org>
Needed by some GPU/DRM drivers that are built out-of-tree
Bug: 159733980
Signed-off-by: Todd Kjos <tkjos@google.com>
Change-Id: Ia156d1b0a74c82d9f15b144131aff2ddeead0672
The binder driver makes the assumption proc->context pointer is invariant after
initialization (as documented in the kerneldoc header for struct proc).
However, in commit f0fe2c0f050d ("binder: prevent UAF for binderfs devices II")
proc->context is set to NULL during binder_deferred_release().
Another proc was in the middle of setting up a transaction to the dying
process and crashed on a NULL pointer deref on "context" which is a local
set to &proc->context:
new_ref->data.desc = (node == context->binder_context_mgr_node) ? 0 : 1;
Here's the stack:
[ 5237.855435] Call trace:
[ 5237.855441] binder_get_ref_for_node_olocked+0x100/0x2ec
[ 5237.855446] binder_inc_ref_for_node+0x140/0x280
[ 5237.855451] binder_translate_binder+0x1d0/0x388
[ 5237.855456] binder_transaction+0x2228/0x3730
[ 5237.855461] binder_thread_write+0x640/0x25bc
[ 5237.855466] binder_ioctl_write_read+0xb0/0x464
[ 5237.855471] binder_ioctl+0x30c/0x96c
[ 5237.855477] do_vfs_ioctl+0x3e0/0x700
[ 5237.855482] __arm64_sys_ioctl+0x78/0xa4
[ 5237.855488] el0_svc_common+0xb4/0x194
[ 5237.855493] el0_svc_handler+0x74/0x98
[ 5237.855497] el0_svc+0x8/0xc
The fix is to move the kfree of the binder_device to binder_free_proc()
so the binder_device is freed when we know there are no references
remaining on the binder_proc.
Fixes: f0fe2c0f050d ("binder: prevent UAF for binderfs devices II")
Signed-off-by: Todd Kjos <tkjos@google.com>
(cherry picked from commit d35d3660e065b69fdb8bf512f3d899f350afce52
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-linus)
Bug: 158252621
Change-Id: Iee9547d58b85794af034b78eaab47075f3635f82
During crash shutdown, system is in panic mode and all
interrupts are disabled. Thus when doing CNSS pci register
dump collection do not lock. Use spinlock during normal
operation only.
Change-Id: I82dc531e93c13aa583e8162b8dc7e8866f86c48b
Signed-off-by: Manikandan Mohan <manikand@codeaurora.org>
Add support for building using the lahaina-qgki-consolidate_defconfig
which consists of the QGKI + consolidate fragments.
Change-Id: Ie6bf7e564560a808a67f2c65bcb63e099f43e4f4
Signed-off-by: Jack Pham <jackp@codeaurora.org>
In current implementation the Linux version string that is attached to
the kernel linux image as well as the all kernel modules includes the
sha1 of the main git project for the kernel.
This Commit adds the BUILD_NUMBER env variable with an 'ab' prefix to
the Linux version string. This maps to both the Linux Image and all
kernel modules version strings.
Bug: 159842160
Bug: 137521202
Test: Build the kernel and test the version string
Change-Id: I4795955f36f477b257ca86495726e24d6b196d05
Signed-off-by: Alex Hong <rurumihong@google.com>
(cherry picked from commit e60f995403c9799dd0dc14d62d77d6698a8a7126)
[willmcvicker: fix uts_len check to include -ab$(BUILD_NUMBER)]
Signed-off-by: Will McVicker <willmcvicker@google.com>
Common change to add required symbols to the whitelist.
Change-Id: I799bb1b8b2e637d6a5570ff82b8040447a9bf0e7
Signed-off-by: Siddharth Gupta <sidgup@codeaurora.org>
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Enable system_pm_violators debug driver to read and report DRVs that are
preventing system low power modes.
Change-Id: I0e10010b6df3670c05d3d7aa5aed3581f664ec81
Signed-off-by: Lina Iyer <ilina@codeaurora.org>
Use lock_device_hotplug() inplace of lock_device_hotplug_sysfs() as the
latter can return immediately if there are any parallel
onlining/offlining of memory blocks.
Change-Id: Ica3cc286b7d4f87310f86e8c9e6db2157e511419
Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
Change the VM_MAX_READAHEAD value from the default 128KB
to 512KB. This will allow the readahead window to grow to a maximum size
of 512KB, which greatly benefits to sequential read throughput.
Change-Id: Ia0780ea4e2a4ae0b6111485b72fb25376dcb1f96
Signed-off-by: Lee Susman <lsusman@codeaurora.org>
[vinmenon@codeaurora.org: switch to VM_READAHEAD_PAGES on 5.4]
Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
fault_around aims to reduce minor faults of file-backed pages via
speculative ahead pte mapping and relying on readahead logic. However,
on non-HW access bit architecture the benefit is highly limited because
they should emulate the young bit with minor faults for reclaim's page
aging algorithm. IOW, we cannot reduce minor faults on those
architectures.
I did quick a test on my ARM machine.
512M file mmap sequential every word read on eSATA drive 4 times.
stddev is stable.
= fault_around 4096 =
elapsed time(usec): 6747645
= fault_around 65536 =
elapsed time(usec): 6709263
0.5% gain.
Even when I tested it with eMMC there is no gain because I guess with
slow storage the major fault is the dominant factor.
Also, fault_around has the side effect of shrinking slab more
aggressively and causes higher vmpressure, so if such speculation fails,
it can evict slab more which can result in page I/O (e.g., inode cache).
In the end, it would make void any benefit of fault_around.
So let's make the default "disabled" on those architectures.
Change-Id: I5e6b74943c95f6779b3a6e463b4d0a8b27eaac01
Link: http://lkml.kernel.org/r/20160518014229.GB21538@bbox
Signed-off-by: Minchan Kim <minchan@kernel.org>
Cc: Kirill A. Shutemov <kirill@shutemov.name>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Git-commit: d0834a6c2c
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
[vinmenon@codeaurora.org: trivial merge conflict fixes]
Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
We allow pages to movable zone only when __GFP_CMA is set along with
other required flags. When an anon page first allocated will
go to the movable zone but when the same is swapped out and then swapin
is not allowed to go. Fix it.
Fixes: 0157fbd79dbe ("mm: Allow only __GFP_CMA allocations from Movable zone")
Change-Id: I746299259a91819499e948ca34fe8880c8eaa175
[guptap@codeaurora.org: Fixed minor merge conflicts]
Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
Update the clock IDs which are required and supported from the Graphics
clock controller on HOLI.
Change-Id: I8f16d0ff3ed42500521c8384cd8272ce9d5b9d22
Signed-off-by: Taniya Das <tdas@codeaurora.org>
In the cases where the branch clocks requires to vote on a voltage rail
add the clock ops callbacks for the same.
Change-Id: If7ffbc4fdda1fb71c1d097f56a5eb762859eb2c4
Signed-off-by: Taniya Das <tdas@codeaurora.org>
The qcom_clk_set_flags API would be used to set/clear the memory
flags for the desired branches.
Change-Id: I58b2347f63d382168b61dd04ead57ad114559eb2
Signed-off-by: Taniya Das <tdas@codeaurora.org>
Add clock IDs for GCC and APSSCC clients to be able to request
for clocks from these clock controllers.
Change-Id: Ifc6acdbd05398e2f501cdc2cfb8694b16eb9b866
Signed-off-by: Naveen Yadav <naveenky@codeaurora.org>
If we made an active request on a RSC that does not have a dedicated TCS
for active state use, then re-purposed wake TCSes should be checked for not
busy before setting solver mode.
Change-Id: I8a493f4ac15d31df5b1963e5ae0d5d9966b482cc
Signed-off-by: Maulik Shah <mkshah@codeaurora.org>
DEBUGFS will be disabled on android R perf builds. Since tz logs
are dependent on debugfs, CONFIG_MSM_TZ_LOG needs to be removed
as well.
Change-Id: I88211eb98cfbf64b2fe444c8fc0d4e122bebf7cb
Signed-off-by: Prerna Kalla <prernak@codeaurora.org>
Add support for creating the audio ML CMA heap. This heap will
be used to provide machine learning (ML) information to audio
hardware, which can only use physically contiguous memory.
Change-Id: I7b4677c7a178d3fc8592a43cac08799e8124fefe
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
Add support for mapping memory to/from VMID_ADSP_HEAP and VMID_LPASS.
Change-Id: Ie479de719cbfbccb726b3284665573806958ac89
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
iommu_debugfs_top was introduced in earlier kernel versions when
IOMMU_DEBUGFS was not present. Now that IOMMU_DEBUGFS is present,
and exposes iommu_debugfs_dir, which is logically equivalent to
iommu_debugfs_top, there is no point in keeping it around, so
remove it.
Change-Id: I7032e370ccfd32f9d2b9046fecd98b4c6388450f
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
Refactor IOMMU pagetable page accounting code into a config option
so that it only includes additional headers in configurations where
the page accounting feature is needed. Doing so prevents the
definition of certain structures from being expanded, which can
affect the CRC value generated for exported symbols in module.symvers.
Change-Id: Idd6fc0e1cbb46ace211971ac142be491d0a5ab09
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
For certain use cases SID remains same and when an
smmu page fault occurs it becomes difficult for client
to identify which of the usecases is actually causing
the fault. In such cases MID/PID/BID info can help.
So, add a function for the same so that clients can
call this from their fault handler and get the info.
Change-Id: Ia720641224f908287ae1d66908ab12def82bbbab
Signed-off-by: Vijayanand Jitta <vjitta@codeaurora.org>
1. Fix to format context correctly as expected by
hardware for system KDF.
HWKM reverses bytes at a 8-byte boundary while getting
the context from cryptolib. Reformat the context in the
command packet in such a way that HWKM receives it in the
correct order. Also, pad the context to a 8-byte multiple
as the way HW would pad it is not expected.
2. Use context for FBE to match with the one
for VTS test cases.
Change-Id: I3c13c91b0dfc85aef406b05694dbd22afb0b2e0b
Signed-off-by: Gaurav Kashyap <gaurkash@codeaurora.org>
Currently when a flash/torch device is disabled, ITARGET of the channel
is programmed to 0 by qti_flash_led_disable() before the channel is
de-strobed. This is causing a ramp down of the flash LED channel during
disable. Fix this by programming target current to 0 only after channel
is de-strobed.
Change-Id: Ie566f4e75b8af8c27b7b9a828823a9bfddc48bb6
Signed-off-by: Shyam Kumar Thella <sthella@codeaurora.org>
Disable the flash LED channel when a brightness of 0 is set.
As flash/torch devices can be enabled and disabled using switch as well
as from sysfs, reset the state of flash/torch devices when they are
disabled instead of doing it in switch disable.
Change-Id: If8ffb22d8c72a94325a1e9237778b810a152a293
Signed-off-by: Shyam Kumar Thella <sthella@codeaurora.org>
Different configuration/condition may draw different power. Inform the
controller driver of the change so it can respond properly (e.g.
GET_STATUS request). This fixes an issue with setting MaxPower from
configfs. The composite driver doesn't check this value when setting
self-powered.
Cc: stable@vger.kernel.org
Fixes: 88af8bbe4e ("usb: gadget: the start of the configfs interface")
Signed-off-by: Thinh Nguyen <thinhn@synopsys.com>
Signed-off-by: Felipe Balbi <balbi@kernel.org>
Git-commit: 5e5caf4fa8d3039140b4548b6ab23dd17fce9b2c
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Change-Id: I96588f97d32c9b6d80302e601cb0cc8d771c1296
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
Use the uic_cmd->cmd_active as a flag to track the lifecycle of an UIC cmd.
The flag is set before send the UIC cmd and cleared after the completion is
raised in IRQ handler. For a power mode change operation, including hibern8
enter/exit, the flag is cleared only after hba->uic_async_done completion
is raised. When completion timeout happens, if the flag is cleared, instead
of returning timeout error, simply ignore it.
Change-Id: Ie3cd6ae6221a44619925fb2cf78136a5617fdd5d
Signed-off-by: Can Guo <cang@codeaurora.org>
5.4.49 changed some structure definitions in the USB gadget and sound
code, and we added some more padding in this area to prevent that from
happening in the future.
Because of that, update the abi.xml file with these changes.
Leaf changes summary: 2 artifacts changed
Changed leaf types summary: 2 leaf types changed
Removed/Changed/Added functions summary: 0 Removed, 0 Changed, 0 Added function
Removed/Changed/Added variables summary: 0 Removed, 0 Changed, 0 Added variable
'struct snd_usb_endpoint at card.h:54:1' changed:
type size changed from 44544 to 44992 (in bits)
9 data member insertions:
'unsigned int snd_usb_endpoint::framesize[2]', at offset 43744 (in bits) at card.h:89:1
'unsigned int snd_usb_endpoint::sample_rem', at offset 43808 (in bits) at card.h:90:1
'unsigned int snd_usb_endpoint::sample_accum', at offset 43840 (in bits) at card.h:91:1
'unsigned int snd_usb_endpoint::fps', at offset 43872 (in bits) at card.h:92:1
'bool snd_usb_endpoint::is_implicit_feedback', at offset 44512 (in bits) at card.h:113:1
'u64 snd_usb_endpoint::android_kabi_reserved1', at offset 44736 (in bits) at card.h:118:1
'u64 snd_usb_endpoint::android_kabi_reserved2', at offset 44800 (in bits) at card.h:119:1
'u64 snd_usb_endpoint::android_kabi_reserved3', at offset 44864 (in bits) at card.h:120:1
'u64 snd_usb_endpoint::android_kabi_reserved4', at offset 44928 (in bits) at card.h:121:1
there are data member changes:
'unsigned int snd_usb_endpoint::freqn' offset changed from 43744 to 43904 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::freqm' offset changed from 43776 to 43936 (in bits) (by +160 bits)
'int snd_usb_endpoint::freqshift' offset changed from 43808 to 43968 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::freqmax' offset changed from 43840 to 44000 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::phase' offset changed from 43872 to 44032 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::maxpacksize' offset changed from 43904 to 44064 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::maxframesize' offset changed from 43936 to 44096 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::max_urb_frames' offset changed from 43968 to 44128 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::curpacksize' offset changed from 44000 to 44160 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::curframesize' offset changed from 44032 to 44192 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::syncmaxsize' offset changed from 44064 to 44224 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::datainterval' offset changed from 44128 to 44288 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::syncinterval' offset changed from 44160 to 44320 (in bits) (by +160 bits)
'unsigned char snd_usb_endpoint::silence_value' offset changed from 44192 to 44352 (in bits) (by +160 bits)
'unsigned int snd_usb_endpoint::stride' offset changed from 44224 to 44384 (in bits) (by +160 bits)
'int snd_usb_endpoint::iface' offset changed from 44256 to 44416 (in bits) (by +160 bits)
'int snd_usb_endpoint::altsetting' offset changed from 44288 to 44448 (in bits) (by +160 bits)
'int snd_usb_endpoint::skip_packets' offset changed from 44320 to 44480 (in bits) (by +160 bits)
'spinlock_t snd_usb_endpoint::lock' offset changed from 44352 to 44544 (in bits) (by +192 bits)
'list_head snd_usb_endpoint::list' offset changed from 44416 to 44608 (in bits) (by +192 bits)
2 impacted interfaces
'struct usb_gadget at gadget.h:395:1' changed:
type size changed from 8256 to 8512 (in bits)
5 data member insertions:
'int usb_gadget::irq', at offset 8224 (in bits) at gadget.h:432:1
'u64 usb_gadget::android_kabi_reserved1', at offset 8256 (in bits) at gadget.h:434:1
'u64 usb_gadget::android_kabi_reserved2', at offset 8320 (in bits) at gadget.h:435:1
'u64 usb_gadget::android_kabi_reserved3', at offset 8384 (in bits) at gadget.h:436:1
'u64 usb_gadget::android_kabi_reserved4', at offset 8448 (in bits) at gadget.h:437:1
24 impacted interfaces
Bug: 151154716
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: Ic3fa7583c5b69b0984f4c7b711150b974bec5cc7
