Skip to contentSkip to conversation

madvise: MADV_SOFT_OFFLINE requests can return -EBUSY

PATCH In review [email protected] 3 participants 6 messages Nov 26, 2024 – Dec 4, 2024 Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 madvise: MADV_SOFT_OFFLINE requests can return -EBUSY

If the page could not be offlined madvise will return -EBUSY. This might occur if the page is currently in use or locked.

---

man/man2/madvise.2 +7 -0
index 4f2210ee2..c10dcd599 100644
@@ -702,6 +702,13 @@ The map exists, but the area maps something that isn't a file.
 .BR MADV_COLLAPSE )
 Could not charge hugepage to cgroup: cgroup limit exceeded.
 .TP
+.B EBUSY
+(for
+.B MADV_SOFT_OFFLINE )
+If any pages within the add+length range could not be offlined,
+madvise will return -EBUSY.
+This might occur if the page is currently in use or locked.
+.TP
 .B EFAULT
 .I advice
 is
#1 lore raw

Hi Tyonnchie,

Quoted 1 line · On Tue, Nov 26, 2024 at 11:12:03AM -0500, [email protected] wrote:

If the page could not be offlined madvise will return -EBUSY. This might occur if the page is currently in use or locked.

Could you show this in a small example program (if possible)? Like 30 lines or so. If not, it's okay.

Have a lovely day!
Alex

Quoted 24 lines

---

man/man2/madvise.2 +7 -0
index 4f2210ee2..c10dcd599 100644
@@ -702,6 +702,13 @@ The map exists, but the area maps something that isn't a file.
 .BR MADV_COLLAPSE )
 Could not charge hugepage to cgroup: cgroup limit exceeded.
 .TP
+.B EBUSY
+(for
+.B MADV_SOFT_OFFLINE )
+If any pages within the add+length range could not be offlined,
+madvise will return -EBUSY.
+This might occur if the page is currently in use or locked.
+.TP
 .B EFAULT
 .I advice
 is
Signature · 1 line
<https://www.alejandro-colomar.es/>
#2 lore raw
Quoted 7 lines · Alejandro Colomar

Hi Tyonnchie,

Quoted 1 line · On Tue, Nov 26, 2024 at 11:12:03AM -0500, [email protected] wrote:

If the page could not be offlined madvise will return -EBUSY. This might occur if the page is currently in use or locked.

Could you show this in a small example program (if possible)? Like 30 lines or so. If not, it's okay.

Hi Alejandro!

Given the ongoing holidays, let me take the liberty of giving some context in order to keep the conversation going.

We received reports of failed LTP madvise11[1] tests. The errors looked like this:

    madvise11.c:409: TINFO: Spawning 4 threads, with a total of 640 memory pages
    madvise11.c:132: TFAIL: madvise failed: EBUSY (16)
    madvise11.c:163: TINFO: Thread  [0]  returned 16, failed.
    madvise11.c:191: TFAIL: thread  [0]  - exited with errors
    madvise11.c:163: TINFO: Thread  [2]  returned 0, succeeded.
    madvise11.c:163: TINFO: Thread  [3]  returned 0, succeeded.
    madvise11.c:163: TINFO: Thread  [1]  returned 0, succeeded.
    madvise11.c:361: TINFO: Restore 629 Soft-offlined pages
    madvise11.c:290: TWARN: write(3,0x7ffce114b8a0,8) failed: EBUSY (16)

Clearly the problem had to do with -EBUSY being returned by a madvise() operation. The bug was initially reported on kernels with PREEMPT_RT enabled but we soon observed that the problem also happened with the stock kernel, though requiring more repetitions to trigger issue.

After debug and investigation we observed that the -EBUSY return was a valid case in the kernel code and was not being handled by the test. A fix was sent to the LTP project by Li Wang[2], specifically for the madvise11 test.

In this process, we noticed that the man pages did not mention -EBUSY as a possible result of a failed offlining operation, as described by Tyonnchie.

I hope this helps!

Best regards,
Luis

