These commits reference Deadlock between v6.9 and v6.10-rc1
These commits are not, yet, in stable/linux-rolling-stable.
Let me know if you would rather me compare to a different repo/branch.
The list has been manually pruned to only contain commits that look like
actual issues.
If they contain a Fixes line it has been verified that at least one of the
commits that the Fixes tag(s) reference is in stable/linux-rolling-stable
56c35f43eef013579c76
eec7620800081e27dbf8
4268254a39484fc11ba9
0a46ef234756dca04623
ecf0b2b8a37c84641866
e03a5d3e95f22d15d8df
4d3421e04c5dc38baf15
9cc6290991e6cfc9a644
77e619a82fc384ae3d1d
e533e4c62e9993e62e94
21ad2d03641ae70a7acd
2afd5276d314d775ae0b
3bdb7f161697e2d5123b
6f31d6b643a32cc126cf
--
Ronnie Sahlberg [Principal Software Engineer, Linux]
P 775 384 8203 | E [email] | W ciq.com
Here is a list of potential Use after free that are not yet in
linux-running-stable
The list has been manually pruned and I believe they are all genuine issues.
546ceb1dfdac866648ec
36c92936e868601fa1f4
4e7aaa6b82d63e8ddcbf
2884dc7d08d98a89d8d6
166fcf86cd34e15c7f38
4b4391e77a6bf24cba2e
da4a827416066191aafe
de3e26f9e5b76fc62807
0fc75c5940fa634d84e6
647535760a00a854c185
a4edf675ba3357f60e2e
90e823498881fb8a91d8
2c6b531020f0590db3b6
7172dc93d621d5dc302d
86735b57c905e775f05d
795bb82d12a16a4cee42
2ecd487b670fcbb1ad48
--
Ronnie Sahlberg [Principal Software Engineer, Linux]
P 775 384 8203 | E [email] | W ciq.com
The following is a pruned list of commits from upstream v6.9..v6.10-rc3
that looks like genuine kernel panics.
As far as I can tell these are not yet in linux-rolling-stable
If there are issues with the list or things I cna improve when pruning the list
please let me know
a6736a0addd60fccc3a3
79f18a41dd056115d685
8eef5c3cea65f248c99c
12cda920212a49fa22d9
b01e1c030770ff3b4fe3
744d197162c2070a6045
3f0c44c8c21cfa3bb6b7
0105eaabb27f31d9b8d3
6434e69814b159608a23
d38e48563c1f70460503
c8b3f38d2dae03979448
33afbfcc105a57215975
491aee894a08bc9b8bb5
d0d1df8ba18abc57f28f
ffbe335b8d471f79b259
93c1800b3799f1737598
3c34fb0bd4a4237592c5
ffb9072bce200a4d0040
9dedabe95b49ec9b0d16
788e4c75f831d06fcfbb
642f89daa34567d02f31
f55cd31287e5f77f226c
6ca445d8af0ed5950ebf
ed281c6ab6eb8a914f06
e8dc41afca161b988e6d
c6a6c9694aadc4c3ab8d
eebadafc3b14d9426fa9
29b4c7bb8565118e2c7e
da0e01cc7079124cb1e8
b66c079aabdff3954e93
514ca22a25265e9bef10
05090ae82f44570fefdd
3b89ec41747a6b6b8c7b
57787fa42f9fc12fe189
1af2dface5d286dd1f2f
81bf14519a8ca17af4f0
991b5e2aad870828669c
17b0dfa1f35bf58c17ae
--
Ronnie Sahlberg [Principal Software Engineer, Linux]
P 775 384 8203 | E [email] | W ciq.com
Pruned list of commits that look like genuine deadlocks that are not
yet in linux-rolling-stable
44c06bbde6443de206b3
8c2f5dd0c362ec036f02
e57f2187ccc125f1f14f
67ec8cdf29971677b2fb
--
Ronnie Sahlberg [Principal Software Engineer, Linux]
P 775 384 8203 | E [email] | W ciq.com
Manually checked list of commits in upstream that mention NULL pointers and
that reference that they fix a commit that is in linux-running-stable.
a9b9741854a9fe9df948
c4ab9da85b9df3692f86
c44711b78608c98a3e6b
0dcc53abf58d572d34c5
445c0b69c72903528fdf
97ab3e8eec0ce79d9e26
47558cbaa842c4561d08
62cbabc6fd228e62daff
02367f52901932674ff2
--
Ronnie Sahlberg [Principal Software Engineer, Linux]
P 775 384 8203 | E [email] | W ciq.com