Date: Tue, 29 May 2018 22:24:05 +0800 From: Julian Elischer <julian@freebsd.org> To: Andriy Gapon <avg@FreeBSD.org>, Hans Petter Selasky <hps@selasky.org>, FreeBSD Current <freebsd-current@FreeBSD.org> Subject: Re: head@r334204, Bad link elm in callout_process() Message-ID: <f1004a49-b6b5-ec68-e784-c87c04e22acf@freebsd.org> In-Reply-To: <0df613ac-70aa-f793-1b7b-7a5e097fef28@FreeBSD.org> References: <d52aa0a9-7fbe-da6e-aa36-f34171e33843@FreeBSD.org> <84341ca3-90a5-97ef-8eee-dc1bbb07503c@selasky.org> <0df613ac-70aa-f793-1b7b-7a5e097fef28@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29/5/18 9:53 pm, Andriy Gapon wrote:
> On 29/05/2018 14:53, Hans Petter Selasky wrote:
>> On 05/29/18 13:20, Andriy Gapon wrote:
>>> (kgdb) p *$4.lh_first->c_links.le.le_next
>>> $6 = {
>>> c_links = {
>>> le = {
>>> le_next = 0x0,
>>> le_prev = 0xfffffe0003999f98
>> Where does the le_prev point?
>>
>> Typically happens when callouts are not properly drained before freeing memory.
> Yeah, this could have been a pilot error.
> I added some debugging code and that code could do callout_init + callout_reset
> on an active or pending callout. I am not seeing the problem without the
> debugging code.
> Sorry for the noise!
did you add code to that machine?? (bob.$work)
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f1004a49-b6b5-ec68-e784-c87c04e22acf>