On Tue, Aug 02, 2016 at 08:53:55AM +0200, Daniel Wagner wrote: > On 08/02/2016 08:34 AM, Luis R. Rodriguez wrote: > >On Tue, Aug 02, 2016 at 07:49:19AM +0200, Daniel Wagner wrote: > >>>The sysdata API's main goal rather is to provide a flexible API first, > >>>compartamentalizing the usermode helper was secondary. But now it seems > >>>I may just also add devm support too to help simplify code further. > >> > >>I missed the point that you plan to add usermode helper support to > >>the sysdata API. > > > >I had no such plans, when I have asked folks so far about "hey are you > >really in need for it, OK what for? " and "what extended uses do you > >envision?" so I far I have not gotten any replies at all. So -- instead > >sysdata currently ignores it. > > So you argue for the remoteproc use case with 100+ MB firmware that > if there is a way to load after pivot_root() (or other additional > firmware partition shows up) then there is no need at all for > usermode helper? No, I'm saying I'd like to hear valid uses cases for the usermode helper and so far I have only found using coccinelle grammar 2 explicit users, that's it. My patch series (not yet merge) then annotates these as valid as I've verified through their documentation they have some quirky requirement. Other than these two drivers I'd like hear to valid requirements for it. The existential issue is a real issue but it does not look impossible to resolve. It may be a solution to bloat up the kernel with 100+ MB size just to stuff built-in firmware to avoid this issue, but it does not mean a solution is not possible. Remind me -- why can remoteproc not stuff the firmware in initramfs ? Anyway, here's a simple suggestion: fs/exec.c gets a sentinel file monitor support per enum kernel_read_file_id. For instance we'd have one for READING_FIRMWARE, one for READING_KEXEC_IMAGE, perhaps READING_POLICY, and this would in turn be used as the system configurable deterministic file for which to wait for to be present before enabling each enum kernel_read_file_id type read. Thoughts ? Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
