Skip to contentSkip to conversation

docs/misra: add documentation to address MISRA C:2012 Dir 4.1

RFC PATCH In review Nicola Vetrini 4 participants 9 messages Aug 21, 2023 – Aug 22, 2023 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

cover docs/misra: add documentation to address MISRA C:2012 Dir 4.1

The headline of Directive 4.1 states: "Run-time failures shall be minimized". Thus, it requires the project to supply documentation that pertains the measures and techinques used to prevent run-time failures from happening. For ease of reading, the documentation is in RST format, but since ECLAIR needs a source file to check that the needed subsections and their format is the one expected, the Makefiles for the docs/ are amended to generate such a file.

Moreover, the format and categories of the subsections in the .rst file can be customized based on feedback from the community: the one provided is just a basic skeleton that should be tailored to the project.

Nicola Vetrini (3):
docs/misra: add documentation for MISRA C:2012 Dir 4.1
docs: make the docs for MISRA C:2012 Dir 4.1 visible to ECLAIR automation/eclair: build docs/misra to address MISRA C:2012 Dir 4.1

 automation/eclair_analysis/build.sh   |  10 +-
 automation/eclair_analysis/prepare.sh |   1 +
 docs/Makefile                         |   7 +-
 docs/misra/C-runtime-failures.rst     | 239 ++++++++++++++++++++++++++
 docs/misra/Makefile                   |  36 ++++
 docs/misra/rules.rst                  |   7 +-
 6 files changed, 296 insertions(+), 4 deletions(-)
 create mode 100644 docs/misra/C-runtime-failures.rst
 create mode 100644 docs/misra/Makefile

--
2.34.1

#1 lore raw

RFC PATCH 1/3 docs/misra: add documentation for MISRA C:2012 Dir 4.1

The aforementioned directive requires the project to supply documentation on the measures taken towards the minimization of run-time failures.

The 'rules.rst' file is updated accordingly to mention the newly added documentation.

---
 docs/misra/C-runtime-failures.rst | 239 ++++++++++++++++++++++++++++++
 docs/misra/rules.rst              |   7 +-
 2 files changed, 245 insertions(+), 1 deletion(-)
 create mode 100644 docs/misra/C-runtime-failures.rst
