Now replaced by dist build under dist/, only the config file and kABI
file are kept for a smooth transition.
Signed-off-by: Kairui Song <kasong@tencent.com>
[upstream commit dbcf24d153884439dad30484a0e3f02350692e4c]
Commit a02e8964eaf92 ("virtio-net: ethtool configurable LRO")
maps LRO to virtio guest offloading features and allows the
administrator to enable and disable those features via ethtool.
This leads to several issues:
- For a device that doesn't support control guest offloads, the "LRO"
can't be disabled triggering WARN in dev_disable_lro() when turning
off LRO or when enabling forwarding bridging etc.
- For a device that supports control guest offloads, the guest
offloads are disabled in cases of bridging, forwarding etc slowing
down the traffic.
Fix this by using NETIF_F_GRO_HW instead. Though the spec does not
guarantee packets to be re-segmented as the original ones,
we can add that to the spec, possibly with a flag for devices to
differentiate between GRO and LRO.
Further, we never advertised LRO historically before a02e8964eaf92
("virtio-net: ethtool configurable LRO") and so bridged/forwarded
configs effectively always relied on virtio receive offloads behaving
like GRO - thus even if this breaks any configs it is at least not
a regression.
Fixes: a02e8964eaf92 ("virtio-net: ethtool configurable LRO")
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Reported-by: Ivan <ivan@prestigetransportation.com>
Tested-by: Ivan <ivan@prestigetransportation.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Menglong Dong <imagedong@tencent.com>
When kernel rpm is installed, if selinux in the host is not set,
the function of selinux will be disabled.
Signed-off-by: Chun Liu <kaicliu@tencent.com>
Use drm_get_edid to get the resolution, if that fails, set it to
a fixed resolution. Rewrite the desrtoy callback function to release
resources.
Signed-off-by: Tian Tao <tiantao6@hisilicon.com>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
Adding driver implementation to support i2c driver algorithms for
bit-shift adapters, so hibmc will using the interface provided by
drm to read edid.
Signed-off-by: Tian Tao <tiantao6@hisilicon.com>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
driver inclusion
category: Bugfix
bugzilla: NA
CVE: NA
The resolution of line offset without 128 byte alignment under 16bpp
is adjusted to make it 128 byte aligned, so as to ensure GPU to access
its display memory space normally. At the same time, the initialization
color depth is 32bpp.
Signed-off-by: GongJunjie <gongjunjie2@huawei.com>
Reviewed-by: Xin Yin <yinxin.yinxin@huawei.com>
Reviewed-by: Weiwei Deng <dengweiwei@huawei.com>
Reviewed-by: Liang Liu <liuliang39@huawei.com>
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
driver inclusion
category: feature
bugzilla: NA
CVE: NA
Added PLL and mode list support corresponding to some resolutions.
The increased resolution is 640x480,1440x900,1600x900, enabling
shadowfb acceleration.
Signed-off-by: GongJunjie <gongjunjie2@huawei.com>
Reviewed-by: Xin Yin <yinxin.yinxin@huawei.com>
Reviewed-by: Mu Zhang <zhangmu1@huawei.com>
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
For some reason, TK4 Makefile fails for userspace tools when there are
too many workers. Just limit it to one, user space tools are fast to
compile anyway.
Signed-off-by: Kairui Song <kasong@tencent.com>
Upstream: no
Fixes: "canonicalization unexpectedly shrank by one character" error on
older RHEL based distro. debugedit util doesn't recognize double '//' in
kernel tracepoints.
Signed-off-by: Kairui Song <kasong@tencent.com>
Upstream: no
It's kernel-core's dependency. And for older RHEL based distro, just
depend on systemd instead.
Signed-off-by: Kairui Song <kasong@tencent.com>
Just dump latest dist files from OCKS, with following change:
- Use symlinks for the config file and kabi files under dist/configs
and dist/kabi, point to the ones under package/, keep compatibility.
- Update VENDOR_CAPITALIZED, VENDOR, URL, and KDIST in dist/Makefile
- Clean up changelog.
Signed-off-by: Kairui Song <kasong@tencent.com>
Enable commonly used DRM/FB drivers for VMs. We may need to enable more
DRM drivers later but for now, just enabled these VM drivers.
Also update changelog. Latest OC public iso is already using OC 5.4
kernel as default kernel.
Signed-off-by: Kairui Song <kasong@tencent.com>
The member of member_offset structure should be char pointer and
not an array, otherwise it could result in
memlat_member_offset[i].member always be true when we iterate the
array. The ARM-GCC can find it and report the error.
Signed-off-by: Bin Lai <robinlai@tencent.com>
Reviewed-by: Munger Jiang <mungerjiang@tencent.com>
ACPICA commit c11af67d8f7e3d381068ce7771322f2b5324d687
If original_count is 0 in acpi_ut_update_ref_count (),
acpi_ut_delete_internal_obj () is invoked for the target object, which is
incorrect, because that object has been deleted once already and the
memory allocated to store it may have been reclaimed and allocated
for a different purpose by the host OS. Moreover, a confusing debug
message following the "Reference Count is already zero, cannot
decrement" warning is printed in that case.
To fix this issue, make acpi_ut_update_ref_count () return after finding
that original_count is 0 and printing the above warning.
Link: https://github.com/acpica/acpica/commit/c11af67d
Link: https://github.com/acpica/acpica/pull/652
Reported-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Bob Moore <robert.moore@intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: caelli <caelli@tencent.com>
libperf-jvmti.so doesn't build in tmanager.
Add a dummy libperf-jvmti.so in perf to compat two system.
Signed-off-by: Haisu Wang <haisuwang@tencent.com>
Remove the duplicate files from kernel-tools/bpftools but
included by perf.
Keep the python2, python-perf name and libraries location
for backward compatibility.
Signed-off-by: Haisu Wang <haisuwang@tencent.com>
Enable selinux by add 'selinux' to CONFIG_LSM for arm64. Meanwhile,
enable CONFIG_SECURITY_SELINUX for x86.
Signed-off-by: Menglong Dong <imagedong@tencent.com>
commit d5f9023fa61ee8b94f37a93f08e94b136cf1e463 upstream.
can_rx_register() callbacks may be called concurrently to the call to
can_rx_unregister(). The callbacks and callback data, though, are
protected by RCU and the struct sock reference count.
So the callback data is really attached to the life of sk, meaning
that it should be released on sk_destruct. However, bcm_remove_op()
calls tasklet_kill(), and RCU callbacks may be called under RCU
softirq, so that cannot be used on kernels before the introduction of
HRTIMER_MODE_SOFT.
However, bcm_rx_handler() is called under RCU protection, so after
calling can_rx_unregister(), we may call synchronize_rcu() in order to
wait for any RCU read-side critical sections to finish. That is,
bcm_rx_handler() won't be called anymore for those ops. So, we only
free them, after we do that synchronize_rcu().
Fixes: ffd980f976e7 ("[CAN]: Add broadcast manager (bcm) protocol")
Link: https://lore.kernel.org/r/20210619161813.2098382-1-cascardo@canonical.com
Cc: linux-stable <stable@vger.kernel.org>
Reported-by: syzbot+0f7e7e5e2f4f40fa89c0@syzkaller.appspotmail.com
Reported-by: Norbert Slusarek <nslusarek@gmx.net>
Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Httpchaos need both CONFIG_NETFILTER_XT_MATCH_SOCKET and
CONFIG_NETFILTER_XT_TARGET_TPROXY, these config were aleady opened in x86, but
not on arm64, so just open it.
Kernel-5.4 prohibit user to modify the sched_domain flags bit, but
we have to do it to optimize performance in some cases. So we remove
the prohibition of sched_domain flags moditication allow user do the
better tunning.
Signed-off-by: Bin Lai <robinlai@tencent.com>
Reviewed-by: Bauerchen <bauerchen@tencent.com>