linux-kernel - [RFC PATCH 0/3] Fix module information when symbol

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

Message-Id: <1173501083.26213.403.camel@localhost>
Date:	Sat, 10 Mar 2007 02:31:22 -0200
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	rusty@...tcorp.com.au
Cc:	Trent Piepho <xyzzy@...akeasy.org>,
	Rechberger Markus <mrechberger@...il.com>,
	Linux DVB <linux-dvb@...uxtv.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: [RFC PATCH 0/3] Fix module information when symbol_get is used

Hi Rusty,

DVB code uses symbol_get/symbol_put functions at module.c to allow
dynamically add frontend modules (responsible for tuning and
demodulating the digital signal). The problem is that symbol_get doesn't
properly mark the module that requested it.

Trent worked on a fix for this, by using 3 patches. One on module.c,
another on mtd driver, and the last one on linux-dvb.

With the patch, lsmod produces output like this:
cx88_dvb               14084  0
or51132                 9988  1 cx88_dvb

Without it, this is what you get:
cx88_dvb               14084  0
or51132                 9988  1


 drivers/media/dvb/bt8xx/dst.c             |    5 -
 drivers/media/dvb/dvb-core/dvb_frontend.c |    9 +--
 drivers/mtd/chips/gen_probe.c             |    4 -
 include/linux/module.h                    |   13 ++--
 kernel/module.c                           |   87 ++++++++++++++++++++++--------
 5 files changed, 80 insertions(+), 38 deletions(-)

-
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/