On 7/2/2024 3:10 PM, Dmitry Baryshkov wrote: > On Tue, 2 Jul 2024 at 10:07, Ekansh Gupta <quic_ekangupt@xxxxxxxxxxx> wrote: >> >> >> On 7/1/2024 10:41 PM, Dmitry Baryshkov wrote: >>> On Mon, Jul 01, 2024 at 10:50:38AM GMT, Ekansh Gupta wrote: >>>> On 6/28/2024 7:51 PM, Greg KH wrote: >>>>> On Fri, Jun 28, 2024 at 04:12:10PM +0530, Ekansh Gupta wrote: >>>>>> On 6/28/2024 3:59 PM, Ekansh Gupta wrote: >>>>>>> On 6/27/2024 4:43 PM, Dmitry Baryshkov wrote: >>>>>>>> On Thu, Jun 27, 2024 at 11:35:18AM GMT, Ekansh Gupta wrote: >>>>>>>>> For user PD initialization, initmem is allocated and sent to DSP for >>>>>>>>> initial memory requirements like shell loading. This size is passed >>>>>>>>> by user space and is checked against a max size. For unsigned PD >>>>>>>>> offloading, more than 2MB size could be passed by user which would >>>>>>>>> result in PD initialization failure. Remove the user PD initmem size >>>>>>>>> check and allow buffer allocation for user passed size. Any additional >>>>>>>>> memory sent to DSP during PD init is used as the PD heap. >>>>>>>> Would it allow malicious userspace to allocate big enough buffers and >>>>>>>> reduce the amount of memory available to the system? To other DSP >>>>>>>> programs? >>>>>>> The allocation here is happening from SMMU context bank which is uniquely assigned >>>>>>> to processes going to DSP. As per my understanding process can allocate maximum >>>>>>> 4GB of memory from the context bank and the memory availability will be taken care >>>>>>> by kernel memory management. Please correct me if my understanding is incorrect. >>>>>> Just wanted to add 1 question here: >>>>>> User space can also directly allocate memory. Wouldn't that be a problem if any malicious userspace >>>>>> allocated huge memory? >>>>> No, because any userspace program that takes up too much memory will be >>>>> killed by the kernel. >>>>> >>>>> You can not have userspace tell the kernel to allocate 100Gb of memory, >>>>> as then the kernel is the one that just took it all up, and then >>>>> userspace applications will start to be killed off. >>>>> >>>>> You MUST bounds check your userspace-supplied memory requests. Remember >>>>> the 4 words of kernel development: >>>>> >>>>> All input is evil. >>>> Thanks for the detailed explanation, Greg. I'll remember this going forward. >>>> >>>> For this change, I'll increase the max size limit to 5MB which is the requirement for >>>> unsigned PD to run on DSP. >>> So we are back to the quesiton of why 5MB is considered to be enough, >>> see >>> >>> https://lore.kernel.org/linux-arm-msm/2024061755-snare-french-de38@gregkh/ >> This is based on the initial memory requirement for unsigned PD. This includes memory for shell loading on DSP >> + memory for static heap allocations(heap allocations are dynamic for Signed PD). This requirement tends to >> around 5MB. I'll update this also information in commit text. There will be some additional memory passed to >> the PD which will get added to the PD heap. > Could you please clarify, are these 2MB and 5MB requirements coming > from the DSP side or from the userspace side? In other words, is it > coming from the shell / firmware / etc? I did some more checking here, I'll summarize the problem and try to propose a better solution: init.filelen is actually the size of fastrpc shell file which is close to 900kb for both signed and unsigned shells. User space passes this memory and size after opening and reading the shell file. The bound check is for this filelen which looks correct also as this size is not expected to be more than 2MB. Now for PD initmem, this memory is needed for PD initialization which includes loading of shell and other initialization requirements eg. PD heap. As of today, the initmem allocation is taken as the max of FASTRPC_FILELEN_MAX(2MB bound check macro) and 4 times of filelen(~4MB). So every time, atleast 2MB memory is allocated for this initmem for PD initialization. For unsigned PD, there are some additional read-write segments loaded on DSP which takes the size requirement to slightly more than 4MB. Therefore allocating 5MB is helping unsigned PD to be spawned. I hope this helps in understanding the problem. Proposed solution: I believe the bound check macro should not be used for initmem size. I can add some new definition with FASTRPC_INITMEM_MIN. In the create_process function, the "memlen" will be set to FASTRPC_INITMEM_MIN initially and it will get increased to 5MB if "unsigned_module" is requested. Or I can add different MACRO definitions for both signed(3MB) and unsigned PD(5MB) minimum initmem size. Please let me know if this is not clear, I'll send a patch for better understanding. --Ekansh >> --Ekansh >>>> --Ekansh >>>>> thanks, >>>>> >>>>> greg k-h >
