Upstreamed Android kernel from v3.18.120 to v3.18.132

---

Link to the github repository :-

• https://github.com/TheStreak969/kernel_oneplus_msm8996/

---

What is a linux kernel?

The linux kernel is a Organization established in 2002 to distribute the linux kernel & other opensource software to public without charge. The linux kernel org is maintained by the linux foundation

---

Why linux kernel is only used in Android Devices?

linux kernel is an open source project which means everyone can make modification & enhancements to meet mobile o/s requirements like better memory optimisations,Ram managements & better performance.

---

Description

So today i finally managed to Upstream My Android Kernel From v3.18.120 to v3.18.132 there are more than 200+ patches to pick & so many conflicts to solve Some of my patches are linked below withits description..........

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/5682aab08b1b6447b78612ca22723f832f4a6cc4
  Here I merged the v3.18.132 tag

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/f47cc9a1c030d2726463723eca0898750f093369

Description:-

Other filesystems such as ext4, f2fs and ubifs all return ENXIO when
lseek (SEEK_DATA or SEEK_HOLE) requests a negative offset.
man 2 lseek says

: EINVAL whence is not valid. Or: the resulting file offset would be
: negative, or beyond the end of a seekable device.
:
: ENXIO whence is SEEK_DATA or SEEK_HOLE, and the file offset is beyond
: the end of the file.

Make tmpfs return ENXIO under these circumstances as well. After this,
tmpfs also passes xfstests's generic/448.

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/5e77a3cec9785a4c9eb45c12015ad3e63bd7c620

Description:-

" This patch factors out all non sending parts of can_get_echo_skb() into
a seperate function __can_get_echo_skb(), so that it can be re-used in
an upcoming patch. "

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/0ab93875c16343cf8fb252ad7805393c27f9e96c

Description:-

After building the kernel with Clang, the following section mismatch
warning appears:

WARNING: vmlinux.o(.text+0x3bf19a6): Section mismatch in reference from
the function ssc_probe() to the function
.init.text:atmel_ssc_get_driver_data()
The function ssc_probe() references
the function __init atmel_ssc_get_driver_data().
This is often because ssc_probe lacks a __init
annotation or the annotation of atmel_ssc_get_driver_data is wrong.

Remove __init from atmel_ssc_get_driver_data to get rid of the mismatch.

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/a4f47937442cca6cfdba8a21e8a55ac952e1dd9f

Description:-

There are some cases can cause memory leak when parsing
option 'osdname'.

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/23b7a8492e086427f0ee0cd21f33e48a0a229af1

Description:-

I noticed during the creation of another bugfix that the BCH_CONST_PARAMS
option that is set by DOCG3 breaks setting variable parameters for any
other users of the BCH library code.
To avoid the immediate problem of the conflict between MTD_NAND_BCH
and DOCG3, this only sets the constant parameters if MTD_NAND_BCH
is disabled, which should fix the problem for all cases that
are affected. This should also work for all stable kernels.

Note that there is only one machine that actually seems to use the
DOCG3 driver (arch/arm/mach-pxa/mioa701.c), so most users should have
the driver disabled, but it almost certainly shows up if we wanted
to test random kernels on machines that use software BCH in MTD.

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/d56cb5949e9f3f254663266ee735b4dcea19e206

Description:-

There is another cast from unsigned long to int which causes
a bounds check to fail with specially crafted input. The value is
then used as an index in the slot array in cdrom_slot_status().

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/9c0bb88b9c948bf5cfa50edceb57b2b296fdf200

Description:-

media: tvp5150: fix width alignment during set_selection()
The driver ignored the width alignment which exists due to the UYVY
colorspace format. Fix the width alignment and make use of the the
provided v4l2 helper function to set the width, height and all
alignments in one.

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/4e4541ef1bf8d4e79b115c7325a603241267d2ef

Description:-

media: em28xx: make v4l2-compliance happier by starting sequence on zero
The v4l2-compliance tool complains if a video doesn't start
with a zero sequence number.

While this shouldn't cause any real problem for apps, let's
make it happier, in order to better check the v4l2-compliance
differences before and after patchsets.