docs/misra/C-runtime-failures.rst new file +239 -0
new file mode 100644
index 000000000000..f72385b08417
@@ -0,0 +1,239 @@
+===================================================================
+Measures taken towards the minimization of Run-time failures in Xen
+===================================================================
+
+This document specifies which procedures and techinques are used troughout the
+Xen codebase to prevent or minimize the impact of certain classes of run-time
+errors that can occurr in the execution of a C program, due to the very minimal
+built-in checks that are present in the language.
+
+The presence of such documentation is requested by MISRA C:2012 Directive 4.1,
+whose headline states: "Run-time failures shall be minimized".
+
+
+Documentation for MISRA C:2012 Dir 4.1: overflow
+________________________________________________
+
+To be written.
+Example: Pervasive use of assertions and extensive test suite.
+
+
+Documentation for MISRA C:2012 Dir 4.1: unexpected wrapping
+___________________________________________________________
+
+To be written.
+Example: The only wrapping the is present in the code concerns
+unsigned integers and they are all expected.
+
+
+Documentation for MISRA C:2012 Dir 4.1: invalid shift
+_____________________________________________________
+
+To be written.
+Example: Pervasive use of assertions and extensive test suite.
+
+
+Documentation for MISRA C:2012 Dir 4.1: division/remainder by zero
+__________________________________________________________________
+
+To be written.
+Example:
+There division or remainder operations in the project code ensure that
+their second argument is never zero.
+
+
+Documentation for MISRA C:2012 Dir 4.1: unsequenced side effects
+________________________________________________________________
+
+To be written.
+Example:
+No function in this project is meant to be executed from interrupt handlers
+or in multi-threading environments.
+
+
+Documentation for MISRA C:2012 Dir 4.1: read from uninitialized automatic object
+________________________________________________________________________________
+
+To be written.
+Example:
+Automatic variables are used to store temporary parameters and they
+are always initialized to either a default value or a proper value
+before usage.
+
+
+Documentation for MISRA C:2012 Dir 4.1: read from uninitialized allocated object
+________________________________________________________________________________
+
+To be written.
+Example:
+The code does not use dynamically allocated storage.
+
+
+Documentation for MISRA C:2012 Dir 4.1: write to string literal or const object
+_______________________________________________________________________________
+
+To be written.
+Example:
+The toolchain puts every string literal and const object into a read-only
+section of memory.  The hardware exception raised when a write is attempted
+on such a memory section is correctly handled.
+
+
+Documentation for MISRA C:2012 Dir 4.1: non-volatile access to volatile object
+______________________________________________________________________________
+
+To be written.
+Example:
+Volatile access is limited to registers that are always accessed
+through macros or inline functions.
+
+
+Documentation for MISRA C:2012 Dir 4.1: access to dead allocated object
+_______________________________________________________________________
+
+To be written.
+Example:
+The code does not use dynamically allocated storage.
+
+
+Documentation for MISRA C:2012 Dir 4.1: access to dead automatic object
+_______________________________________________________________________
+
+To be written.
+Example:
+Pointers to automatic variables are never returned, nor stored in
+wider-scoped objects.  No function does the same on any pointer
+received as a parameter.
+
+
+Documentation for MISRA C:2012 Dir 4.1: access to dead thread object
+____________________________________________________________________
+
+To be written.
+Example:
+The program does not use per-thread variables.
+
+
+Documentation for MISRA C:2012 Dir 4.1: access using null pointer
+_________________________________________________________________
+
+To be written.
+Example:
+All possibly null pointers are checked before access.
+
+
+Documentation for MISRA C:2012 Dir 4.1: access using invalid pointer
+____________________________________________________________________
+
+To be written.
+Example:
+Usage of pointers is limited.  Pointers passed as parameters are
+always checked for validity.
+
+
+Documentation for MISRA C:2012 Dir 4.1: access using out-of-bounds pointer
+__________________________________________________________________________
+
+To be written.
+Example:
+Pointers are never uses to access arrays: indices are always used
+instead.
+
+
+Documentation for MISRA C:2012 Dir 4.1: access using unaligned pointer
+______________________________________________________________________
+
+To be written.
+Example:
+Pointer conversion that may result in unaligned pointers are never used.
+
+
+Documentation for MISRA C:2012 Dir 4.1: mistyped access to object
+-----------------------------------------------------------------
+
+To be written.
+Example:
+Pointer conversions that may result in mistyped accesses to objects
+are never used.
+
+
+Documentation for MISRA C:2012 Dir 4.1: mistyped access to function
+___________________________________________________________________
+
+To be written.
+Example:
+The code never uses function pointers.
+
+
+Documentation for MISRA C:2012 Dir 4.1: invalid pointer arithmetic
+__________________________________________________________________
+
+To be written.
+Example:
+Pointer arithmetic is never used.
+
+
+Documentation for MISRA C:2012 Dir 4.1: invalid pointer comparison
+__________________________________________________________________
+
+To be written.
+Example:
+Arrays are always accessed using indices instead of pointers.  Pointers
+are only compared to NULL.
+
+
+Documentation for MISRA C:2012 Dir 4.1: overlapping copy
+________________________________________________________
+
+To be written.
+Example:
+The code never uses memcpy() and does not perform assignment of
+overlapping objects (which is doable only via pointers).
+
+
+Documentation for MISRA C:2012 Dir 4.1: invalid arguments to function
+_____________________________________________________________________
+
+To be written.
+Example:
+All parameters to functions are checked for validity.
+
+
+Documentation for MISRA C:2012 Dir 4.1: returned function error
+_______________________________________________________________
+
+To be written.
+Example:
+All functions that may produce an error, do returns a suitable status code
+that is checked at each call site.
+
+
+Documentation for MISRA C:2012 Dir 4.1: tainted input
+_____________________________________________________
+
+To be written.
+Example:
+All parameters of all functions in the API are checked before being used.
+
+
+Documentation for MISRA C:2012 Dir 4.1: data race
+_________________________________________________
+
+To be written.
+Example:
+No function in this code is meant to be executed from interrupt handlers or
+in a multi-threading environment.
+
+
+Documentation for MISRA C:2012 Dir 4.1: invariant violation
+___________________________________________________________
+
+To be written.
+
+
+Documentation for MISRA C:2012 Dir 4.1: communication error
+___________________________________________________________
+
+To be written.
+Example:
+This project does not involve any external communication.
docs/misra/rules.rst +6 -1
index 8f0e4d3f25f4..cebff854a95c 100644
@@ -47,7 +47,12 @@ maintainers if you want to suggest a change.
    * - `Dir 2.1 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/D_02_01.c>`_
      - Required
      - All source files shall compile without any compilation errors
