The no_mangle attribute is unsafe since Rust 2024

blog/content/edition-2/posts/08-paging-introduction/index.fa.md

@@ -314,7 +314,7 @@ extern "x86-interrupt" fn page_fault_handler(
 ```rust
 // in src/main.rs
 
-#[no_mangle]
+#[unsafe(no_mangle)]
 pub extern "C" fn _start() -> ! {
     println!("Hello World{}", "!");
 
@@ -372,7 +372,7 @@ println!("write worked");
 ```rust
 // in src/main.rs
 
-#[no_mangle]
+#[unsafe(no_mangle)]
 pub extern "C" fn _start() -> ! {
     println!("Hello World{}", "!");
 

blog/content/edition-2/posts/08-paging-introduction/index.ja.md

@@ -321,7 +321,7 @@ extern "x86-interrupt" fn page_fault_handler(
 ```rust
 // in src/main.rs
 
-#[no_mangle]
+#[unsafe(no_mangle)]
 pub extern "C" fn _start() -> ! {
     println!("Hello World{}", "!");
 
@@ -379,7 +379,7 @@ println!("write worked");
 ```rust
 // in src/main.rs
 
-#[no_mangle]
+#[unsafe(no_mangle)]
 pub extern "C" fn _start() -> ! {
     println!("Hello World{}", "!");
 

blog/content/edition-2/posts/08-paging-introduction/index.md

@@ -309,7 +309,7 @@ Now we can try to access some memory outside our kernel:
 ```rust
 // in src/main.rs
 
-#[no_mangle]
+#[unsafe(no_mangle)]
 pub extern "C" fn _start() -> ! {
     println!("Hello World{}", "!");
 
@@ -367,7 +367,7 @@ Let's try to take a look at the page tables that define how our kernel is mapped
 ```rust
 // in src/main.rs
 
-#[no_mangle]
+#[unsafe(no_mangle)]
 pub extern "C" fn _start() -> ! {
     println!("Hello World{}", "!");
 

blog/content/edition-2/posts/08-paging-introduction/index.zh-CN.md

@@ -318,7 +318,7 @@ extern "x86-interrupt" fn page_fault_handler(
 ```rust
 // in src/main.rs
 
-#[no_mangle]
+#[unsafe(no_mangle)]
 pub extern "C" fn _start() -> ! {
     println!("Hello World{}", "!");
 
@@ -376,7 +376,7 @@ println!("write worked");
 ```rust
 // in src/main.rs
 
-#[no_mangle]
+#[unsafe(no_mangle)]
 pub extern "C" fn _start() -> ! {
     println!("Hello World{}", "!");