This is actually an old issue. It is there since at least its
videobuf2 conversion, e. g. changeset 3829fadc461 ("[media]
em28xx: convert to videobuf2"), if VB1 wouldn't suffer from
the same issue.

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/07d0eca50cb64c5f9251720ad23c7f00f0d6c5df|

Description:-

w1: omap-hdq: fix missing bus unregister at removal
The bus master was not removed after unloading the module
or unbinding the driver. That lead to oopses like this
In Logs ( adb logcat -b kernel kernel.log ) i found this-
[ 127.842987] Unable to handle kernel paging request at virtual address bf01d04c
[ 127.850646] pgd = 70e3cd9a
[ 127.853698] [bf01d04c] *pgd=8f908811, *pte=00000000, *ppte=00000000
[ 127.860412] Internal error: Oops: 80000007 [#1] PREEMPT SMP ARM
[ 127.866668] Modules linked in: bq27xxx_battery overlay [last unloaded: omap_hdq]
[ 127.874542] CPU: 0 PID: 1022 Comm: w1_bus_master1 Not tainted 4.19.0-rc4-00001-g2d51da718324 #12
[ 127.883819] Hardware name: Generic OMAP36xx (Flattened Device Tree)
[ 127.890441] PC is at 0xbf01d04c
[ 127.893798] LR is at w1_search_process_cb+0x4c/0xfc
[ 127.898956] pc : [bf01d04c] lr : [c05f9580] psr: a0070013
[ 127.905609] sp : cf885f48 ip : bf01d04c fp : ddf1e11c
[ 127.911132] r10: cf8fe040 r9 : c05f8d00 r8 : cf8fe040
[ 127.916656] r7 : 000000f0 r6 : cf8fe02c r5 : cf8fe000 r4 : cf8fe01c
[ 127.923553] r3 : c05f8d00 r2 : 000000f0 r1 : cf8fe000 r0 : dde1ef10
[ 127.930450] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none
[ 127.938018] Control: 10c5387d Table: 8f8f0019 DAC: 00000051
[ 127.944091] Process w1_bus_master1 (pid: 1022, stack limit = 0x9135699f)
[ 127.951171] Stack: (0xcf885f48 to 0xcf886000)
[ 128.037017] 5fa0: 00000000 00000000 00000000 00000000
[ 128.045684] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 128.054351] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 128.061340] Code: bad PC value
[ 128.064697] ---[ end trace af066e33c0e14119 ]---

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/ff4ba6d23122fc821693972c4e24bd31bb30d3ae

Description:-

The genweq_add_file and genwqe_del_file by caching current without
using reference counting embed the assumption that a file descriptor
will never be passed from one process to another. It even embeds the
assumption that the the thread that opened the file will be in
existence when the process terminates. Neither of which are
guaranteed to be true.

Therefore replace caching the task_struct of the opener with
pid of the openers thread group id. All the knowledge of the
opener is used for is as the target of SIGKILL and a SIGKILL
will kill the entire process group.
It will still be possible to cause genwqe_device_remove to wait
8 seconds by passing a file descriptor to another process but
the possible user after free is fixed.

Fixes:GenWQE Character device and DDCB queue.

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/2eff4c24d3984b4af924d1e6f6e722df768f8195

Description:-

If the starting block number of either the source or destination file
exceeds the EOF, EXT4_IOC_MOVE_EXT should return EINVAL.

Also fixed the helper function mext_check_coverage() so that if the
logical block is beyond EOF, make it return immediately, instead of
looping until the block number wraps all the away around. This takes
long enough that if there are multiple threads trying to do pound on
an the same inode doing non-sensical things, it can end up triggering
the kernel's soft lockup detector.

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/ce0ea118a99224c4c260c27e2798d0b28fc9e58a

Description:-

net: stmmac: Fix stmmac_mdio_reset() when building stmmac as modules
When building stmmac, it is only possible to select CONFIG_DWMAC_GENERIC,
or any of the glue drivers, when CONFIG_STMMAC_PLATFORM is set.
The only exception is CONFIG_STMMAC_PCI.

When calling of_mdiobus_register(), it will call our ->reset()
callback, which is set to stmmac_mdio_reset().

Most of the code in stmmac_mdio_reset() is protected by a
"#if defined(CONFIG_STMMAC_PLATFORM)", which will evaluate
to false when CONFIG_STMMAC_PLATFORM=m.

Because of this, the phy reset gpio will only be pulled when
stmmac is built as built-in, but not when built as modules.

Fix this by using "#if IS_ENABLED()" instead of "#if defined()".

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/4ae48cdff6b731c98033d95569316180b97c7f9c

Description:-

Now, with commit b94f1c0 ("ipv6: Use icmpv6_notify() to propagate
redirect, instead of rt6_redirect()."), we call protocol error handlers
from ndisc_redirect_rcv(), after the control buffer is already stolen and
some parts are already zeroed out. This implies that inet6_iif() on this
path will always return zero.

This gives unexpected results on UDP socket lookup in __udp6_lib_err(), as
we might actually need to match sockets for a given interface.

Instead of always claiming the control buffer in ndisc_rcv(), do that only
when needed.

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/9c0da6ffc297dd9244b1bd6b945a5a978089b4ba|

Description:-

Mark Home Agent 1 as having non-compliant BARs so the PCI core doesn't
touch them.

The problem with these devices is documented in the Xeon v4 specification
update:

BDF2 PCI BARs in the Home Agent Will Return Non-Zero Values
During Enumeration

Problem: During system initialization the Operating System may access
the standard PCI BARs (Base Address Registers). Due to
this erratum, accesses to the Home Agent BAR registers (Bus
1; Device 18; Function 0,4; Offsets (0x14-0x24) will return
non-zero values.

Implication: The operating system may issue a warning. Intel has not
observed any functional failures due to this erratum.

---

• https://github.com/TheStreak969/kernel_oneplus_msm8996/commit/41b3d8bd0e6a212f8c78ef45e2a5c20398fc932b|

Description:-

ovl: fix open in stacked overlay
If two overlayfs filesystems are stacked on top of each other, then we need
recursion in ovl_d_select_inode().

I guess d_backing_inode() is supposed to do that. But currently it doesn't
and that functionality is open coded in vfs_open(). This is now copied
into ovl_d_select_inode() to fix this regression.

---

Proof Of My Work:- Here is the ScreenShot of my login Session in Github

---

My Github Profile:- https://github.com/TheStreak969/

I hope u liked my 1st post on utopian-io. Thanks ;)

---