-     -
+
+   * - `Dir 4.1 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/D_04_01.c>`_
+     - Required
+     - Run-time failures shall be minimized
+     - The strategies adopted by Xen to prevent certain classes of runtime
+       failures are documented by `C-runtime-failures.rst <docs/misra/C-runtime-failures.rst>`_
 
    * - `Dir 4.7 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/D_04_07.c>`_
      - Required
Signature · 1 line
2.34.1
#2 lore raw

RFC PATCH 2/3 docs: make the docs for MISRA C:2012 Dir 4.1 visible to ECLAIR

In reply to Nicola Vetrini

To be able to check for the existence of the necessary subsections in the documentation for MISRA C:2012 Dir 4.1, ECLAIR needs to have a source file that is built.

This file is generated from 'C-runtime-failures.rst' in docs/misra and the configuration is updated accordingly.

---
 docs/Makefile       |  7 ++++++-
 docs/misra/Makefile | 36 ++++++++++++++++++++++++++++++++++++
 2 files changed, 42 insertions(+), 1 deletion(-)
 create mode 100644 docs/misra/Makefile
docs/Makefile +6 -1
index 966a104490ac..ff991a0c3ca2 100644
@@ -43,7 +43,7 @@ DOC_PDF  := $(patsubst %.pandoc,pdf/%.pdf,$(PANDOCSRC-y)) \
 all: build
 
 .PHONY: build
-build: html txt pdf man-pages figs
+build: html txt pdf man-pages figs misra
 
 .PHONY: sphinx-html
 sphinx-html:
@@ -66,9 +66,14 @@ endif
 .PHONY: pdf
 pdf: $(DOC_PDF)
 
+.PHONY: misra
+misra:
+	$(MAKE) -C misra
+
 .PHONY: clean
 clean: clean-man-pages
 	$(MAKE) -C figs clean
+	$(MAKE) -C misra clean
 	rm -rf .word_count *.aux *.dvi *.bbl *.blg *.glo *.idx *~
 	rm -rf *.ilg *.log *.ind *.toc *.bak *.tmp core
 	rm -rf html txt pdf sphinx/html
docs/misra/Makefile new file +36 -0
new file mode 100644
index 000000000000..f62cd936bfcc
@@ -0,0 +1,36 @@
+XEN_ROOT=$(CURDIR)/../..
+include $(XEN_ROOT)/Config.mk
+-include $(XEN_ROOT)/config/Docs.mk
+
+
+TARGETS := $(addprefix C-runtime-failures,.c .o)
+
+all: $(TARGETS)
+
+define MISRA_HEADER
+/*
+
+endef
+
+define MISRA_FOOTER
+
+*/
+
+endef
+export MISRA_HEADER
+export MISRA_FOOTER
+
+C-runtime-failures.c: C-runtime-failures.rst
+# sed is used in place of cat to prevent occurrences of '*/'
+# in the .rst from breaking the compilation
+	( \
+	  echo "$${MISRA_HEADER}"; \
+	  sed -e 's|*/|*//*|' $<; \
+	  echo "$${MISRA_FOOTER}" \
+	) > $@
+
+%.o: %.c
+	$(CC) -c $< -o $@
+
+clean:
+	rm -f *.c *.o
Signature · 1 line
2.34.1
#3 lore raw

Re: [RFC PATCH 2/3] docs: make the docs for MISRA C:2012 Dir 4.1 visible to ECLAIR

Quoted 48 lines · Nicola Vetrini

To be able to check for the existence of the necessary subsections in the documentation for MISRA C:2012 Dir 4.1, ECLAIR needs to have a source file that is built.

This file is generated from 'C-runtime-failures.rst' in docs/misra and the configuration is updated accordingly.

---
 docs/Makefile       |  7 ++++++-
 docs/misra/Makefile | 36 ++++++++++++++++++++++++++++++++++++
 2 files changed, 42 insertions(+), 1 deletion(-)
 create mode 100644 docs/misra/Makefile
docs/Makefile +6 -1
index 966a104490ac..ff991a0c3ca2 100644
@@ -43,7 +43,7 @@ DOC_PDF  := $(patsubst %.pandoc,pdf/%.pdf,$(PANDOCSRC-y)) \
 all: build
 
 .PHONY: build
-build: html txt pdf man-pages figs
+build: html txt pdf man-pages figs misra
 
 .PHONY: sphinx-html
 sphinx-html:
@@ -66,9 +66,14 @@ endif
 .PHONY: pdf
 pdf: $(DOC_PDF)
 
+.PHONY: misra
+misra:
+	$(MAKE) -C misra
+
 .PHONY: clean
 clean: clean-man-pages
 	$(MAKE) -C figs clean
+	$(MAKE) -C misra clean
 	rm -rf .word_count *.aux *.dvi *.bbl *.blg *.glo *.idx *~
 	rm -rf *.ilg *.log *.ind *.toc *.bak *.tmp core
 	rm -rf html txt pdf sphinx/html
docs/misra/Makefile new file +0 -0
new file mode 100644
index 000000000000..f62cd936bfcc

docs/misra/Makefile line 3

Quoted 3 lines
docs/misra/Makefile new file +3 -0
@@ -0,0 +1,36 @@
+XEN_ROOT=$(CURDIR)/../..
+include $(XEN_ROOT)/Config.mk
+-include $(XEN_ROOT)/config/Docs.mk

Why do you include this? I can't spot what you consume from there. Also, why the leading -? _If_ you need something from there, surely you always need it (and hence you require ./configure to have been run up front)?

docs/misra/Makefile line 5

Quoted 2 lines
docs/misra/Makefile new file +2 -0
+
+

Nit (style): No double blank lines please.

docs/misra/Makefile line 6

Quoted 1 line
docs/misra/Makefile new file +1 -0
+TARGETS := $(addprefix C-runtime-failures,.c .o)

Does the .c really need listing here?

Quoted 4 lines
docs/misra/Makefile new file +4 -0
+all: $(TARGETS)
+
+define MISRA_HEADER
+/*

docs/misra/Makefile line 21

Quoted 10 lines
docs/misra/Makefile new file +10 -0
+
+endef
+
+define MISRA_FOOTER
+
+*/
+
+endef
+export MISRA_HEADER
+export MISRA_FOOTER

Style-wise I would say: Either you put each export immediately after its define, or you merge both into a single line.

docs/misra/Makefile line 30

Quoted 8 lines
docs/misra/Makefile new file +8 -0
+C-runtime-failures.c: C-runtime-failures.rst
+# sed is used in place of cat to prevent occurrences of '*/'
+# in the .rst from breaking the compilation
+	( \
+	  echo "$${MISRA_HEADER}"; \
+	  sed -e 's|*/|*//*|' $<; \
+	  echo "$${MISRA_FOOTER}" \
+	) > $@

