Skip to content

rust: convert Task to use ARef #774

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 23, 2022
Merged

Conversation

wedsonaf
Copy link

This is to unify the usage of all ref-counted C structures.

Signed-off-by: Wedson Almeida Filho [email protected]

This is to unify the usage of all ref-counted C structures.

Signed-off-by: Wedson Almeida Filho <[email protected]>
@wedsonaf wedsonaf merged commit f56c5f3 into Rust-for-Linux:rust May 23, 2022
@wedsonaf wedsonaf deleted the task-aref branch May 23, 2022 16:43
vtta pushed a commit to vtta/linux-archive that referenced this pull request Sep 29, 2023
The port lock is not always held when calling serial8250_clear_IER().
When an oops is in progress, the lock is tried to be taken and when it
is not, a warning is issued:
 WARNING: CPU: 0 PID: 1 at drivers/tty/serial/8250/8250_port.c:707 	+0x57/0x60
 Modules linked in:
 CPU: 0 PID: 1 Comm: init Not tainted 6.5.0-rc5-1.g225bfb7-default+ Rust-for-Linux#774 00f1be860db663ed29479b8255d3b01ab1135bd3
 Hardware name: QEMU Standard PC ...
 RIP: 0010:serial8250_clear_IER+0x57/0x60
...
 Call Trace:
  <TASK>
  serial8250_console_write+0x9e/0x4b0
  console_flush_all+0x217/0x5f0
...

Therefore, remove the annotation as it doesn't hold for all invocations.

The other option would be to make the lockdep test conditional on
'oops_in_progress' or pass 'locked' from serial8250_console_write(). I
don't think, that is worth it.

Signed-off-by: "Jiri Slaby (SUSE)" <[email protected]>
Reported-by: Vlastimil Babka <[email protected]>
Cc: John Ogness <[email protected]>
Fixes: d0b309a (serial: 8250: synchronize and annotate UART_IER access)
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants