| Age | Commit message (Collapse) | Author | Files |
|---|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
These were adding definitions for the second time
(see bug #10450 for why) or adding an include that isn't anymore
necessary for musl builds.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch was adding a change to the source file that was already there,
so the lines of code were repeated twice. This didn't create a bug or a
security issue, but it may well have.
Long story:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
showkey can also be provided by busybox
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
As of the 4.13 kernel, there are configuration + linker combinations
that do not need (or build) crtsavres.o for ppc64 targets. The commit
of interest is:
commit efe0160cfd40a99c052a00e174787c1f4158a9cd
Author: Nicholas Piggin <npiggin@gmail.com>
Date: Fri May 12 01:56:52 2017 +1000
powerpc/64: Linker on-demand sfpr functions for modules
For final link, the powerpc64 linker generates fpr save/restore
functions on-demand, placing them in the .sfpr section. Starting with
binutils 2.25, these can be provided for non-final links with
--save-restore-funcs. Use that where possible for module links.
This saves about 200 bytes per module (~60kB) on powernv defconfig
build.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
As such, our arch test for crtsavres.o is not enough, we add a secondary
existence check before trying the copy.
[YOCTO #12576]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The oe-core version of python3 patches the purelib use directory to
the system libdir so as to make it work with multilibs properly inside
the patch fix_for_using_different_libdir.patch with:
- 'purelib': '{base}/lib/python{py_version_short}/site-packages',
+ 'purelib': '{base}/'+sys.lib+'/python{py_version_short}/site-packages',
The problem is that this broke the pip3-python package because the
install directory is out of sync when using a multilib version of
python. When ever a module is installed with pip3 install that is a
purelib it will get installed to a location that python3 will never
reference and cause random failures.
This patch fixes the purelib install directory to match the purelib
use directory for externally managed python modules when using
multilibs.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
When running bitbake -c populate_sdk <image_name>, it is expected that
packages matching SDKIMAGE_INSTALL_COMPLEMENTARY name mask (unless
declared in PACKAGE_EXCLUDE_COMPLEMENTARY) are installed to resulting
SDK. Underlying mechanism issues a package manager install call for set
of complementary packages. However the mechanism doesn't seem to inform
the user all too obviously in case the package manager command behind
install_complementary() method fails -- and since it is combined with
attempt_only=True option, user might end up wondering why several *-dev,
*-dbg packages are missing from resulting SDK.
Improve associated install() method behaviour in affected OpkgPM and
DpkgPM classes so that a problematic state of affairs becomes directly
obvious for bitbake user, resulting in shell output like:
WARNING: someimage-1.0-r0 do_populate_sdk: Unable to install packages.
Command '...' returned 1:
Collected errors:
* Solver encountered 1 problem(s):
* Problem 1/1:
* - package somepkg-dev-1.0-r0.x86 requires somepkg = 1.0-r0, but
none of the providers can be installed
*
* Solution 1:
* - allow deinstallation of someotherpkg-1.1-r1.x86
* - do not ask to install a package providing somepkg-dev
* Solution 2:
* - do not ask to install a package providing somepkg-dev
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
Integrating the following warning backport:
commit eb371933cf4d3495d0899880b2e0e252ce9db517 upstream.
Coffee Lake CPU on Kaby Lake PCH is possible.
It does exist, and it does work.
The only missed case was this warning here noticed
by Wendy who could get one system with this configuration
and reported the issue for us:
Hardware Configuration
Board ID KBL S DDR4 UDIMM EV CRB
Processor Intel® Processor code named Coffee Lake S, (6+2), 6 cores 12 threads, GT2, A0 (Internal) (QNJ4)
[ 3.220585] WARNING: CPU: 10 PID: 206 at drivers/gpu/drm/i915/i915_drv.c:340 i915_driver_load+0x1210/0x1660 [i915]
[ 3.221312] Modules linked in: hid_generic usbhid i915 i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt nvme fb_sys_fops ptp ahci i2c_hid drm pps_core nvme_core libahci wmi hid video
[ 3.222050] CPU: 10 PID: 206 Comm: systemd-udevd Not tainted 4.13.0-rc5-intel-next+ #1
[ 3.222706] Hardware name: Intel Corporation Kabylake Client platform/KBL S DDR4 UDIMM EV CRB, BIOS KBLSE2R1.R00.X089.P00.1705051000 05/05/2017
Cc: Wendy Wang <wendy.wang@intel.com>
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20170821235056.9015-1-rodrigo.vivi@intel.com
Signed-off-by: Liwei Song <liwei.song@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
Integrating a configuration change for systemtap:
features/systemtap/systemtap.cfg: enable CONFIG_KERNEL_DEBUG
And porting the aufs warning fix to 4.14 and 4.15:
aufs: fix compile warning
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
Integrating the warning/leak fixes:
73873cb152c brd: remove unused brd_mutex
912c53b1b346 audit: fix memleak in auditd_send_unicast_skb.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
From: "Kexin(Casey) Chen" <Casey.Chen@windriver.com>
Forward port linux-yocto-4.8's patch to fix the build warning.
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-4.8/commit/?h=standard/base&id=7e0dd2f2b0971f0e3191e1ddc088e09eb9855567
fs/aufs/debug.h:95:19: warning: comparison of constant '0'
with boolean expression is always false [-Wbool-compare]
if (unlikely((e) < 0)) \
^
fs/aufs/vdir.c:852:2: note: in expansion of macro 'AuTraceErr'
AuTraceErr(!valid);
^~~~~~~~~~
In expansion of AuTraceErr(!valid), comparison of (!valid)
and constant '0' always passes unlikely(x) false. function
'static int seek_vdir(struct file *file, struct dir_context *ctx)'
is to find whether there is a valid vd_deblk following ctx->pos.
return 1 means valid, 0 for not. Change to AuTraceErr(valid - 1)
makes more sense.
Signed-off-by: Kexin(Casey) Chen <Casey.Chen@windriver.com>
Signed-off-by: Dengke Du <dengke.du@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
Updating the korg stable release which comprises the following commits:
6e4548ea58e6 Linux 4.14.24
ab5d9d1751bc net: sched: fix use-after-free in tcf_block_put_ext
ac2be03ba64f net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
1c8e7e61cbdf net: sched: crash on blocks with goto chain action
b6b42b3d2d95 net: sched: fix crash when deleting secondary chains
bc44a1bbd131 arm64: dts: marvell: mcbin: add comphy references to Ethernet ports
d8cf635c9142 arm64: dts: marvell: add comphy nodes on cp110 master and slave
27245fc6f7a8 powerpc/pseries: Enable RAS hotplug events later
60190108f7e2 MIPS: Implement __multi3 for GCC7 MIPS64r6 builds
819cbaae314e mlxsw: pci: Wait after reset before accessing HW
3d23aaff9e55 nfp: always unmask aux interrupts at init
e69660fdecda of_mdio: avoid MDIO bus removal when a PHY is missing
83d9e9c211fe net: gianfar_ptp: move set_fipers() to spinlock protecting area
00c840f3b51c sctp: make use of pre-calculated len
413e58ac3d84 sctp: add a ceiling to optlen in some sockopts
cd659881219d xen/gntdev: Fix partial gntdev_mmap() cleanup
5aee2c142e3d xen/gntdev: Fix off-by-one error when unmapping with holes
197faf0c3a14 SolutionEngine771x: fix Ether platform data
f5ac846ba15f mdio-sun4i: Fix a memory leak
84ada11975b7 xen-netfront: enable device after manual module load
0e29d0bac356 bnxt_en: Fix the 'Invalid VF' id check in bnxt_vf_ndo_prep routine.
a74e2cb46cdb bnxt_en: Fix population of flow_type in bnxt_hwrm_cfa_flow_alloc()
4a33ecfb67b9 x86/platform/intel-mid: Revert "Make 'bt_sfi_data' const"
fa10314f23bc nvme-fabrics: initialize default host->id in nvmf_host_default()
5e1311a13449 powerpc/pseries: Make RAS IRQ explicitly dependent on DLPAR WQ
9024bb7e27d2 leds: core: Fix regression caused by commit 2b83ff96f51d
be2b86901a34 bpf: sockmap missing NULL psock check
5ac98131312a ia64, sched/cputime: Fix build error if CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y
7e3acce11e08 block: drain queue before waiting for q_usage_counter becoming zero
91c12917d4a8 wcn36xx: Fix dynamic power saving
3f39cc7fe90b can: flex_can: Correct the checking for frame length in flexcan_start_xmit()
0f258cc64f4e mac80211: mesh: drop frames appearing to be from us
c38bd3a9fe11 nl80211: Check for the required netlink attribute presence
d66a35c2a1fa net: ena: unmask MSI-X only after device initialization is completed
aae87222cc9c i40e: don't remove netdev->dev_addr when syncing uc list
0f51f3cf99df i40e/i40evf: Account for frags split over multiple descriptors in check linearize
1edfa41adb10 uapi libc compat: add fallback for unsupported libcs
5c9da1201713 x86/efi: Fix kernel param add_efi_memmap regression
935454915c33 RDMA/netlink: Fix locking around __ib_get_device_by_index
7cbd67344e05 drm/ttm: check the return value of kzalloc
d31d0cf5a980 NET: usb: qmi_wwan: add support for YUGA CLM920-NC5 PID 0x9625
49a8f703725e e1000: fix disabling already-disabled warning
f22fec25935d macvlan: Fix one possible double free
4d3d428c56a0 xfs: quota: check result of register_shrinker()
4def40b2ee02 xfs: quota: fix missed destroy of qi_tree_lock
ba28394c579b IB/ipoib: Fix race condition in neigh creation
67851c9381a1 IB/mlx4: Fix mlx4_ib_alloc_mr error flow
9d27ab346384 Input: xen-kbdfront - do not advertise multi-touch pressure support
4132ec352700 ip6_tunnel: allow ip6gre dev mtu to be set below 1280
d4727e485a1d btrfs: Fix flush bio leak
4c6652a08139 s390/dasd: fix wrongly assigned configuration data
622ded58410c afs: Fix missing error handling in afs_write_end()
4ebaea9e65d2 genirq: Guard handle_bad_irq log messages
1fd2d40b4667 IB/mlx5: Fix mlx5_ib_alloc_mr error flow
c2acc8859138 led: core: Fix brightness setting when setting delay_off=0
6b800ce9ee84 perf/x86/intel: Plug memory leak in intel_pmu_init()
2f4c6c045305 bnx2x: Improve reliability in case of nested PCI errors
9f00176d7c5e tg3: Enable PHY reset in MTU change path for 5720
2c0d89a27335 tg3: Add workaround to restrict 5762 MRRS to 2048
575650b6566b tipc: fix tipc_mon_delete() oops in tipc_enable_bearer() error path
831923622a59 tipc: error path leak fixes in tipc_enable_bearer()
cbc3dbfe4f37 netfilter: nf_tables: fix potential NULL-ptr deref in nf_tables_dump_obj_done()
cdbde4c04c5c crypto: inside-secure - fix request allocations in invalidation path
7cc6e8415d23 crypto: inside-secure - free requests even if their handling failed
0971f188da94 crypto: inside-secure - per request invalidation
0653ba0580ae arm64: dts: renesas: ulcb: Remove renesas, no-ether-link property
22d5e20c6a55 lib/mpi: Fix umul_ppmm() for MIPS64r6
36d0a678fb25 crypto: af_alg - Fix race around ctx->rcvused by making it atomic_t
99b329b4611a ARM: dts: ls1021a: fix incorrect clock references
8164587e5262 RDMA/vmw_pvrdma: Call ib_umem_release on destroy QP path
831c169c9bac i915: Reject CCS modifiers for pipe C on Geminilake
8a5c84b1055a netfilter: uapi: correct UNTRACKED conntrack state bit number
b7b0385937fa scsi: storvsc: Fix scsi_cmd error assignments in storvsc_handle_error
e2f52fa3f8d6 netfilter: nf_tables: fix chain filter in nf_tables_dump_rules()
def8d0ae4ac9 xen/balloon: Mark unallocated host memory as UNUSABLE
caca324f9373 ASoC: rsnd: fixup ADG register mask
43da2bcade2a net/mlx5: Stay in polling mode when command EQ destroy fails
a2cfb1c664c3 net/mlx5: Cleanup IRQs in case of unload failure
9a472c211291 net/mlx5e: Fix ETS BW check
11be1c24a60d net: stmmac: Fix bad RX timestamp extraction
06dcd2d77a01 net: stmmac: Fix TX timestamp calculation
3eeac1d10a1b ip6_tunnel: get the min mtu properly in ip6_tnl_xmit
5dc4cbcfb5f2 ip6_gre: remove the incorrect mtu limit for ipgre tap
212ea3380bbb ip_gre: remove the incorrect mtu limit for ipgre tap
4699beb77127 vxlan: update skb dst pmtu on tx path
26e6b9f0be83 net: arc_emac: fix arc_emac_rx() error paths
9b72f8c448ec net: mediatek: setup proper state for disabled GMAC on the default
c7f40ff40061 x86-64/Xen: eliminate W+X mappings
54c153a0847b staging: ion: Fix ion_cma_heap allocations
d61a373f4344 cgroup: Fix deadlock in cpu hotplug path
56d80186a5ac ASoC: nau8825: fix issue that pop noise when start capture
3cf652bedcb9 spi: atmel: fixed spin_lock usage inside atmel_spi_remove
52a63f35cd70 mac80211_hwsim: Fix a possible sleep-in-atomic bug in hwsim_get_radio_nl
647ed111f78f x86/stacktrace: Make zombie stack traces reliable
e095ecaec6d9 xfrm: Reinject transport-mode packets through tasklet
e677319068b0 drm/nouveau/pci: do a msi rearm on init
0b9aeeb6070e net: phy: xgene: disable clk on error paths
ac4dc9f1af33 sget(): handle failures of register_shrinker()
60f1c1f27992 sctp: fix the issue that a __u16 variable may overflow in sctp_ulpq_renege
c8b8dd735938 x86/asm: Allow again using asm.h when building for the 'bpf' clang target
ba9443c55f36 ARM: 8731/1: Fix csum_partial_copy_from_user() stack mismatch
ae3471f65a04 parisc: Reduce thread stack to 16 kb
4b2e0f099619 ipv6: icmp6: Allow icmp messages to be looped back
6de1b002a29f mtd: nand: brcmnand: Zero bitflip is not an error
f485259011ad mtd: nand: gpmi: Fix failure when a erased page has a bitflip at BBM
14862bfbffd9 net: usb: qmi_wwan: add Telit ME910 PID 0x1101 support
043309fb5106 net: aquantia: Fix hardware DMA stream overload on large MRRS
dabd233b757d net: aquantia: Fix actual speed capabilities reporting
fbd047ffcccf nvme: check hw sectors before setting chunk sectors
a1aef5ce2abe nvme-fc: remove double put reference if admin connect fails
4d9f62729178 phy: cpcap-usb: Fix platform_get_irq_byname's error checking.
959f6a0906d5 dmaengine: fsl-edma: disable clks on all error paths
7cfa95893cbb scsi: aacraid: Fix I/O drop during reset
647a37ec1a17 mm/frame_vector.c: release a semaphore in 'get_vaddr_frames()'
7edaa9afb923 exec: avoid gcc-8 warning for get_task_comm
f92679fee6ad hrtimer: Ensure POSIX compliance (relative CLOCK_REALTIME hrtimers)
267ef1d33284 Linux 4.14.23
ac3d021048be microblaze: fix endian handling
9ce9f4e4a543 m32r: fix endianness constraints
821e97898016 drm/i915/breadcrumbs: Ignore unsubmitted signalers
1f0ffdc67108 drm/amdgpu: add new device to use atpx quirk
4517799bf655 drm/amdgpu: Avoid leaking PM domain on driver unbind (v2)
14fdf4448277 drm/amdgpu: add atpx quirk handling (v2)
30537deb089c drm/amdgpu: only check mmBIF_IOV_FUNC_IDENTIFIER on tonga/fiji
46c1e4023b58 drm/amdgpu: Add dpm quirk for Jet PRO (v2)
68de83c13b30 drm/amdgpu: disable MMHUB power gating on raven
8ac8aa5eba0e drm: Handle unexpected holes in color-eviction
5c9beaf3aca7 drm/cirrus: Load lut in crtc_commit
faf1a75046cb usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path
51aba4e16ccc usb: gadget: f_fs: Use config_ep_by_speed()
6e936140e0d7 usb: gadget: f_fs: Process all descriptors during bind
7551ff0ab230 Revert "usb: musb: host: don't start next rx urb if current one failed"
7e402ea2cdc2 usb: ldusb: add PIDs for new CASSY devices supported by this driver
a1e8aa2176d2 usb: dwc3: ep0: Reset TRB counter for ep0 IN
49e18b2ba887 usb: dwc3: gadget: Set maxpacket size for ep0 IN
1075f6078692 usb: host: ehci: use correct device pointer for dma ops
3b5061ec6fca drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA
f74ddc2e6152 Add delay-init quirk for Corsair K70 RGB keyboards
21aadb063e70 arm64: cpufeature: Fix CTR_EL0 field definitions
6842a512ad16 arm64: Disable unhandled signal log messages by default
96e99291728f arm64: Remove unimplemented syscall log message
7e8407d1462d usb: ohci: Proper handling of ed_rm_list to handle race condition between usb_kill_urb() and finish_unlinks()
85c3d26bd754 ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and io_watchdog_func()
50f80b646a2b PCI/cxgb4: Extend T3 PCI quirk to T4+ devices
4a665d628f93 irqchip/mips-gic: Avoid spuriously handling masked interrupts
bc4704f507cd irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()
62160e348e89 mm, swap, frontswap: fix THP swap if frontswap enabled
7a14562d6e2c x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()
0b82d316fa5b Kbuild: always define endianess in kconfig.h
6315213f0a78 iio: adis_lib: Initialize trigger before requesting interrupt
9dc4030c87b7 iio: buffer: check if a buffer has been set up when poll is called
1b985a6e8d4d iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined
f4f94e9baeba iio: adc: stm32: fix stm32h7_adc_enable error handling
2492eca0a05b RDMA/uverbs: Sanitize user entered port numbers prior to access it
84205f964bcc RDMA/uverbs: Fix circular locking dependency
aaa1915e3d2c RDMA/uverbs: Fix bad unlock balance in ib_uverbs_close_xrcd
f3d66d43500c RDMA/uverbs: Protect from command mask overflow
da768ed845a5 RDMA/uverbs: Protect from races between |
