linux-kernel - remove_proc_entry and read

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: <200701311154.35929.duncan.sands@math.u-psud.fr>
Date:	Wed, 31 Jan 2007 11:54:35 +0100
From:	Duncan Sands <duncan.sands@...h.u-psud.fr>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: remove_proc_entry and read_proc

Can read_proc still be executing when remove_proc_entry returns?

In my driver [*] I allocate some data and create a proc entry using
create_proc_entry.  My read method reads from my allocated data.  When
shutting down, I call remove_proc_entry and immediately free the data.
If some call to read_proc is still executing at this point then it will
be accessing freed memory.  Can this happen?  I've been rummaging around
in fs/proc to see what prevents it, but didn't find anything yet.

Thanks a lot,

Duncan.

[*] Actually it's the ATM layer that does all this (net/atm); my driver
uses that layer.
-
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/