linux-kernel - RE: [RFC 3/6] remoteproc: Move fw sanity check to find_rsc

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: <81C3A93C17462B4BBD7E272753C10579232F4FBCF7@EXDCVYMBSTM005.EQ1STM.local>
Date:	Mon, 4 Jun 2012 11:56:47 +0200
From:	Sjur BRENDELAND <sjur.brandeland@...ricsson.com>
To:	Ohad Ben-Cohen <ohad@...ery.com>
Cc:	Loic PALLARDY <loic.pallardy@...ricsson.com>,
	Ludovic BARRE <ludovic.barre@...ricsson.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Arnd Bergmann <arnd@...db.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	Sjur Brændeland <sjurbren@...il.com>
Subject: RE: [RFC 3/6] remoteproc: Move fw sanity check to find_rsc_table.

>> Prepare for pluggable firmware handling by calling firmware
>> sanity check from function find_rsc_table.
> 
> Can we keep the present location of rproc_fw_sanity_check(), and later
> just invoke the relevant ops handler instead?

The sanity_check() is working on the ELF structures. And all ELF
processing needs to be moved to a separate file. So if you want
to keep the call to sanity_check() here, I need to make the
sanity_check() function a separate handler. That could make sense,
but will also bloat the struct rproc_fw_ops with one more function
pointer.

Regards,
Sjur
--
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/