Skip to content

Conversation

@crafcat7
Copy link
Contributor

Summary

Fixed CI Break caused by #14632

==================================================================================== Configuration/Tool: spresense/example_camera,CONFIG_ARM_TOOLCHAIN_GNU_EABI 2024-11-12 12:24:37
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Building NuttX...
mount/fs_automount.c: In function 'automount_initialize': Error: mount/fs_automount.c:816:7: error: 'return' with no value, in function returning non-void [-Werror=return-type]
  816 |       return;
      |       ^~~~~~
In file included from mount/fs_automount.c:43:
/github/workspace/sources/nuttx/include/nuttx/fs/automount.h:176:11: note: declared here
  176 | FAR void *automount_initialize(FAR const struct automount_lower_s *lower);
      |           ^~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors

Impact

Is a new feature added?: NO
Impact on build: NO
Impact on hardware: NO, this change does not specifically target any particular hardware architectures or boards.
Impact on documentation: NO,This patch does not introduce any new features
Impact on compatibility: This implementation aims to be backward compatible. No existing functionality is expected to be broken.

Testing

Build Host(s): Linux x86
Target(s): spresense/example_camera

Create version.h
CPP:  nxfonts_convert.c-> nxfonts_convert_32bpp.i LN: platform/board to /home/crafcat7/SSD/vela/apps/platform/dummy
Register: camera
Register: nsh
Register: sh
Register: msconn
Register: msdis
CPP:  /home/crafcat7/SSD/vela/nuttx/boards/arm/cxd56xx/spresense/scripts/ramconfig-new.ld-> /home/crafcat7/SSD/vela/nuttx/boards/arm/cxd56xx/spresense/scriptsLD: nuttx
Memory region         Used Size  Region Size  %age Used
             ram:      220228 B      1536 KB     14.00%
         gnssram:          0 GB       640 KB      0.00%
Generating: nuttx.spk
tools/cxd56/mkspk -c2 nuttx nuttx nuttx.spk;
File nuttx.spk is successfully created.
Done.

@github-actions github-actions bot added Area: File System File System issues Size: XS The size of the change in this PR is very small labels Nov 13, 2024
@crafcat7 crafcat7 force-pushed the fix_automount_initialize branch 2 times, most recently from f05a115 to 79c961b Compare November 13, 2024 02:36
====================================================================================
Configuration/Tool: spresense/example_camera,CONFIG_ARM_TOOLCHAIN_GNU_EABI
2024-11-12 12:24:37
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Building NuttX...
mount/fs_automount.c: In function 'automount_initialize':
Error: mount/fs_automount.c:816:7: error: 'return' with no value, in function returning non-void [-Werror=return-type]
  816 |       return;
      |       ^~~~~~
In file included from mount/fs_automount.c:43:
/github/workspace/sources/nuttx/include/nuttx/fs/automount.h:176:11: note: declared here
  176 | FAR void *automount_initialize(FAR const struct automount_lower_s *lower);
      |           ^~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors

Signed-off-by: chenrun1 <chenrun1@xiaomi.com>
@crafcat7 crafcat7 force-pushed the fix_automount_initialize branch from 79c961b to b8dc53b Compare November 13, 2024 02:41
@anchao
Copy link
Contributor

anchao commented Nov 13, 2024

@crafcat7 another question:

_assert
|
 ->dump_fatal_info
   |
    ->dump_tasks
      |
       ->dump_filelist
         |
          ->files_dumplist
            |
             ->lib_get_pathbuffer
               |
                ->nxmutex_lock      <-- hold mutex on assert will trigger an nested exception

@crafcat7
Copy link
Contributor Author

@crafcat7 another question:

_assert
|
 ->dump_fatal_info
   |
    ->dump_tasks
      |
       ->dump_filelist
         |
          ->files_dumplist
            |
             ->lib_get_pathbuffer
               |
                ->nxmutex_lock      <-- hold mutex on assert will trigger an nested exception

Can we solve this problem by changing to spinlock instead of mutex?

@xiaoxiang781216
Copy link
Contributor

Yes, let's change to spinlock

@xiaoxiang781216 xiaoxiang781216 merged commit 8068ba7 into apache:master Nov 13, 2024
@crafcat7
Copy link
Contributor Author

@crafcat7 another question:

_assert
|
 ->dump_fatal_info
   |
    ->dump_tasks
      |
       ->dump_filelist
         |
          ->files_dumplist
            |
             ->lib_get_pathbuffer
               |
                ->nxmutex_lock      <-- hold mutex on assert will trigger an nested exception

Can we solve this problem by changing to spinlock instead of mutex?

I submitted a fix for this issue at #14799

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: File System File System issues Size: XS The size of the change in this PR is very small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants