Date: Fri, 31 Mar 2017 02:57:05 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Message-ID: <bug-148807-2472-hHfkotIymu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-148807-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-148807-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 --- Comment #43 from Kubilay Kocak <koobs@FreeBSD.org> --- @All For issues where the 'described problem' and the 'thing(s) that need t= o be changed' are not one and the same, to retain all history/contextual informa= tion and not cause confusion (renaming titles, etc), the correct process is as follows: 1) Leave the 'original description/report of symptoms' issues 'as is'. 2) Create a blocking (depends on) issue for each area/component within Free= BSD that requires a change/fix (em, igb, etc). Alternatively, if multiple areas require fixing/changes but these will be resolved by a single person or maintainer (the assignee), then a single blocking issue is fine. Notes: The assignee of the blocked (parent) issue (ie 'the original report') can be changed to the person(s) responsible (assignee) to the blocking (sub) issue= .=20 Alternatively, the assignee of the parent issue can also be a person who wa= nts to/will 'see it through', coordinating and updating issue metadata until all sub-tasks are closed, including any relevant MFC's and documentation tasks. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-148807-2472-hHfkotIymu>