The rule of thumb is to generate into a temporary file (then you also don't need to wrap everything in parentheses [or braces]), and then use mv to produce the final output. This escapes anomalies with failed or interrupted commands.

Jan

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw

Re: [RFC PATCH 2/3] docs: make the docs for MISRA C:2012 Dir 4.1 visible to ECLAIR

(Nicola, I'm sorry for the duplicate, but I didn't mean to drop xen-devel@.)

Quoted 15 lines · Nicola Vetrini
Quoted 5 lines
Quoted 5 lines
docs/misra/Makefile new file +5 -0
+C-runtime-failures.c: C-runtime-failures.rst
+# sed is used in place of cat to prevent occurrences of '*/'
+# in the .rst from breaking the compilation
+	( \
+	  echo "$${MISRA_HEADER}"; \
Quoted 9 lines

docs/misra/Makefile line 30

Quoted 3 lines
docs/misra/Makefile new file +3 -0
+	  sed -e 's|*/|*//*|' $<; \
+	  echo "$${MISRA_FOOTER}" \
+	) > $@

The rule of thumb is to generate into a temporary file (then you also don't need to wrap everything in parentheses [or braces]), and then use mv to produce the final output. This escapes anomalies with failed or interrupted commands.

Quoted 3 lines

I do see your point for temporary files, though wrapping commands with parentheses is a
fairly common pattern in Xen Makefiles afaict.

Now I'm curious: Grepping for ') >' underneath xen/ I couldn't find a single instance in any makefile. (I'm not going to exclude there are a few uses, but then likely not merely to combine multiple commands' output.)

Jan

#6 lore raw

Re: [RFC PATCH 2/3] docs: make the docs for MISRA C:2012 Dir 4.1 visible to ECLAIR

Quoted 16 lines · Jan Beulich
Quoted 15 lines · Nicola Vetrini
Quoted 14 lines

docs/misra/Makefile line 30

Quoted 8 lines
docs/misra/Makefile new file +8 -0
+C-runtime-failures.c: C-runtime-failures.rst
+# sed is used in place of cat to prevent occurrences of '*/'
+# in the .rst from breaking the compilation
+	( \
+	  echo "$${MISRA_HEADER}"; \
+	  sed -e 's|*/|*//*|' $<; \
+	  echo "$${MISRA_FOOTER}" \
+	) > $@

The rule of thumb is to generate into a temporary file (then you also don't need to wrap everything in parentheses [or braces]), and then use mv to produce the final output. This escapes anomalies with failed or interrupted commands.

Quoted 8 lines
Quoted 3 lines

I do see your point for temporary files, though wrapping commands with parentheses is a
fairly common pattern in Xen Makefiles afaict.

Now I'm curious: Grepping for ') >' underneath xen/ I couldn't find a single instance in any makefile. (I'm not going to exclude there are a few uses, but then likely not merely to combine multiple commands' output.)

Maybe using { } > out might be better that using ( ) > out. I think it would result in one less fork of the shell, without changing the resulting file, so always good to take.

You should add also set -e at the beginning, to take care of the sed command failing.

Or just use a temporary file.

Signature · 1 line
Anthony PERARD
#7 lore raw

Re: [RFC PATCH 2/3] docs: make the docs for MISRA C:2012 Dir 4.1 visible to ECLAIR

In reply to Nicola Vetrini
Quoted 19 lines · Nicola Vetrini
docs/misra/Makefile new file +13 -0
new file mode 100644
index 000000000000..f62cd936bfcc
@@ -0,0 +1,36 @@
+XEN_ROOT=$(CURDIR)/../..
+include $(XEN_ROOT)/Config.mk
+-include $(XEN_ROOT)/config/Docs.mk
+
+
+TARGETS := $(addprefix C-runtime-failures,.c .o)
+
+all: $(TARGETS)
+
+define MISRA_HEADER
+/*
+
+endef

docs/misra/Makefile line 23

Quoted 10 lines
docs/misra/Makefile new file +10 -0
+
+define MISRA_FOOTER
+
+*/
+
+endef
+export MISRA_HEADER
+export MISRA_FOOTER
+
+C-runtime-failures.c: C-runtime-failures.rst

Any reason not to use "%.c: %.rst" ? You could even write

    "C-runtime-failures.c: %.c: %.rst"

(Or even $(TARGETS:.o=.c): %.c %.rst", if TARGETS only had the .o, and if we expect all *.c to be generated from *.rst in this Makefile)

docs/misra/Makefile line 25

Quoted 2 lines
docs/misra/Makefile new file +2 -0
+# sed is used in place of cat to prevent occurrences of '*/'
+# in the .rst from breaking the compilation

I think I'd like this comment just before the rule, rather than between the target line and the recipe. That just push the recipe far way from the target due to the indentation.

docs/misra/Makefile line 27

Quoted 2 lines
docs/misra/Makefile new file +2 -0
+	( \
+	  echo "$${MISRA_HEADER}"; \

Would it be ok to just do echo "/*" here instead of defining a make variable and using it via the environment? I'd like to try to avoid the dollar escape $$ which make shell code harder to read when written in makefile.

docs/misra/Makefile line 28

Quoted 1 line
docs/misra/Makefile new file +1 -0
+	  sed -e 's|*/|*//*|' $<; \

The first '*' in this command is awkward, as its a special character. I'd rather not rely on sed to convert it to non-special, so could you escape it?

Also, this pattern only takes care of the first occurrence of '*/' on a line, but they could be more than one.

docs/misra/Makefile line 36

Quoted 8 lines
docs/misra/Makefile new file +8 -0
+	  echo "$${MISRA_FOOTER}" \
+	) > $@
+
+%.o: %.c
+	$(CC) -c $< -o $@
+
+clean:
+	rm -f *.c *.o

This rm -f *.c is prone to mistake. I hope no one is going to write a C file in this directory, run make clean and lost their source. Or, copy this makefile somewhere else. Would it be ok to just spell out all the .c files that are expected to be generated by this makefile?

Cheers,

Signature · 1 line
Anthony PERARD
#8 lore raw

RFC PATCH 3/3 automation/eclair: build docs/misra to address MISRA C:2012 Dir 4.1

In reply to Nicola Vetrini

The documentation pertaining Directive 4.1 is contained in docs/misra. The build script driving the analysis is amended to allow ECLAIR to find it and thus resolving violations of the directive.

---
 automation/eclair_analysis/build.sh   | 10 ++++++++--
 automation/eclair_analysis/prepare.sh |  1 +
 2 files changed, 9 insertions(+), 2 deletions(-)
automation/eclair_analysis/build.sh +8 -2
index ec087dd822fa..a0433eedeb4d 100755
@@ -34,8 +34,14 @@ else
 fi
 
 (
-  cd xen
-
+  cd docs
+  make "-j${PROCESSORS}" "-l${PROCESSORS}.0"    \
+       "CROSS_COMPILE=${CROSS_COMPILE}"         \
+       "CC=${CROSS_COMPILE}gcc-12"              \
+       "CXX=${CROSS_COMPILE}g++-12"             \
+       "XEN_TARGET_ARCH=${XEN_TARGET_ARCH}"     \
+       misra
+  cd ../xen
   make "-j${PROCESSORS}" "-l${PROCESSORS}.0"    \
        "CROSS_COMPILE=${CROSS_COMPILE}"         \
        "CC=${CROSS_COMPILE}gcc-12"              \
automation/eclair_analysis/prepare.sh +1 -0
index 275a1a3f517c..10854741790e 100755
@@ -35,6 +35,7 @@ else
 fi
 
 (
+    ./configure
     cd xen
     cp "${CONFIG_FILE}" .config
     make clean
Signature · 1 line
2.34.1
Acked-by on v1 3/3
#9 lore raw

Re: [RFC PATCH 3/3] automation/eclair: build docs/misra to address MISRA C:2012 Dir 4.1

Quoted 5 lines · Nicola Vetrini

The documentation pertaining Directive 4.1 is contained in docs/misra. The build script driving the analysis is amended to allow ECLAIR to find it and thus resolving violations of the directive.

Quoted 41 lines
---
 automation/eclair_analysis/build.sh   | 10 ++++++++--
 automation/eclair_analysis/prepare.sh |  1 +
 2 files changed, 9 insertions(+), 2 deletions(-)
automation/eclair_analysis/build.sh +8 -2
index ec087dd822fa..a0433eedeb4d 100755
@@ -34,8 +34,14 @@ else
 fi
 
 (
-  cd xen
-
+  cd docs
+  make "-j${PROCESSORS}" "-l${PROCESSORS}.0"    \
+       "CROSS_COMPILE=${CROSS_COMPILE}"         \
+       "CC=${CROSS_COMPILE}gcc-12"              \
+       "CXX=${CROSS_COMPILE}g++-12"             \
+       "XEN_TARGET_ARCH=${XEN_TARGET_ARCH}"     \
+       misra
+  cd ../xen
   make "-j${PROCESSORS}" "-l${PROCESSORS}.0"    \
        "CROSS_COMPILE=${CROSS_COMPILE}"         \
        "CC=${CROSS_COMPILE}gcc-12"              \
automation/eclair_analysis/prepare.sh +1 -0
index 275a1a3f517c..10854741790e 100755
@@ -35,6 +35,7 @@ else
 fi
 
 (
+    ./configure
     cd xen
     cp "${CONFIG_FILE}" .config
     make clean
Signature · 1 line
2.34.1