| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
This should fix our broken bisections.
Closes #6136.
|
| |
|
|
|
|
|
|
| |
The bug is easily triggerable during fuzzing / running reproducers and
it was present in torvalds for ~1.5 months.
Backport it when building these revisions in order to not derail the
bisections.
|
| |
|
|
|
| |
Otherwise we will not be able to bisect 3 months of Linux kernel
history.
|
| |
|
|
|
|
|
| |
The commit should fix the bisections for the period of 2-3 months.
See e.g. this failed bisection:
https://syzkaller.appspot.com/x/bisect.txt?x=124a9200580000
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The current common vcs interface and its implementations are designed to
support a very big number of situations (git modules, cleaning up
complex state, etc), which is too heavy and restrictive when we just
need a thin wrapper over the git command that supports a few basic
operations.
Refactor pkg/vcs to split out the wrapper code from the big git
implementation of the vcs.Repo interface.
Export the wrapper to enable reuse in other parts of the system.
|
| |
|
|
| |
It unblocks the bisection for the period of Jan 2021-Mar 2021.
|
| |
|
|
|
|
|
|
|
|
| |
The following error appears when bisecting older Linux versions:
check.c: In function 'validate_call':
check.c:2865:58: error: '%d' directive output may be truncated
writing between 1 and 10 bytes into a region of size 9
[-Werror=format-truncation=]
2865 | snprintf(pvname, sizeof(pvname), "pv_ops[%d]", idx);
|
| |
|
|
| |
Also, slightly refactor the code to facilitate testing.
|
| |
|
|
|
|
|
|
| |
These backports are also specified in syz-ci configs, which are stored
as plain JSON files.
Add a special dummy field that will be used for remembering the
rationale for the backport as well as useful links.
|
| |
|
|
|
|
|
|
| |
If the guilty commit is recent enough, it is possible that we'll be
testing a revision where the problem is not yet introduced.
Add a new field that holds the guilty revision and check for it every
time a patch is to be applied.
|
| |
|
|
|
|
|
|
|
|
|
| |
So far we don't really need it.
There's also a problem that we only find commits within a certain time
frame (5 years fro, now), so for old-introduced problems we cannot
reliably determine their presence.
It does not seem to be worth it to re-write the GetCommitsByTitles logic
now.
|
|
|
Factor out the code that cherry-picks missing fixes to a Linux repo.
Add two more commits that address issues with older kernel revisions.
|