linux-kernel - Re: FW: Kernel: low stack detected by irq handler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABJk5knEkDvNkpN+Gq1+yPM5pQ0AnBFJR=QNWONZr=uVaSwd0g@mail.gmail.com>
Date:	Wed, 28 Mar 2012 15:41:12 +0530
From:	radiatejava <radiatejava@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: FW: Kernel: low stack detected by irq handler

I have an update to this case (note that this kernel module is
trapping every packet entering into the system and processing it as
needed) - recently some functions were added to in the processing path
of the packet to log the packet contents to a log file
(/var/log/messages). Logging functions were all written as 'inline'
functions. We just tried removing the inline keyword from the function
definitions and we are no longer observing the issue of kernel crash
and low stack by irq handler. Can anyone explain to me what is the
impact of having the function inline ? Appreciate your response. In
case the original issue is not visible here, I am putting the link
http://marc.info/?l=linux-kernel&m=131805703608420&w=2

Thanks in advance.

>> Hello experts,
>> I have recently moved from kernel 2.6.18-128 to 2.6.18-194. I have my
>> own kernel module also (click). With the new 2.6.18-194 version of
>> kernel, I am getting this error:
>>
>> Kernel: low stack detected by irq handler
>
> You are using too much stack basically and the kernel is catching this.
> The call trace should let you work out which path through your code is
> the problem.
>
> You've got an IRQ in the middle so it may well be its the combination of
> too much stack being used by the main code paths and an IRQ at just the
> wrong moment causing further high stack usage in the IRQ path that tips
> it over the edge.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/