Skip to content
Snippets Groups Projects
  1. Jan 15, 2025
  2. Dec 20, 2024
    • Anand Kulkarni's avatar
      Resolving the buffer accessed out of bound issue · 7c4345e1
      Anand Kulkarni authored
      
      While packing shared buffer with names of all shared objects present
      in custom DSP_LIBRARY_PATH , their is a possibility of buffer overflow
      if the shared object names are exceeding the desired limit.The change
      makes sure the limit is not exceeded thus avoiding buffer overflow.
      Also, the buffer was allocated with 1KB memory which might fall short
      to accomodate all the needed shared object names so, increasing this
      size to 2KB.
      
      Signed-off-by: default avatarAnand Kulkarni <quic_anankulk@quicinc.com>
      v0.1.4
      7c4345e1
  3. Dec 19, 2024
  4. Nov 29, 2024
  5. Nov 22, 2024
  6. Nov 20, 2024
  7. Nov 15, 2024
  8. Nov 13, 2024
  9. Oct 23, 2024
  10. Oct 18, 2024
  11. Oct 15, 2024
    • ANANDU KRISHNAN E's avatar
      Handle dspqueue close error during SSR · 0a7b22ea
      ANANDU KRISHNAN E authored
      
      Once the SSR notification is received, clients are supposed to close
      all open handles, which closes the current session. After SSR is
      completed, clients can open a new session and continue. To close the
      dspqueue handle, dspqueue close call should complete successfully.
      However, the dspqueue close contains APIs which will make IOCTL
      calls that fail with the AEE_ECONNRESET error during SSR. These
      errors prevent dspqueue handle from closing successfully.
      Don’t call APIS wiht IOCTLs in dspqueue close if SSR is ongoing.
      Also Update dspsignal and dspqueue functions to return
      AEE_ECONNRESET in case of SSR
      
      Signed-off-by: default avatarANANDU KRISHNAN E <quic_anane@quicinc.com>
      0a7b22ea
  12. Oct 11, 2024
  13. Oct 10, 2024
  14. Oct 07, 2024
  15. Oct 04, 2024
  16. Sep 27, 2024
    • Abhinav Parihar's avatar
      Avoid fetching handle info using remote handle · 400492e8
      Abhinav Parihar authored
      
      Currently we are trying to fetch handle_info information
      from remote handles which doesn't point to the correct
      memory locations leading to segmentation faults.
      For non domain calls user communicates via remote handle
      instead of local handles. These user copy of remote handles
      cannot be used to get handle_info related information and
      will lead to faults.
      
      Signed-off-by: default avatarAbhinav Parihar <quic_parihar@quicinc.com>
      400492e8
    • Abhinav Parihar's avatar
      Maintain correct domain handle count · d67070b6
      Abhinav Parihar authored
      
      In scenarios where static domain handle support is not
      available, wrong handle info is being passed to
      fastrpc_update_module_list function. This leads to wrongful
      updation of domainsCount variable which is meant to keep
      count of dynamic domain handles. The corrupted domainsCount
      variable leads to premature exit of user process.
      
      Signed-off-by: default avatarAbhinav Parihar <quic_parihar@quicinc.com>
      d67070b6
  17. Aug 09, 2024
Loading