Skip to content
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

Setup CI for nix-based kernel build #4

Open
2 tasks done
rvolosatovs opened this issue Nov 21, 2022 · 0 comments
Open
2 tasks done

Setup CI for nix-based kernel build #4

rvolosatovs opened this issue Nov 21, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@rvolosatovs
Copy link
Member

rvolosatovs commented Nov 21, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Code of Conduct

  • I agree to follow this project's Code of Conduct

Current Behaviour

No such CI

Expected Behaviour

Build the nix flake. Maybe also upload the config and kernel as artifacts?

This should be mostly copy-pasting from https://github.com/profianinc/nixpkgs/blob/b79f2c25c15ba9259138d855b4353bb9493c8c57/.github/workflows/build.yml

@rvolosatovs rvolosatovs added the bug Something isn't working label Nov 21, 2022
@rvolosatovs rvolosatovs changed the title [Bug]: Setup CI for nix-based kernel build Setup CI for nix-based kernel build Nov 21, 2022
@rvolosatovs rvolosatovs self-assigned this Nov 21, 2022
@dpal dpal added this to Enarx Board Nov 22, 2022
@dpal dpal moved this to New in Enarx Board Nov 22, 2022
@dpal dpal moved this from New to Scheduled in Enarx Board Nov 23, 2022
jarkkojs pushed a commit that referenced this issue Nov 28, 2022
xfstests generic/013 and generic/476 reported WARNING as follows:

  WARNING: lock held when returning to user space!
  6.1.0-rc5+ #4 Not tainted
  ------------------------------------------------
  fsstress/504233 is leaving the kernel with locks still held!
  2 locks held by fsstress/504233:
   #0: ffff888054c38850 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at:
                        lock_two_nondirectories+0xcf/0xf0
   #1: ffff8880b8fec750 (&sb->s_type->i_mutex_key#21/4){+.+.}-{3:3}, at:
                        lock_two_nondirectories+0xb7/0xf0

This will lead to deadlock and hungtask.

Fix this by releasing locks when failed to write out on a file range in
cifs_file_copychunk_range().

Fixes: 3e3761f ("smb3: use filemap_write_and_wait_range instead of filemap_write_and_wait")
Cc: [email protected] # 6.0
Reviewed-by: Paulo Alcantara (SUSE) <[email protected]>
Signed-off-by: ChenXiaoSong <[email protected]>
Signed-off-by: Steve French <[email protected]>
@dpal dpal moved this from Scheduled (this sprint) to Standby (next sprint) in Enarx Board Jan 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Standby (next sprint)
Development

No branches or pull requests

1 participant