linux-kernel - Re: Linux 2.6.25-rc2

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <84144f020802190621s509dbe7gc8e5609d94aca9b4@mail.gmail.com>
Date:	Tue, 19 Feb 2008 16:21:51 +0200
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Mathieu Desnoyers" <mathieu.desnoyers@...ymtl.ca>
Cc:	"Torsten Kaiser" <just.for.lkml@...glemail.com>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Christoph Lameter" <clameter@....com>
Subject: Re: Linux 2.6.25-rc2

Hi Mathieu,

On Feb 19, 2008 4:02 PM, Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:
> - stat(c, ALLOC_FASTPATH); seems to be using a var++, therefore
>   indicating it is not reentrant if IRQs are disabled. Since those are
>   only stats, I guess it's ok, but still weird.

What is not re-entrant?

On Feb 19, 2008 4:02 PM, Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:
> Since this shows mostly with network card drivers, I think the most
> plausible cause would be an IRQ nesting over kmem_cache_alloc_node and
> calling it.

Yes, this can happen. Are you saying it is not safe to be in the
lockless path when an IRQ triggers?
--
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/