repo stringclasses 1
value | test_patch stringlengths 335 66.3k | issue_numbers listlengths 1 2 | version stringclasses 9
values | base_commit stringlengths 40 40 | problem_statement stringlengths 33 13k | instance_id stringlengths 24 25 | pull_number int64 183 1.64k | patch stringlengths 448 420k | hints_text stringlengths 0 64.4k | created_at stringlengths 20 20 | environment_setup_commit stringclasses 10
values |
|---|---|---|---|---|---|---|---|---|---|---|---|
asterinas/asterinas | diff --git /dev/null b/test/apps/pthread/pthread_signal_test.c
new file mode 100644
--- /dev/null
+++ b/test/apps/pthread/pthread_signal_test.c
@@ -0,0 +1,109 @@
+// SPDX-License-Identifier: MPL-2.0
+// A regression test for the futex lost wakeup bug fixed in https://github.com/asterinas/asterinas/pull/1642
+
+#include... | [
"1587"
] | 0.9 | 9da6af03943c15456cdfd781021820a7da78ea40 | `futex_wait_bitset()` should remove `futex_item` when `pause_timeout()` fails
### Describe the bug
1. When signaled or timeout, the `futex_item` is not removed from the `futex_bucket`, which can lead to lost-wakeup.
2. `waiter.pause_timeout()` returns `Ok(())` upon waking up from a signal, which can lead to incorre... | asterinas__asterinas-1642 | 1,642 | diff --git a/kernel/src/process/posix_thread/futex.rs b/kernel/src/process/posix_thread/futex.rs
--- a/kernel/src/process/posix_thread/futex.rs
+++ b/kernel/src/process/posix_thread/futex.rs
@@ -253,7 +253,9 @@ impl FutexBucket {
}
let item = item_cursor.remove().unwrap();
- item.... | The [wakeup test](https://github.com/torvalds/linux/blob/2d5404caa8c7bb5c4e0435f94b28834ae5456623/kernel/futex/waitwake.c#L671-L673) must take precedence over the [pending signals test](https://github.com/torvalds/linux/blob/2d5404caa8c7bb5c4e0435f94b28834ae5456623/kernel/futex/waitwake.c#L678-L683).
This is the rea... | 2024-11-26T12:04:42Z | 9da6af03943c15456cdfd781021820a7da78ea40 |
asterinas/asterinas | diff --git a/ostd/src/arch/x86/trap/trap.S b/ostd/src/arch/x86/trap/trap.S
--- a/ostd/src/arch/x86/trap/trap.S
+++ b/ostd/src/arch/x86/trap/trap.S
@@ -57,6 +57,7 @@ trap_handler_table:
.section .text
.global trap_common
trap_common:
+ cld # clear DF before calling/returning to any C function t... | [
"1606"
] | 0.9 | 5f35189a51ebc54298ea2cb0e4d53afe4e4e75eb | Shift overflow in `CpuSet` (`bit_idx` out of range)
### Describe the bug
A kernel panic is triggered due to a shift overflow. The `bit_idx` value is huge: `bit_idx=18446603338235158984`, which seems like an address (`0xffff8000780aa1c8`).
https://github.com/asterinas/asterinas/blob/e6c613f53841983765a7b3c56ea995... | asterinas__asterinas-1637 | 1,637 | diff --git a/ostd/src/arch/x86/trap/trap.S b/ostd/src/arch/x86/trap/trap.S
--- a/ostd/src/arch/x86/trap/trap.S
+++ b/ostd/src/arch/x86/trap/trap.S
@@ -57,6 +57,7 @@ trap_handler_table:
.section .text
.global trap_common
trap_common:
+ cld # clear DF before calling/returning to any C function t... | I did some debugging. It seems that using stack data in IRQs (like `SmallVec` in this case) might not be safe. Below is a summary of my findings to assist with further debugging.
### Create a test case to reproduce the bug reliably
Test case: `test/apps/dynamic/execve.c`
<details>
```c
#include <stdio.h>
... | 2024-11-24T15:05:40Z | 9da6af03943c15456cdfd781021820a7da78ea40 |
asterinas/asterinas | diff --git a/kernel/src/fs/pipe.rs b/kernel/src/fs/pipe.rs
--- a/kernel/src/fs/pipe.rs
+++ b/kernel/src/fs/pipe.rs
@@ -247,7 +247,7 @@ mod test {
W: Fn(Arc<PipeWriter>) + Sync + Send + 'static,
R: Fn(Arc<PipeReader>) + Sync + Send + 'static,
{
- let channel = Channel::with_capacity(1);
+ ... | [
"1554"
] | 0.9 | 11382524d1d23cc6d41adf977a72138baa39e38d | PIPE implementation does not guarantee atomic writes for up to PIPE_BUF bytes
### Describe the bug
The current implementation of the PIPE in Asterinas does not ensure that writes of up to PIPE_BUF bytes are atomic.
### To Reproduce
Apply the following patch and run `test/pipe/pipe_atomicity`
<details><summ... | asterinas__asterinas-1559 | 1,559 | diff --git a/kernel/src/fs/pipe.rs b/kernel/src/fs/pipe.rs
--- a/kernel/src/fs/pipe.rs
+++ b/kernel/src/fs/pipe.rs
@@ -247,7 +247,7 @@ mod test {
W: Fn(Arc<PipeWriter>) + Sync + Send + 'static,
R: Fn(Arc<PipeReader>) + Sync + Send + 'static,
{
- let channel = Channel::with_capacity(1);
+ ... | This one is easy to fix. Just check if the remaining space in the internal buffer of a pipe is no less than `PIPE_BUF` before actually writing the data. | 2024-11-05T07:28:33Z | 9da6af03943c15456cdfd781021820a7da78ea40 |
asterinas/asterinas | diff --git a/tools/bump_version.sh b/tools/bump_version.sh
--- a/tools/bump_version.sh
+++ b/tools/bump_version.sh
@@ -106,6 +106,9 @@ DOCS_DIR=${ASTER_SRC_DIR}/docs
OSTD_CARGO_TOML_PATH=${ASTER_SRC_DIR}/ostd/Cargo.toml
OSTD_TEST_CARGO_TOML_PATH=${ASTER_SRC_DIR}/ostd/libs/ostd-test/Cargo.toml
OSTD_MACROS_CARGO_TOML_... | [
"1291"
] | 0.9 | 2af9916de92f8ca1e694bb6ac5e33111bbcf51fd | Invalid opcode after relocation for Linux EFI-handover boot
<!-- Thank you for taking the time to report a bug. Your input is valuable to us.
Please replace all the <angle brackets> below with your own information. -->
### Describe the bug
<!-- A clear and concise description of what the bug is. -->
Sometimes... | asterinas__asterinas-1447 | 1,447 | diff --git a/Cargo.lock b/Cargo.lock
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1,6 +1,6 @@
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
-version = 3
+version = 4
[[package]]
name = "acpi"
diff --git a/Cargo.lock b/Cargo.lock
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1,6 +1,6 ... | 2024-10-14T14:03:58Z | 9da6af03943c15456cdfd781021820a7da78ea40 | |
asterinas/asterinas | diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -226,6 +226,8 @@ ktest: initramfs $(CARGO_OSDK)
@for dir in $(OSDK_CRATES); do \
[ $$dir = "ostd/libs/linux-bzimage/setup" ] && continue; \
(cd $$dir && cargo osdk test) || exit 1; \
+ tail --lines 10 qemu.log | grep -q "^\\[ktest runner\\] All ... | [
"1399",
"919"
] | 0.9 | 96efd620072a0cbdccc95b58901894111f17bb3a | Silently failed ktest in OSTD: untracked_map_unmap
<!-- Thank you for taking the time to report a bug. Your input is valuable to us.
Please replace all the <angle brackets> below with your own information. -->
### Describe the bug
<!-- A clear and concise description of what the bug is. -->
https://github.com... | asterinas__asterinas-1372 | 1,372 | diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -226,6 +226,8 @@ ktest: initramfs $(CARGO_OSDK)
@for dir in $(OSDK_CRATES); do \
[ $$dir = "ostd/libs/linux-bzimage/setup" ] && continue; \
(cd $$dir && cargo osdk test) || exit 1; \
+ tail --lines 10 qemu.log | grep -q "^\\[ktest runner\\] All ... |
I've already checked out your PR #918 addressing issues raised in this RFC, and find it convincing.
To sum up, the current inner API designs do have the 2 following major weaknesses:
- The "tracked" and "untracked" ranges are all managed by the page table, but the node is agnostic to it to some extent;
- The ... | 2024-09-24T09:24:48Z | 9da6af03943c15456cdfd781021820a7da78ea40 |
asterinas/asterinas | diff --git a/ostd/src/mm/page_table/test.rs b/ostd/src/mm/page_table/test.rs
--- a/ostd/src/mm/page_table/test.rs
+++ b/ostd/src/mm/page_table/test.rs
@@ -81,6 +81,10 @@ fn test_untracked_map_unmap() {
#[ktest]
fn test_user_copy_on_write() {
+ fn prot_op(prop: &mut PageProperty) {
+ prop.flags -= PageFlag... | [
"919"
] | 0.8 | ae4ac384713e63232b74915593ebdef680049d31 | [RFC] Safety model about the page tables
# Background
This issue discusses the internal APIs of the page table. More specifically, the following two sets of APIs:
- The APIs provided by `RawPageTableNode`/`PageTableNode`
- Files: [`framework/aster-frame/src/mm/page_table/node.rs`](https://github.com/asterinas/... | asterinas__asterinas-1369 | 1,369 | diff --git a/kernel/src/vm/vmar/mod.rs b/kernel/src/vm/vmar/mod.rs
--- a/kernel/src/vm/vmar/mod.rs
+++ b/kernel/src/vm/vmar/mod.rs
@@ -16,7 +16,7 @@ use align_ext::AlignExt;
use aster_rights::Rights;
use ostd::{
cpu::CpuExceptionInfo,
- mm::{VmSpace, MAX_USERSPACE_VADDR},
+ mm::{tlb::TlbFlushOp, PageFlags,... | I've already checked out your PR #918 addressing issues raised in this RFC, and find it convincing.
To sum up, the current inner API designs do have the 2 following major weaknesses:
- The "tracked" and "untracked" ranges are all managed by the page table, but the node is agnostic to it to some extent;
- The s... | 2024-09-23T14:17:42Z | ae4ac384713e63232b74915593ebdef680049d31 |
asterinas/asterinas | diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -16,7 +17,14 @@ LOG_LEVEL ?= error
SCHEME ?= ""
SMP ?= 1
OSTD_TASK_STACK_SIZE_IN_PAGES ?= 64
-# End of global options.
+# End of global build options.
+
+# GDB debugging and profiling options.
+GDB_TCP_PORT ?= 1234
+GDB_PROFILE_FORMAT ?= flame-graph
+... | [
"964"
] | 0.8 | f7932595125a0bba8230b5f8d3b110c687d6f3b2 | [Perf Guide] Flame graph scripts on Asterinas
[Flame graph](https://github.com/brendangregg/FlameGraph) is a well known and powerful tool for performance (bottoleneck) analysis. It's based on sampling. If you inspect the call stack 100 times per second, the function that appears more often, would like to consume more t... | asterinas__asterinas-1362 | 1,362 | diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -1,13 +1,14 @@
# SPDX-License-Identifier: MPL-2.0
-# Global options.
+# =========================== Makefile options. ===============================
+
+# Global build options.
ARCH ?= x86_64
BENCHMARK ?= none
BOOT_METHOD ?= grub-rescue-iso
BOOT_P... | 2024-09-21T13:48:03Z | ae4ac384713e63232b74915593ebdef680049d31 | |
asterinas/asterinas | diff --git a/kernel/src/lib.rs b/kernel/src/lib.rs
--- a/kernel/src/lib.rs
+++ b/kernel/src/lib.rs
@@ -146,15 +143,8 @@ fn init_thread() {
// driver::pci::virtio::block::block_device_test();
let thread = Thread::spawn_kernel_thread(ThreadOptions::new(|| {
println!("[kernel] Hello world from kernel!")... | [
"1244"
] | 0.8 | 42e28763c59202486af4298d5305e5c5e5ab9b54 | Reachable unwrap panic in `read_clock()`
### Describe the bug
There is a reachable unwrap panic in `read_clock()` at kernel/src/syscall/clock_gettime.rs:141 when make a `clock_gettime` syscall with specific argument.
https://github.com/asterinas/asterinas/blob/aa77747f94c4b1cb1237ba52414642827a6efc25/kernel/src/sys... | asterinas__asterinas-1328 | 1,328 | diff --git a/kernel/src/lib.rs b/kernel/src/lib.rs
--- a/kernel/src/lib.rs
+++ b/kernel/src/lib.rs
@@ -133,10 +133,7 @@ fn ap_init() -> ! {
}
fn init_thread() {
- println!(
- "[kernel] Spawn init thread, tid = {}",
- current_thread!().tid()
- );
+ println!("[kernel] Spawn init thread");
... | 2024-09-12T06:03:09Z | ae4ac384713e63232b74915593ebdef680049d31 | |
asterinas/asterinas | diff --git a/ostd/src/sync/mutex.rs b/ostd/src/sync/mutex.rs
--- a/ostd/src/sync/mutex.rs
+++ b/ostd/src/sync/mutex.rs
@@ -138,3 +150,27 @@ impl<'a, T: ?Sized> MutexGuard<'a, T> {
guard.mutex
}
}
+
+#[cfg(ktest)]
+mod test {
+ use super::*;
+ use crate::prelude::*;
+
+ // A regression test for a... | [
"1274"
] | 0.8 | 963874471284ed014b76d268d933b6d13073c2cc | Potential mutex lock bug leading to multiple threads entering critical section
### Describe the bug
Hi there!
I'm working on a testcase for issue #1261 to reproduce the bug, and I noticed a weird behavior. It seems that `mutex.lock()` does not block when another thread has already acquired the lock in `ktest`. Th... | asterinas__asterinas-1279 | 1,279 | diff --git a/ostd/src/sync/mutex.rs b/ostd/src/sync/mutex.rs
--- a/ostd/src/sync/mutex.rs
+++ b/ostd/src/sync/mutex.rs
@@ -50,7 +50,9 @@ impl<T: ?Sized> Mutex<T> {
pub fn try_lock(&self) -> Option<MutexGuard<T>> {
// Cannot be reduced to `then_some`, or the possible dropping of the temporary
// g... | The bug introduced in this commit: https://github.com/asterinas/asterinas/commit/d15b4d9115cf33490245c06a93928995765f0d3f#r146080074
A potential fix: #497 | 2024-09-02T06:56:20Z | ae4ac384713e63232b74915593ebdef680049d31 |
asterinas/asterinas | diff --git a/osdk/src/config/manifest.rs b/osdk/src/config/manifest.rs
--- a/osdk/src/config/manifest.rs
+++ b/osdk/src/config/manifest.rs
@@ -128,82 +128,7 @@ fn deserialize_toml_manifest(path: impl AsRef<Path>) -> Option<TomlManifest> {
for scheme in manifest.map.values_mut() {
scheme.work_dir = Some(cw... | [
"1237"
] | 0.8 | 539984bbed414969b0c40cf181a10e9341ed2359 | OSDK should not check the options that have been overridden
### Describe the bug
OSDK will (but should not) keep checking the existence of the file, despite that option is overridden .
### To Reproduce
1. Create a `OSDK.toml` whose `initramfs` points to a non-exist file.
``` toml
[boot]
initramfs =... | asterinas__asterinas-1256 | 1,256 | diff --git a/osdk/Cargo.lock b/osdk/Cargo.lock
--- a/osdk/Cargo.lock
+++ b/osdk/Cargo.lock
@@ -146,7 +146,7 @@ dependencies = [
[[package]]
name = "cargo-osdk"
-version = "0.8.0"
+version = "0.8.1"
dependencies = [
"assert_cmd",
"clap",
diff --git a/osdk/Cargo.lock b/osdk/Cargo.lock
--- a/osdk/Cargo.lock
+++ b... | 2024-08-28T11:24:08Z | ae4ac384713e63232b74915593ebdef680049d31 | |
asterinas/asterinas | diff --git a/kernel/aster-nix/src/process/process_filter.rs b/kernel/aster-nix/src/process/process_filter.rs
--- a/kernel/aster-nix/src/process/process_filter.rs
+++ b/kernel/aster-nix/src/process/process_filter.rs
@@ -14,14 +14,15 @@ pub enum ProcessFilter {
impl ProcessFilter {
// used for waitid
- pub fn ... | [
"1197"
] | 0.6 | 562e64437584279783f244edba10b512beddc81d | Reachable unwrap panic in `ProcessFilter::from_which_and_id()`
### Describe the bug
There is a reachable unwrap panic in `ProcessFilter::from_which_and_id()` at kernel/aster-nix/src/process/process_filter.rs:24 when make a `waitid` syscall.
https://github.com/asterinas/asterinas/blob/ce2af1eb057077753a7a757edc1833e... | asterinas__asterinas-1215 | 1,215 | diff --git a/kernel/aster-nix/src/process/process_filter.rs b/kernel/aster-nix/src/process/process_filter.rs
--- a/kernel/aster-nix/src/process/process_filter.rs
+++ b/kernel/aster-nix/src/process/process_filter.rs
@@ -14,14 +14,15 @@ pub enum ProcessFilter {
impl ProcessFilter {
// used for waitid
- pub fn ... | 2024-08-21T12:44:17Z | 562e64437584279783f244edba10b512beddc81d | |
asterinas/asterinas | diff --git a/test/benchmark/lmbench-mem-fcp/config.json b/test/benchmark/lmbench-mem-fcp/config.json
--- a/test/benchmark/lmbench-mem-fcp/config.json
+++ b/test/benchmark/lmbench-mem-fcp/config.json
@@ -1,7 +1,7 @@
{
"alert_threshold": "125%",
"alert_tool": "customBiggerIsBetter",
- "search_pattern": "134... | [
"1155"
] | 0.6 | 0291b5dc6bb142b9c6165c1cb29b7658eefdaa63 | Unexpected benchmark alert triggered
I've observed that the recent benchmark workflow has consistently failed due to the `lmbench-mem` alert being triggered. This benchmark exhibits considerable instability on both Asterinas and Linux platforms. Notably, even identical commits can yield divergent results. In light of t... | asterinas__asterinas-1187 | 1,187 | diff --git a/test/benchmark/lmbench-mem-fcp/config.json b/test/benchmark/lmbench-mem-fcp/config.json
--- a/test/benchmark/lmbench-mem-fcp/config.json
+++ b/test/benchmark/lmbench-mem-fcp/config.json
@@ -1,7 +1,7 @@
{
"alert_threshold": "125%",
"alert_tool": "customBiggerIsBetter",
- "search_pattern": "134... | Or we can run the benchmark for more times?
@boterinas claim | 2024-08-16T08:24:13Z | 562e64437584279783f244edba10b512beddc81d |
asterinas/asterinas | diff --git a/.github/workflows/publish_osdk_and_ostd.yml b/.github/workflows/publish_osdk_and_ostd.yml
--- a/.github/workflows/publish_osdk_and_ostd.yml
+++ b/.github/workflows/publish_osdk_and_ostd.yml
@@ -16,7 +16,7 @@ jobs:
osdk-publish:
runs-on: ubuntu-latest
timeout-minutes: 10
- container: asterin... | [
"975"
] | 0.7 | c2a83427520f8263a8eb2c36edacdba261ad5cae | ktest as a kernel
<!-- Thank you for taking the time to propose a new idea or significant change. Please provide a comprehensive overview of the concepts and motivations at play. -->
### Summary
<!-- Briefly summarize the idea, change, or feature you are proposing. What is it about, and what does it aim to achiev... | asterinas__asterinas-1159 | 1,159 | diff --git a/.github/workflows/benchmark_asterinas.yml b/.github/workflows/benchmark_asterinas.yml
--- a/.github/workflows/benchmark_asterinas.yml
+++ b/.github/workflows/benchmark_asterinas.yml
@@ -57,7 +57,7 @@ jobs:
fail-fast: false
timeout-minutes: 60
container:
- image: asterinas/asterinas:0... | This proposal aims to address to problems.
> * a lot of runtime needed when running ktest, which need to be passed as parameters https://github.com/asterinas/asterinas/pull/834 ;
> * need to pass cfg to aster-frame when rebuilding the test https://github.com/asterinas/asterinas/issues/974 ;
I can see why this pr... | 2024-08-13T11:21:28Z | c2a83427520f8263a8eb2c36edacdba261ad5cae |
asterinas/asterinas | diff --git a/osdk/tests/examples_in_book/write_a_kernel_in_100_lines_templates/lib.rs b/osdk/tests/examples_in_book/write_a_kernel_in_100_lines_templates/lib.rs
--- a/osdk/tests/examples_in_book/write_a_kernel_in_100_lines_templates/lib.rs
+++ b/osdk/tests/examples_in_book/write_a_kernel_in_100_lines_templates/lib.rs
@... | [
"1264"
] | 0.8 | c68302f7007225fa47f22a1085a8c59dcdae2ad4 | Sporadic SMP syscall test aborts
<!-- Thank you for taking the time to report a bug. Your input is valuable to us.
Please replace all the <angle brackets> below with your own information. -->
### Describe the bug
<!-- A clear and concise description of what the bug is. -->
The SMP syscall test aborts with no ... | asterinas__asterinas-1158 | 1,158 | diff --git a/kernel/src/sched/priority_scheduler.rs b/kernel/src/sched/priority_scheduler.rs
--- a/kernel/src/sched/priority_scheduler.rs
+++ b/kernel/src/sched/priority_scheduler.rs
@@ -50,12 +50,12 @@ impl<T: PreemptSchedInfo> PreemptScheduler<T> {
let mut minimum_load = usize::MAX;
for candidate ... | 2024-08-13T09:28:07Z | ae4ac384713e63232b74915593ebdef680049d31 | |
asterinas/asterinas | diff --git a/kernel/aster-nix/src/lib.rs b/kernel/aster-nix/src/lib.rs
--- a/kernel/aster-nix/src/lib.rs
+++ b/kernel/aster-nix/src/lib.rs
@@ -89,9 +89,6 @@ fn init_thread() {
// Work queue should be initialized before interrupt is enabled,
// in case any irq handler uses work queue as bottom half
thread... | [
"1130"
] | 0.6 | 38b46f7ac3dd206d116f7db1fa33654569a8e443 | We shouldn't disable preemption when disabling IRQ.
Currently `ostd::trap::disable_local` disables preemption as well when disabling IRQ. However, such a policy would like to be based on an observation that: "we shouldn't do `switch_to_task()` when IRQ is disabled". Indeed we shouldn't do so. But this is not the best w... | asterinas__asterinas-1154 | 1,154 | diff --git a/kernel/aster-nix/src/lib.rs b/kernel/aster-nix/src/lib.rs
--- a/kernel/aster-nix/src/lib.rs
+++ b/kernel/aster-nix/src/lib.rs
@@ -89,9 +89,6 @@ fn init_thread() {
// Work queue should be initialized before interrupt is enabled,
// in case any irq handler uses work queue as bottom half
thread... | 2024-08-12T13:23:15Z | 562e64437584279783f244edba10b512beddc81d | |
asterinas/asterinas | diff --git a/osdk/tests/cli/mod.rs b/osdk/tests/cli/mod.rs
--- a/osdk/tests/cli/mod.rs
+++ b/osdk/tests/cli/mod.rs
@@ -1,5 +1,7 @@
// SPDX-License-Identifier: MPL-2.0
+use std::fs;
+
use crate::util::*;
#[test]
diff --git a/osdk/tests/cli/mod.rs b/osdk/tests/cli/mod.rs
--- a/osdk/tests/cli/mod.rs
+++ b/osdk/test... | [
"1135"
] | 0.6 | 6414111cc57b42db2bae1a0c8b01b85c3830a3b3 | OSDK should support creating crate with `-` in its name
As discovered by #1133, `cargo osdk new --kernel my-first-os` will panic due to `my-first-os` contains `-`.
Since `cargo new my-first-os` is allowed, we should fix the problem to keep osdk consistent with cargo.
| asterinas__asterinas-1138 | 1,138 | diff --git a/osdk/src/commands/new/mod.rs b/osdk/src/commands/new/mod.rs
--- a/osdk/src/commands/new/mod.rs
+++ b/osdk/src/commands/new/mod.rs
@@ -163,18 +163,14 @@ fn get_manifest_path<'a>(cargo_metadata: &'a serde_json::Value, crate_name: &str
fn get_src_path<'a>(cargo_metadata: &'a serde_json::Value, crate_name: &s... | 2024-08-08T01:38:09Z | 562e64437584279783f244edba10b512beddc81d | |
asterinas/asterinas | diff --git a/kernel/aster-nix/src/process/process/mod.rs b/kernel/aster-nix/src/process/process/mod.rs
--- a/kernel/aster-nix/src/process/process/mod.rs
+++ b/kernel/aster-nix/src/process/process/mod.rs
@@ -636,15 +645,6 @@ impl Process {
}
}
-pub fn current() -> Arc<Process> {
- let current_thread = current... | [
"1106"
] | 0.6 | d04111079cb8edf03d9a58b2bd88d4af4b11543a | Lockless mutability for current task data.
**This is currently a work-in-progress RFC**
<!-- Thank you for taking the time to propose a new idea or significant change. Please provide a comprehensive overview of the concepts and motivations at play. -->
### Summary
<!-- Briefly summarize the idea, change, or fe... | asterinas__asterinas-1125 | 1,125 | diff --git a/kernel/aster-nix/src/prelude.rs b/kernel/aster-nix/src/prelude.rs
--- a/kernel/aster-nix/src/prelude.rs
+++ b/kernel/aster-nix/src/prelude.rs
@@ -26,7 +26,7 @@ pub(crate) use ostd::{
#[macro_export]
macro_rules! current {
() => {
- $crate::process::current()
+ $crate::process::Process:... | Let's say we have a function `foo` with `#[code_context::task]` attribute. How would this `foo` function "receive references to the task data as arguments"? What would the user code look like?
> ```rust
> /// The entrypoint function of a task takes 4 arguments:
> /// 1. the mutable task context,
> /// 2. the share... | 2024-08-03T03:09:32Z | 562e64437584279783f244edba10b512beddc81d |
asterinas/asterinas | diff --git a/ostd/src/mm/dma/dma_coherent.rs b/ostd/src/mm/dma/dma_coherent.rs
--- a/ostd/src/mm/dma/dma_coherent.rs
+++ b/ostd/src/mm/dma/dma_coherent.rs
@@ -192,7 +211,7 @@ mod test {
use alloc::vec;
use super::*;
- use crate::{mm::FrameAllocOptions, prelude::*};
+ use crate::mm::FrameAllocOptions;
... | [
"1089"
] | 0.6 | aa84b31634b9c710e04b337c5d1b8fa207f8dbde | Syscall test at Ext2, MicroVM occasionally fails
<!-- Thank you for taking the time to report a bug. Your input is valuable to us.
Please replace all the <angle brackets> below with your own information. -->
### Describe the bug
<!-- A clear and concise description of what the bug is. -->
### To Reproduce
... | asterinas__asterinas-1112 | 1,112 | diff --git a/Cargo.lock b/Cargo.lock
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -398,6 +398,12 @@ dependencies = [
"toml",
]
+[[package]]
+name = "const-assert"
+version = "1.0.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d8298db53081b3a951cadb6e0f4ebbe36def7bcb591a34676708d0d7ac87dd... | Another example:
https://github.com/asterinas/asterinas/actions/runs/10104476344/job/27943517035?pr=1030
I found it being reproducible (randomly) locally. And it has nothing to do with Ext2. It seems to be a problem with MicroVM.
It is really easy to reproduce but once you need to debug (via printing or gdb), it is ... | 2024-07-30T04:20:46Z | 562e64437584279783f244edba10b512beddc81d |
asterinas/asterinas | diff --git a/ostd/src/panicking.rs b/ostd/src/panicking.rs
--- a/ostd/src/panicking.rs
+++ b/ostd/src/panicking.rs
@@ -29,17 +23,22 @@ use unwinding::{
/// panic handler in the binary crate.
#[export_name = "__aster_panic_handler"]
pub fn panic_handler(info: &core::panic::PanicInfo) -> ! {
- let throw_info = ostd... | [
"1089"
] | 0.6 | e83e1fc01ba38ad2a405d7d710ec7258fb664f60 | Syscall test at Ext2, MicroVM occasionally fails
<!-- Thank you for taking the time to report a bug. Your input is valuable to us.
Please replace all the <angle brackets> below with your own information. -->
### Describe the bug
<!-- A clear and concise description of what the bug is. -->
### To Reproduce
... | asterinas__asterinas-1103 | 1,103 | diff --git a/docs/src/kernel/advanced-instructions.md b/docs/src/kernel/advanced-instructions.md
--- a/docs/src/kernel/advanced-instructions.md
+++ b/docs/src/kernel/advanced-instructions.md
@@ -93,3 +93,6 @@ Your previous launch configs will be restored after the server is down.
Press `F5`(Run and Debug) to start a d... | Another example:
https://github.com/asterinas/asterinas/actions/runs/10104476344/job/27943517035?pr=1030
I found it being reproducible (randomly) locally. And it has nothing to do with Ext2. It seems to be a problem with MicroVM.
It is really easy to reproduce but once you need to debug (via printing or gdb), it is ... | 2024-07-26T11:09:27Z | 562e64437584279783f244edba10b512beddc81d |
asterinas/asterinas | diff --git a/test/apps/network/listen_backlog.c b/test/apps/network/listen_backlog.c
--- a/test/apps/network/listen_backlog.c
+++ b/test/apps/network/listen_backlog.c
@@ -131,7 +131,7 @@ int main(void)
for (backlog = 0; backlog <= MAX_TEST_BACKLOG; ++backlog) {
// Avoid "bind: Address already in use"
- addr.sin... | [
"819"
] | 0.6 | e83e1fc01ba38ad2a405d7d710ec7258fb664f60 | Polling ifaces may not ensure packets be transmitted
The problem occurs when I trying to send two messages to the same TCP socket, and trying to receive the two messages at once.
```C
TEST_RES(sendmsg(sk_accepted, &msg, 0), _ret == strlen(message));
TEST_RES(sendmsg(sk_accepted, &msg, 0), _ret == strlen(message));... | asterinas__asterinas-1098 | 1,098 | diff --git a/kernel/aster-nix/src/net/iface/any_socket.rs b/kernel/aster-nix/src/net/iface/any_socket.rs
--- a/kernel/aster-nix/src/net/iface/any_socket.rs
+++ b/kernel/aster-nix/src/net/iface/any_socket.rs
@@ -59,14 +59,7 @@ impl AnyUnboundSocket {
}
}
-pub struct AnyBoundSocket {
- iface: Arc<dyn Iface>,
-... | 2024-07-26T01:51:02Z | 562e64437584279783f244edba10b512beddc81d | |
asterinas/asterinas | diff --git a/.github/workflows/test_asterinas.yml b/.github/workflows/test_asterinas.yml
--- a/.github/workflows/test_asterinas.yml
+++ b/.github/workflows/test_asterinas.yml
@@ -60,36 +60,24 @@ jobs:
id: boot_test_mb
run: make run AUTO_TEST=boot ENABLE_KVM=1 BOOT_PROTOCOL=multiboot RELEASE=1
- ... | [
"1069"
] | 0.6 | 5aa28eae7e14594bbe68827114443b31002bf742 | CPU local memory is used before initialized
The use (in `ostd`):
`init` → `mm::heap_allocator::init` → `HEAP_ALLOCATOR.init` → `SpinLock::lock_irq_disabled` → `trap::irq::disable_local` → `task::processor::disable_preempt` → `PREEMPT_COUNT.increase_num_locks`, where `PREEMPT_COUNT` is a cpu-local variable.
The init... | asterinas__asterinas-1073 | 1,073 | diff --git a/.github/workflows/test_asterinas.yml b/.github/workflows/test_asterinas.yml
--- a/.github/workflows/test_asterinas.yml
+++ b/.github/workflows/test_asterinas.yml
@@ -60,36 +60,24 @@ jobs:
id: boot_test_mb
run: make run AUTO_TEST=boot ENABLE_KVM=1 BOOT_PROTOCOL=multiboot RELEASE=1
- ... | Modifying `ostd::arch::x86::cpu::get_cpu_local_base` to
``` rust
/// Gets the base address for the CPU local storage by reading the FS base model-specific register.
pub(crate) fn get_cpu_local_base() -> u64 {
let fsbase = FS::read_base().as_u64();
debug_assert_ne!(fsbase, 0, "CPU local memory is used befor... | 2024-07-19T13:26:35Z | 562e64437584279783f244edba10b512beddc81d |
asterinas/asterinas | diff --git a/test/syscall_test/blocklists/epoll_test b/test/syscall_test/blocklists/epoll_test
--- a/test/syscall_test/blocklists/epoll_test
+++ b/test/syscall_test/blocklists/epoll_test
@@ -6,4 +6,7 @@ EpollTest.EdgeTriggered_NoRandomSave
EpollTest.OneshotAndEdgeTriggered
EpollTest.CycleOfOneDisallowed
EpollTest.Cy... | [
"868"
] | 0.6 | c7d2a908e04f359f99443e6ea9423fff736de361 | Epoll syscall tests crash occasionally
When running tests with the command `make run AUTO_TEST=syscall ENABLE_KVM=1 BOOT_PROTOCOL=linux-efi-handover64 RELEASE=1`, some `epoll` tests (from gvisor) will crash.
```
EpollTest.TimeoutNoFds
EpollTest.UnblockWithNewFD
EpollTest.Oneshot
```
The above tests crashed wi... | asterinas__asterinas-1035 | 1,035 | diff --git a/test/syscall_test/blocklists/epoll_test b/test/syscall_test/blocklists/epoll_test
--- a/test/syscall_test/blocklists/epoll_test
+++ b/test/syscall_test/blocklists/epoll_test
@@ -6,4 +6,7 @@ EpollTest.EdgeTriggered_NoRandomSave
EpollTest.OneshotAndEdgeTriggered
EpollTest.CycleOfOneDisallowed
EpollTest.Cy... | 2024-07-07T20:03:32Z | 562e64437584279783f244edba10b512beddc81d | |
asterinas/asterinas | diff --git a/osdk/tests/examples_in_book/write_a_kernel_in_100_lines_templates/lib.rs b/osdk/tests/examples_in_book/write_a_kernel_in_100_lines_templates/lib.rs
--- a/osdk/tests/examples_in_book/write_a_kernel_in_100_lines_templates/lib.rs
+++ b/osdk/tests/examples_in_book/write_a_kernel_in_100_lines_templates/lib.rs
@... | [
"681"
] | 0.6 | 94eba6d85eb9e62ddd904c1132d556b808cc3174 | The APIs of `VmSpace` are vulnerable to race conditions
```rust
#[derive(Debug, Clone)]
pub struct VmSpace {
memory_set: Arc<Mutex<MemorySet>>,
}
impl VmSpace {
/// determine whether a vaddr is already mapped
pub fn is_mapped(&self, vaddr: Vaddr) -> bool {
let memory_set = self.memory_set.... | asterinas__asterinas-1026 | 1,026 | diff --git a/kernel/aster-nix/src/vm/vmar/vm_mapping.rs b/kernel/aster-nix/src/vm/vmar/vm_mapping.rs
--- a/kernel/aster-nix/src/vm/vmar/vm_mapping.rs
+++ b/kernel/aster-nix/src/vm/vmar/vm_mapping.rs
@@ -5,7 +5,9 @@
use core::ops::Range;
-use ostd::mm::{Frame, FrameVec, PageFlags, VmIo, VmMapOptions, VmSpace};
+use... | 2024-07-04T11:40:07Z | 562e64437584279783f244edba10b512beddc81d | |
asterinas/asterinas | diff --git a/.github/workflows/publish_api_docs.yml /dev/null
--- a/.github/workflows/publish_api_docs.yml
+++ /dev/null
@@ -1,43 +0,0 @@
-name: Update API docs
-
-on:
- # Scheduled events for nightly API docs
- schedule:
- # UTC 00:00 everyday
- - cron: "0 0 * * *"
- # Events for API docs of new release
- pu... | [
"1009"
] | 0.6 | 8a9c012249d36c54712030c41388d20a608939f5 | Tracking issue for publishing OSTD to crates.io
# Description
This issue tracks the issue of publishing OSTD to `crates.io`
- [x] Publishing all dependent crates of OSTD to `crates.io`
- [x] align_ext ([v0.1.0](https://crates.io/crates/align_ext))
- [x] ostd-macros([v0.1.1](https://crates.io/crates/ostd-mac... | asterinas__asterinas-1018 | 1,018 | diff --git a/.github/workflows/publish_api_docs.yml /dev/null
--- a/.github/workflows/publish_api_docs.yml
+++ /dev/null
@@ -1,43 +0,0 @@
-name: Update API docs
-
-on:
- # Scheduled events for nightly API docs
- schedule:
- # UTC 00:00 everyday
- - cron: "0 0 * * *"
- # Events for API docs of new release
- pu... | 2024-07-03T08:57:04Z | 562e64437584279783f244edba10b512beddc81d | |
asterinas/asterinas | diff --git a/ostd/src/boot/mod.rs b/ostd/src/boot/mod.rs
--- a/ostd/src/boot/mod.rs
+++ b/ostd/src/boot/mod.rs
@@ -137,10 +137,6 @@ pub fn call_ostd_main() -> ! {
static KTEST_TEST_WHITELIST: Option<&'static [&'static str]>;
static KTEST_CRATE_WHITELIST: Option<&'static [&'static str]>;
... | [
"944"
] | 0.6 | 4844e7ca7ca6d78896a51a71487a6fdfe9ca6654 | RFC: The new scheduling API of Asterinas Framework
## Introduction
This RFC proposes a new set of API for the scheduling subsystem of Asterinas Framework. The new API aims at enabling the Framework users to implement advanced scheduler algorithms such as Linux's CFS and support multiple schedulers such as Linux's sc... | asterinas__asterinas-990 | 990 | diff --git a/kernel/aster-nix/src/sched/priority_scheduler.rs b/kernel/aster-nix/src/sched/priority_scheduler.rs
--- a/kernel/aster-nix/src/sched/priority_scheduler.rs
+++ b/kernel/aster-nix/src/sched/priority_scheduler.rs
@@ -1,56 +1,234 @@
// SPDX-License-Identifier: MPL-2.0
-use intrusive_collections::LinkedList;... | From my point of view, I suggest removing the `RunQueue` trait and the `fn rq(&self, cpu: CpuId) -> &Arc<dyn RunQueue>` method _if_ we cannot figure out any real use cases for them in the Asterinas framework.
We can easily add them in the future if we find them useful in some way, but at least for the use cases list... | 2024-06-28T06:42:22Z | 562e64437584279783f244edba10b512beddc81d |
asterinas/asterinas | diff --git a/docs/src/ostd/a-100-line-kernel.md b/docs/src/ostd/a-100-line-kernel.md
--- a/docs/src/ostd/a-100-line-kernel.md
+++ b/docs/src/ostd/a-100-line-kernel.md
@@ -7,23 +7,7 @@ we will show a new kernel in about 100 lines of safe Rust.
Our new kernel will be able to run the following Hello World program.
```... | [
"871"
] | 0.5 | cd2b305fa890bca9c4374ccd83c9ccb24bf8dda3 | "[ERROR]: Uncaught panic!" when running the 100-line kernel example in the asterinas book.
When running the 100-line kernel example in the asterinas book [https://asterinas.github.io/book/framework/a-100-line-kernel.html ](url), the following error is reported:
```
Drive current: -outdev 'stdio:/root/workspace/asteri... | asterinas__asterinas-954 | 954 | diff --git a/docs/src/ostd/a-100-line-kernel.md b/docs/src/ostd/a-100-line-kernel.md
--- a/docs/src/ostd/a-100-line-kernel.md
+++ b/docs/src/ostd/a-100-line-kernel.md
@@ -7,23 +7,7 @@ we will show a new kernel in about 100 lines of safe Rust.
Our new kernel will be able to run the following Hello World program.
```... | It seems that the scheduler is not set. And the guide does not mention that.
```rust
use aster_frame::task::{set_scheduler, FifoScheduler, Scheduler};
let simple_scheduler = Box::new(FifoScheduler::new());
let static_scheduler: &'static dyn Scheduler = Box::leak(simple_scheduler);
set_scheduler(static_scheduler)... | 2024-06-20T08:52:42Z | cd2b305fa890bca9c4374ccd83c9ccb24bf8dda3 |
asterinas/asterinas | diff --git a/framework/aster-frame/src/mm/kspace.rs b/framework/aster-frame/src/mm/kspace.rs
--- a/framework/aster-frame/src/mm/kspace.rs
+++ b/framework/aster-frame/src/mm/kspace.rs
@@ -52,7 +55,10 @@ use super::{
page_table::{boot_pt::BootPageTable, KernelMode, PageTable},
MemoryRegionType, Paddr, PagingCon... | [
"906"
] | 0.4 | e210e68920481c911f62f03ade0a780f96e48e24 | [TDX BUG] The TDX SHARED bit can‘t be set in the page table during IOAPIC initialization.
In `framework/aster-frame/src/arch/x86/tdx_guest.rs`:
```rust
trap::init();
arch::after_all_init();
bus::init();
mm::kspace::init_kernel_page_table(boot_pt, meta_pages);
```
The kernel page table is init... | asterinas__asterinas-928 | 928 | diff --git a/framework/aster-frame/src/arch/x86/mm/mod.rs b/framework/aster-frame/src/arch/x86/mm/mod.rs
--- a/framework/aster-frame/src/arch/x86/mm/mod.rs
+++ b/framework/aster-frame/src/arch/x86/mm/mod.rs
@@ -161,13 +161,6 @@ impl PageTableEntryTrait for PageTableEntry {
let flags = PageTableFlags::PRESENT.b... | 2024-06-12T07:29:38Z | e210e68920481c911f62f03ade0a780f96e48e24 | |
asterinas/asterinas | diff --git a/regression/apps/Makefile b/regression/apps/Makefile
--- a/regression/apps/Makefile
+++ b/regression/apps/Makefile
@@ -10,6 +10,7 @@ REGRESSION_BUILD_DIR ?= $(INITRAMFS)/regression
# These test apps are sorted by name
TEST_APPS := \
+ alarm \
clone3 \
eventfd2 \
execve \
diff --git /dev/null b/reg... | [
"774",
"790"
] | 0.4 | 34e9d71fe4501bf4cac4d8263ccb568a814ac4b7 | Deliver POSIX signals for busy-loop user code
## Problem
Currently, the POSIX signals are handled in the main loop of user tasks, after `UserMode::execute` returns.
```rust
pub fn create_new_user_task(user_space: Arc<UserSpace>, thread_ref: Weak<Thread>) -> Arc<Task> {
fn user_task_entry() {
loop {... | asterinas__asterinas-782 | 782 | diff --git a/docs/src/framework/a-100-line-kernel.md b/docs/src/framework/a-100-line-kernel.md
--- a/docs/src/framework/a-100-line-kernel.md
+++ b/docs/src/framework/a-100-line-kernel.md
@@ -55,7 +55,7 @@ use alloc::vec;
use aster_frame::cpu::UserContext;
use aster_frame::prelude::*;
use aster_frame::task::{Task, Ta... | I made some modification in #782 to enable timely delivery of POSIX signals based on the solution you proposed. But as to this specific MRE that you mentioned,
```c
int main() {
// When the one second elapses, a SIGALRM will be triggered.
// The default behavior of a process when receiving SIGALRM
// i... | 2024-04-23T16:18:28Z | e210e68920481c911f62f03ade0a780f96e48e24 |
asterinas/asterinas | diff --git a/kernel/aster-nix/src/vm/vmar/options.rs b/kernel/aster-nix/src/vm/vmar/options.rs
--- a/kernel/aster-nix/src/vm/vmar/options.rs
+++ b/kernel/aster-nix/src/vm/vmar/options.rs
@@ -142,14 +142,14 @@ mod test {
use crate::vm::{
page_fault_handler::PageFaultHandler,
perms::VmPerms,
- ... | [
"666"
] | 0.4 | dede22843a99f6d19c8a2dddcfc7ef0ad45ce815 | [BUG] Uncaught panic happened in heap_allocator
I run 416.gamess , one of spec CPU 2006 test items, but a pacnic happened:
```
~ # ./gamess_base.amd64-m64-gcc41-nn < exam29.config
[ERROR]: Uncaught panic!
panicked at framework/aster-frame/src/vm/heap_allocator.rs:24:5:
Heap allocation error, layout = Layout { ... | asterinas__asterinas-679 | 679 | diff --git a/framework/aster-frame/src/arch/x86/boot/linux_boot/mod.rs b/framework/aster-frame/src/arch/x86/boot/linux_boot/mod.rs
--- a/framework/aster-frame/src/arch/x86/boot/linux_boot/mod.rs
+++ b/framework/aster-frame/src/arch/x86/boot/linux_boot/mod.rs
@@ -15,8 +15,7 @@ use crate::{
memory_region::{non_o... | We currently have only the ability to manage <4G of memory. And the default QEMU boot option gives a 2G memory. Maybe an allocation of 629MiB caused an OOM.
Related to #318
```rust
if segment_vmo_size > tail_padding_offset {
let buffer = vec![0u8; segment_vmo_size - tail_padding_offset];
segm... | 2024-03-13T06:03:51Z | e210e68920481c911f62f03ade0a780f96e48e24 |
asterinas/asterinas | diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -144,10 +144,14 @@ ktest: initramfs $(CARGO_OSDK)
(cd $$dir && cargo osdk test) || exit 1; \
done
-.PHONY: docs
-docs:
- @cargo doc # Build Rust docs
- @echo "" # Add a blank line
+docs: $(CARGO_OSDK)
+ @for dir in $(NON_OSDK_CRATES); ... | [
"657"
] | 0.4 | 132d36bf2082acafa14edf665e98463f681d6363 | [BUG] `cargo doc` reports error and fails
# Problem
`cargo doc` is used in `make docs` to generate API documentations. However, the command will fail currently. The problem seems to exist for a long time.
Before introducing OSDK, the `inventory` crate will report error. Since this crate is forked under Asterinas, w... | asterinas__asterinas-665 | 665 | diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -144,10 +144,14 @@ ktest: initramfs $(CARGO_OSDK)
(cd $$dir && cargo osdk test) || exit 1; \
done
-.PHONY: docs
-docs:
- @cargo doc # Build Rust docs
- @echo "" # Add a blank line
+docs: $(CARGO_OSDK)
+ @for dir in $(NON_OSDK_CRATES); ... | This will work.
```bash
cargo doc --target x86_64-unknown-none -Zbuild-std=core,alloc,compiler_builtins -Zbuild-std-features=compiler-builtins-mem
``` | 2024-03-06T09:10:55Z | e210e68920481c911f62f03ade0a780f96e48e24 |
asterinas/asterinas | diff --git a/regression/apps/network/send_buf_full.c b/regression/apps/network/send_buf_full.c
--- a/regression/apps/network/send_buf_full.c
+++ b/regression/apps/network/send_buf_full.c
@@ -197,6 +192,9 @@ int test_full_send_buffer(struct sockaddr_in *addr)
if (pid == 0) {
ssize_t recv_len;
+ close(sendfd);
+ ... | [
"646"
] | 0.4 | 07fbbcfd8c22459719c9af7eeeb3dee5ad24ba92 | The send_buf_full test fails on host linux
The test is run within Asterinas dev container.
To replay the results, commands are
```bash
make build
cd regression/build/initramfs/regression/network
./send_buf_full
```
I run `./send_buf_full` for four times, the results are
```
root@kx-2288H-V6:~/asterinas/reg... | asterinas__asterinas-650 | 650 | diff --git a/regression/apps/network/send_buf_full.c b/regression/apps/network/send_buf_full.c
--- a/regression/apps/network/send_buf_full.c
+++ b/regression/apps/network/send_buf_full.c
@@ -105,14 +105,9 @@ static ssize_t receive_all(int sockfd)
size_t recv_len = 0;
ssize_t ret;
- if (mark_filde_nonblock(sockfd)... | 2024-02-23T12:37:06Z | e210e68920481c911f62f03ade0a780f96e48e24 | |
asterinas/asterinas | diff --git a/Cargo.toml b/Cargo.toml
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -40,6 +40,7 @@ members = [
"framework/libs/linux-bzimage/setup",
"framework/libs/ktest",
"framework/libs/tdx-guest",
+ "services/aster-nix",
"services/comps/block",
"services/comps/console",
"services/comps/frameb... | [
"592"
] | 0.3 | 8d456ebe8fc200fc11c75654fdca2f0dd896e656 | Rename `aster-std` to `aster-nix`
# Background
In the current codebase, the Linux/UNIX layer is implemented in the `aster-std` crate under `services/libs`. The crate does the heavy-lifting job of implementing high-level OS concepts like processes, signals, file systems, sockets, etc. Ideally, we would like to have t... | asterinas__asterinas-637 | 637 | diff --git a/Cargo.lock b/Cargo.lock
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -221,37 +221,7 @@ dependencies = [
]
[[package]]
-name = "aster-rights"
-version = "0.1.0"
-dependencies = [
- "aster-rights-proc",
- "bitflags 1.3.2",
- "typeflags",
- "typeflags-util",
-]
-
-[[package]]
-name = "aster-rights-proc"
-version ... | 2024-02-05T08:00:55Z | 8d456ebe8fc200fc11c75654fdca2f0dd896e656 | |
asterinas/asterinas | diff --git a/regression/apps/scripts/network.sh b/regression/apps/scripts/network.sh
--- a/regression/apps/scripts/network.sh
+++ b/regression/apps/scripts/network.sh
@@ -18,7 +18,7 @@ echo "Start network test......"
./socketpair
./sockoption
./listen_backlog
-./send_buf_full
+# ./send_buf_full
echo "All networ... | [
"625"
] | 0.4 | b450eef1660c0362ba65de07a3bd03c8199c3265 | Support for in-kernel sleep
Currently sleep function we provide seems to be the only `pauser.pause_until_or_timeout()` for the POSIX threads from users, as in the `clock_nanosleep` syscall. However, some functionalities within kernel also need sleep like
https://github.com/asterinas/asterinas/blob/bd6f65667df494f6fb88... | asterinas__asterinas-630 | 630 | diff --git a/kernel/aster-nix/src/net/iface/common.rs b/kernel/aster-nix/src/net/iface/common.rs
--- a/kernel/aster-nix/src/net/iface/common.rs
+++ b/kernel/aster-nix/src/net/iface/common.rs
@@ -3,6 +3,7 @@
use alloc::collections::btree_map::Entry;
use core::sync::atomic::{AtomicU64, Ordering};
+use aster_frame::sy... | In-kernel sleep is supported. A kernel thread can sleep using the `WaitQueue` API provided by the Framework. `Pauser` is in fact based on `WaitQueue`.
In theory, the specific code snippet you show can and should be refactored using `WaitQueue` to avoid busy looping. But it is written that way. Why? My guess is that ... | 2024-01-29T03:53:41Z | e210e68920481c911f62f03ade0a780f96e48e24 |
asterinas/asterinas | diff --git /dev/null b/.github/workflows/license_check.yml
new file mode 100644
--- /dev/null
+++ b/.github/workflows/license_check.yml
@@ -0,0 +1,14 @@
+name: Check License
+on:
+ pull_request:
+ push:
+ branches:
+ - main
+jobs:
+ check-license-lines:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: a... | [
"555"
] | 0.3 | 5fb8a9f7e558977a8027eec32565a2de6b87636b | Add copyright and license info to the header of every file
Need to insert the copyright header to every source code file.
Here is the header for each Rust file.
```rust
// SPDX-License-Identifier: MPL-2.0
```
| asterinas__asterinas-567 | 567 | diff --git /dev/null b/.github/workflows/license_check.yml
new file mode 100644
--- /dev/null
+++ b/.github/workflows/license_check.yml
@@ -0,0 +1,14 @@
+name: Check License
+on:
+ pull_request:
+ push:
+ branches:
+ - main
+jobs:
+ check-license-lines:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: a... | As a side note, the MPL license is unfortunately hard-coded to allow implicit upgrades when the Mozilla Foundation releases a new license version. Not sure if we like that or not (or at least accept it).
> 10.2. Effect of New Versions
>
> You may distribute the Covered Software under the terms of the version
> o... | 2024-01-03T06:45:56Z | 8d456ebe8fc200fc11c75654fdca2f0dd896e656 |
asterinas/asterinas | diff --git a/.github/workflows/cargo_check.yml b/.github/workflows/cargo_check.yml
--- a/.github/workflows/cargo_check.yml
+++ b/.github/workflows/cargo_check.yml
@@ -10,9 +10,9 @@ jobs:
test:
runs-on: ubuntu-latest
timeout-minutes: 10
- container: jinuxdev/jinux:0.2.2
+ container: asterinas/asterina... | [
"551"
] | 0.2 | 6dbf5d560deafea0dcec228e4cb2d5e53c756174 | Rename the project name from Jinux to Asterinas
The project's official name will be Asterinas. The renaming process consists of the following steps:
1. The Github repo will be renamed to `asterinas` and moved to the `asterinas` Github org.
2. The DockerHub Image will be moved to `asterinas/asterinas`.
3. All occurr... | asterinas__asterinas-561 | 561 | diff --git a/.cargo/config.toml b/.cargo/config.toml
--- a/.cargo/config.toml
+++ b/.cargo/config.toml
@@ -1,6 +1,6 @@
[target.'cfg(target_os = "none")']
-runner = "cargo run --package jinux-runner --"
+runner = "cargo run --package aster-runner --"
[alias]
kcheck = "check --target x86_64-custom.json -Zbuild-std... | 2023-12-25T03:34:33Z | 6dbf5d560deafea0dcec228e4cb2d5e53c756174 | |
asterinas/asterinas | diff --git a/regression/syscall_test/blocklists/pty_test b/regression/syscall_test/blocklists/pty_test
--- a/regression/syscall_test/blocklists/pty_test
+++ b/regression/syscall_test/blocklists/pty_test
@@ -21,22 +21,8 @@ PtyTest.SwitchNoncanonToCanonNoNewlineBig
PtyTest.NoncanonBigWrite
PtyTest.SwitchNoncanonToCanon... | [
"254"
] | 0.2 | 576578baf4025686ae4c2893c2aafbc8d1e14722 | Implement session for shell job control
Process groups and sessions form a two-level hierarchical relationship between processes. A session is a collection of process groups. A process’s session membership is determined by its session identifier (SID). All of the processes in a session share a single controlling termin... | asterinas__asterinas-395 | 395 | diff --git a/regression/syscall_test/blocklists/pty_test b/regression/syscall_test/blocklists/pty_test
--- a/regression/syscall_test/blocklists/pty_test
+++ b/regression/syscall_test/blocklists/pty_test
@@ -21,22 +21,8 @@ PtyTest.SwitchNoncanonToCanonNoNewlineBig
PtyTest.NoncanonBigWrite
PtyTest.SwitchNoncanonToCanon... | 2023-08-30T11:25:32Z | 6dbf5d560deafea0dcec228e4cb2d5e53c756174 | |
asterinas/asterinas | diff --git /dev/null b/regression/apps/pty/Makefile
new file mode 100644
--- /dev/null
+++ b/regression/apps/pty/Makefile
@@ -0,0 +1,3 @@
+include ../test_common.mk
+
+EXTRA_C_FLAGS :=
diff --git a/regression/apps/scripts/run_tests.sh b/regression/apps/scripts/run_tests.sh
--- a/regression/apps/scripts/run_tests.sh
+++... | [
"214"
] | 0.1 | 25c4f0f2bcaa0bc8c650b0f4ee7b0d78e2a836b2 | Implement pseudo terminals
Maybe we need #209 for pty, since each pty will be a device under devfs.
| asterinas__asterinas-334 | 334 | diff --git a/regression/apps/Makefile b/regression/apps/Makefile
--- a/regression/apps/Makefile
+++ b/regression/apps/Makefile
@@ -3,7 +3,7 @@ MKFILE_PATH := $(abspath $(lastword $(MAKEFILE_LIST)))
CUR_DIR := $(patsubst %/,%,$(dir $(MKFILE_PATH)))
INITRAMFS ?= $(CUR_DIR)/../build/initramfs
REGRESSION_BUILD_DIR ?= $(... | 2023-08-01T06:37:18Z | 25c4f0f2bcaa0bc8c650b0f4ee7b0d78e2a836b2 | |
asterinas/asterinas | diff --git a/regression/syscall_test/Makefile b/regression/syscall_test/Makefile
--- a/regression/syscall_test/Makefile
+++ b/regression/syscall_test/Makefile
@@ -2,9 +2,13 @@ TESTS ?= open_test read_test statfs_test chmod_test
MKFILE_PATH := $(abspath $(lastword $(MAKEFILE_LIST)))
CUR_DIR := $(patsubst %/,%,$(dir ... | [
"340"
] | 0.1 | dbfb2e1a62a9981a67cc01ff7310981744ec2ac5 | Precompile syscall tests in the dev docker image to accelerate CI
Currently the syscall tests are compiled every-time when CI triggers, which is at a cost of around 12 minutes on Github runners.
| asterinas__asterinas-327 | 327 | diff --git a/regression/syscall_test/Makefile b/regression/syscall_test/Makefile
--- a/regression/syscall_test/Makefile
+++ b/regression/syscall_test/Makefile
@@ -2,9 +2,13 @@ TESTS ?= open_test read_test statfs_test chmod_test
MKFILE_PATH := $(abspath $(lastword $(MAKEFILE_LIST)))
CUR_DIR := $(patsubst %/,%,$(dir ... | 2023-07-27T07:11:21Z | 25c4f0f2bcaa0bc8c650b0f4ee7b0d78e2a836b2 | |
asterinas/asterinas | diff --git /dev/null b/services/libs/keyable-arc/src/lib.rs
new file mode 100644
--- /dev/null
+++ b/services/libs/keyable-arc/src/lib.rs
@@ -0,0 +1,362 @@
+//! Same as the standard `Arc`, except that it can be used as the key type of a hash table.
+//!
+//! # Motivation
+//!
+//! A type `K` is _keyable_ if it can be u... | [
"124"
] | 0.1 | 7e1584fca9b0bb818ea8f115ab471bc21613b7bd | Implement the epoll system call
| asterinas__asterinas-193 | 193 | diff --git a/Cargo.lock b/Cargo.lock
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -145,6 +145,15 @@ dependencies = [
name = "cpio-decoder"
version = "0.1.0"
+[[package]]
+name = "crossbeam-utils"
+version = "0.8.15"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "3c063cd8cc95f5c377ed0d4b49a4b... | 2023-04-20T03:46:19Z | 25c4f0f2bcaa0bc8c650b0f4ee7b0d78e2a836b2 | |
asterinas/asterinas | diff --git a/.gitattributes b/.gitattributes
--- a/.gitattributes
+++ b/.gitattributes
@@ -1,10 +1,10 @@
-src/apps/hello_world/hello_world filter=lfs diff=lfs merge=lfs -text
-src/apps/fork/fork filter=lfs diff=lfs merge=lfs -text
-src/apps/hello_c/hello filter=lfs diff=lfs merge=lfs -text
-src/apps/execve/execve filte... | [
"115"
] | null | 888853a6de752e97c6f94fff83c00594be42929f | Reorganize the codebase for cleanness
To make the codebase more clean and understandable, I propose to do the following changes:
* Rename `tests` to `test`, which indicates that the directory contains various types of testing code, including unit tests, user programs, and possibly LTP tests
* Rename `apps` to `te... | asterinas__asterinas-183 | 183 | diff --git a/.gitattributes b/.gitattributes
--- a/.gitattributes
+++ b/.gitattributes
@@ -1,10 +1,10 @@
-src/apps/hello_world/hello_world filter=lfs diff=lfs merge=lfs -text
-src/apps/fork/fork filter=lfs diff=lfs merge=lfs -text
-src/apps/hello_c/hello filter=lfs diff=lfs merge=lfs -text
-src/apps/execve/execve filte... | 2023-04-10T03:22:03Z | 888853a6de752e97c6f94fff83c00594be42929f |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.