[Bug 263445] [tcp] Fatal trap 12: page fault while in kernel mode // supervisor read data, page not present // 13.1-RC3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263445 --- Comment #20 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=231e0dd5d1fb7778b1cb285e5ebee5502d5ad253 commit 231e0dd5d1fb7778b1cb285e5ebee5502d5ad253 Author: Richard Scheffenegger AuthorDate: 2022-06-07 16:16:54 + Commit: Richard Scheffenegger CommitDate: 2022-06-07 16:18:42 + tcp: skip sackhole checks on NULL Inadvertedly introduced NULL pointer dereference during sackhole sanity check in D35387. Reviewed By:glebius PR: 263445 MFC after: 1 week Sponsored by: NetApp, Inc. Differential Revision: https://reviews.freebsd.org/D35423 sys/netinet/tcp_sack.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 264193] pf: scrub max-mss rule stops working (but still counts) after 13.1-RELEASE upgrade
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264193 --- Comment #10 from Kristof Provost --- (In reply to Gleb Smirnoff from comment #8) It must have changed something to change the behaviour. We've fixed a number of bugs in pf between 13.0 and 13.1, but I'm not sure which of this fixes is responsible. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 263445] [tcp] Fatal trap 12: page fault while in kernel mode // supervisor read data, page not present // 13.1-RC3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263445 --- Comment #19 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=91d6afe6e2a912fd5059fc11dbeffc85474897af commit 91d6afe6e2a912fd5059fc11dbeffc85474897af Author: Richard Scheffenegger AuthorDate: 2022-06-07 07:07:09 + Commit: Richard Scheffenegger CommitDate: 2022-06-07 07:38:16 + tcp: Sanity check of SACK holes on retransmissions Adding a few KASSERT() to validate sanity of sack holes, and bail out if sack hole is inconsistent to avoid panicing non-invariant builds. Reviewed By:hselasky, glebius PR: 263445 MFC after: 1 week Sponsored by: NetApp, Inc. Differential Revision: https://reviews.freebsd.org/D35387 sys/netinet/tcp_sack.c | 12 1 file changed, 12 insertions(+) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 263445] [tcp] Fatal trap 12: page fault while in kernel mode // supervisor read data, page not present // 13.1-RC3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263445 --- Comment #18 from Igor A. Valkov --- (In reply to Michael Tuexen from comment #16) Ok. Now rebuilding kernel without options KERN_TLS. In the previous configuration, uptime is: 10:11 up 7 days, 11 hrs, 2 users, load averages: 17,39 16,85 17,08 :-) crashes are very random. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 263445] [tcp] Fatal trap 12: page fault while in kernel mode // supervisor read data, page not present // 13.1-RC3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263445 Richard Scheffenegger changed: What|Removed |Added Status|New |In Progress --- Comment #17 from Richard Scheffenegger --- While we don't yet understand how the TCPCB ends up in the peculiar state it is in when the panic happens, there appearts to be a symptomatic treatment by ignoring invalid SACK scoreboard state which however is in the approximate correct sequence space (thus no fully random memory contents). See https://reviews.freebsd.org/D35387 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 264056] mlx4(4) Fix resource leak in mlx4_opreq_action()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264056 --- Comment #6 from commit-h...@freebsd.org --- A commit in branch stable/12 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=936bd793479e274155fa2c42e770d0e4e35943cc commit 936bd793479e274155fa2c42e770d0e4e35943cc Author: Hans Petter Selasky AuthorDate: 2022-05-19 08:10:48 + Commit: Hans Petter Selasky CommitDate: 2022-06-07 06:46:14 + mlx4: Fix a memory leak bug. In function mlx4_opreq_action(), pointer "mailbox" is not released, when mlx4_cmd_box() return and error, causing a memory leak bug. Fix this issue by going to "out" label, mlx4_free_cmd_mailbox() can free this pointer. Linux commit: febfd9d3c7f74063e8e630b15413ca91b567f963 PR: 264056 Sponsored by: NVIDIA Networking (cherry picked from commit 527762b2f776381569bd662ce236d2845234c0a7) sys/dev/mlx4/mlx4_core/mlx4_fw.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 264056] mlx4(4) Fix resource leak in mlx4_opreq_action()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264056 --- Comment #5 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=267e6442d049939cd9c8ab5e3b0134deace39e66 commit 267e6442d049939cd9c8ab5e3b0134deace39e66 Author: Hans Petter Selasky AuthorDate: 2022-05-19 08:10:48 + Commit: Hans Petter Selasky CommitDate: 2022-06-07 06:44:28 + mlx4: Fix a memory leak bug. In function mlx4_opreq_action(), pointer "mailbox" is not released, when mlx4_cmd_box() return and error, causing a memory leak bug. Fix this issue by going to "out" label, mlx4_free_cmd_mailbox() can free this pointer. Linux commit: febfd9d3c7f74063e8e630b15413ca91b567f963 PR: 264056 Sponsored by: NVIDIA Networking (cherry picked from commit 527762b2f776381569bd662ce236d2845234c0a7) sys/dev/mlx4/mlx4_core/mlx4_fw.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- You are receiving this mail because: You are on the CC list for the bug.