[1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/madvise/madvise11.c
[2] https://lists.linux.it/pipermail/ltp/2024-May/038310.html

Quoted 19 lines

Have a lovely day!
Alex

Quoted 16 lines

---

man/man2/madvise.2 +3 -0
index 4f2210ee2..c10dcd599 100644
@@ -702,6 +702,13 @@ The map exists, but the area maps something that isn't a file.
 .BR MADV_COLLAPSE )
 Could not charge hugepage to cgroup: cgroup limit exceeded.
 .TP
+.B EBUSY
+(for
+.B MADV_SOFT_OFFLINE )
Quoted 11 lines
Quoted 8 lines
man/man2/madvise.2 +4 -0
+If any pages within the add+length range could not be offlined,
+madvise will return -EBUSY.
+This might occur if the page is currently in use or locked.
+.TP
 .B EFAULT
 .I advice
 is
Signature · 1 line
<https://www.alejandro-colomar.es/>

---end quoted text---

#3 lore raw

Hi Luis, Tyonnchie,

Quoted 32 lines · Luis Claudio R. Goncalves
Quoted 7 lines · Alejandro Colomar

Hi Tyonnchie,

Quoted 1 line · On Tue, Nov 26, 2024 at 11:12:03AM -0500, [email protected] wrote:

If the page could not be offlined madvise will return -EBUSY. This might occur if the page is currently in use or locked.

Could you show this in a small example program (if possible)? Like 30 lines or so. If not, it's okay.

Hi Alejandro!

Given the ongoing holidays, let me take the liberty of giving some context in order to keep the conversation going.

We received reports of failed LTP madvise11[1] tests. The errors looked like this:

    madvise11.c:409: TINFO: Spawning 4 threads, with a total of 640 memory pages
    madvise11.c:132: TFAIL: madvise failed: EBUSY (16)
    madvise11.c:163: TINFO: Thread  [0]  returned 16, failed.
    madvise11.c:191: TFAIL: thread  [0]  - exited with errors
    madvise11.c:163: TINFO: Thread  [2]  returned 0, succeeded.
    madvise11.c:163: TINFO: Thread  [3]  returned 0, succeeded.
    madvise11.c:163: TINFO: Thread  [1]  returned 0, succeeded.
    madvise11.c:361: TINFO: Restore 629 Soft-offlined pages
    madvise11.c:290: TWARN: write(3,0x7ffce114b8a0,8) failed: EBUSY (16)

Clearly the problem had to do with -EBUSY being returned by a madvise() operation. The bug was initially reported on kernels with PREEMPT_RT enabled but we soon observed that the problem also happened with the stock kernel, though requiring more repetitions to trigger issue.

Quoted 8 lines

After debug and investigation we observed that the -EBUSY return was a valid case in the kernel code and was not being handled by the test. A fix was sent to the LTP project by Li Wang[2], specifically for the madvise11 test.

In this process, we noticed that the man pages did not mention -EBUSY as a possible result of a failed offlining operation, as described by Tyonnchie.

I hope this helps!

Thanks! I've applied the patch, with some tweaks:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=3205359a3a7079d9d40a50388e851874729a827a>

I added an Acked-by on your behalf, Luis.

Have a lovely night!
Alex

Quoted 41 lines

Best regards,
Luis

[1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/madvise/madvise11.c
[2] https://lists.linux.it/pipermail/ltp/2024-May/038310.html

Quoted 19 lines

Have a lovely day!
Alex

Quoted 16 lines

---

man/man2/madvise.2 +3 -0
index 4f2210ee2..c10dcd599 100644
@@ -702,6 +702,13 @@ The map exists, but the area maps something that isn't a file.
 .BR MADV_COLLAPSE )
 Could not charge hugepage to cgroup: cgroup limit exceeded.
 .TP
+.B EBUSY
+(for
+.B MADV_SOFT_OFFLINE )
Quoted 11 lines
Quoted 8 lines
man/man2/madvise.2 +4 -0
+If any pages within the add+length range could not be offlined,
+madvise will return -EBUSY.
+This might occur if the page is currently in use or locked.
+.TP
 .B EFAULT
 .I advice
 is
Signature · 1 line
<https://www.alejandro-colomar.es/>

---end quoted text---

Signature · 1 line
<https://www.alejandro-colomar.es/>
#4 lore raw
Quoted 42 lines · Alejandro Colomar

Hi Luis, Tyonnchie,

Quoted 39 lines · Luis Claudio R. Goncalves
Quoted 7 lines · Alejandro Colomar

Hi Tyonnchie,

Quoted 1 line · On Tue, Nov 26, 2024 at 11:12:03AM -0500, [email protected] wrote:

If the page could not be offlined madvise will return -EBUSY. This might occur if the page is currently in use or locked.

Could you show this in a small example program (if possible)? Like 30 lines or so. If not, it's okay.

Hi Alejandro!

Given the ongoing holidays, let me take the liberty of giving some context in order to keep the conversation going.

We received reports of failed LTP madvise11[1] tests. The errors looked like this:

    madvise11.c:409: TINFO: Spawning 4 threads, with a total of 640 memory pages
    madvise11.c:132: TFAIL: madvise failed: EBUSY (16)
    madvise11.c:163: TINFO: Thread  [0]  returned 16, failed.
    madvise11.c:191: TFAIL: thread  [0]  - exited with errors
    madvise11.c:163: TINFO: Thread  [2]  returned 0, succeeded.
    madvise11.c:163: TINFO: Thread  [3]  returned 0, succeeded.
    madvise11.c:163: TINFO: Thread  [1]  returned 0, succeeded.
    madvise11.c:361: TINFO: Restore 629 Soft-offlined pages
    madvise11.c:290: TWARN: write(3,0x7ffce114b8a0,8) failed: EBUSY (16)

Clearly the problem had to do with -EBUSY being returned by a madvise() operation. The bug was initially reported on kernels with PREEMPT_RT enabled but we soon observed that the problem also happened with the stock kernel, though requiring more repetitions to trigger issue.

After debug and investigation we observed that the -EBUSY return was a valid case in the kernel code and was not being handled by the test. A fix was sent to the LTP project by Li Wang[2], specifically for the madvise11 test.

In this process, we noticed that the man pages did not mention -EBUSY as a possible result of a failed offlining operation, as described by Tyonnchie.

Quoted 6 lines
Quoted 1 line

I hope this helps!

Thanks! I've applied the patch, with some tweaks:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=3205359a3a7079d9d40a50388e851874729a827a>

I added an Acked-by on your behalf, Luis.

Thank you!

You have all my respect for the great work you and many others do with the man pages!

Luis

Quoted 43 lines

Have a lovely night!
Alex

Quoted 40 lines

Best regards,
Luis

[1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/madvise/madvise11.c
[2] https://lists.linux.it/pipermail/ltp/2024-May/038310.html

Quoted 30 lines

Have a lovely day!
Alex

Quoted 24 lines

---

man/man2/madvise.2 +7 -0
index 4f2210ee2..c10dcd599 100644
@@ -702,6 +702,13 @@ The map exists, but the area maps something that isn't a file.
 .BR MADV_COLLAPSE )
 Could not charge hugepage to cgroup: cgroup limit exceeded.
 .TP
+.B EBUSY
+(for
+.B MADV_SOFT_OFFLINE )
+If any pages within the add+length range could not be offlined,
+madvise will return -EBUSY.
+This might occur if the page is currently in use or locked.
+.TP
 .B EFAULT
 .I advice
 is
Signature · 1 line
<https://www.alejandro-colomar.es/>
Quoted 6 lines
Quoted 1 line

---end quoted text---

Signature · 1 line
<https://www.alejandro-colomar.es/>

---end quoted text---

#5 lore raw

On Wed, Dec 04, 2024 at 05:45:20PM -0300, Luis Claudio R. Goncalves wrote:

[...]

Quoted 11 lines
Quoted 6 lines
Quoted 1 line

I hope this helps!

Thanks! I've applied the patch, with some tweaks:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=3205359a3a7079d9d40a50388e851874729a827a>

I added an Acked-by on your behalf, Luis.

Thank you!

You have all my respect for the great work you and many others do with the man pages!

Thank you very much! :-}

Cheers,
Alex

Quoted 2 lines

Luis

Signature · 1 line
<https://www.alejandro-colomar.es/>