[LU-16351] Linux 6.1 client support Created: 29/Nov/22  Updated: 16/Jul/23  Resolved: 07/Jul/23

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Shaun Tancheff Assignee: Shaun Tancheff
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

Upstream changes affect Lustre client support:

Linux commit v4.10-rc3-6-gc440408cf690
random: convert get_random_int/long into get_random_u32/u64
Linux commit v6.0-11338-gde492c83cae0
prandom: remove unused functions

In effect prandom_u32 is a wrapper around get_random_u32, so change users of prandom_u32 to get_random_u32 and provide a fallback to prandom_u32 when get_random_u32 is not available.

Linux commit v6.0-rc1-2-g25885a35a720
Change calling conventions for filldir_t
Add a test for the new filldir_t signature and fix the current filldir_t usage

Linux commit v6.0-rc3-94-g35b471467f88
filemap: add filemap_get_folios_contig()
Provide a wrapper and fallback to find_get_pages_contig when filemap_get_folios_contig is not available.

Linux commit v6.0-rc3-225-gf39af05949a4
mm: add VMA iterator
Use vma_iterator and for_each_vma when available.

 Comments   
Comment by Xinliang Liu [ 21/Mar/23 ]

Any update on this?

Comment by Shaun Tancheff [ 21/Mar/23 ]

Looks like gerrit did not add the link:

https://review.whamcloud.com/c/fs/lustre-release/+/49232/

Comment by Xinliang Liu [ 21/Mar/23 ]

Great! Thanks  stancheff  very much for the patch. Looking forward to the landing. Maybe a rebase is needed to fix the merge conflict.

Comment by Shaun Tancheff [ 21/Mar/23 ]

It depends on
LU-16328 llite: Linux 6.0 migrate_folio, vfs_setxattr:
https://review.whamcloud.com/c/fs/lustre-release/+/49265
and
LU-16327 llite: read_folio, release_folio, filler_t
https://review.whamcloud.com/c/fs/lustre-release/+/49199

It can be rebased to exclude
LU-16350 osd-ldiskfs: no_llseek removed, dquot_transfer
https://review.whamcloud.com/c/fs/lustre-release/+/49266
which is only in the series due to the conflicting changes in lustre/autoconf/lustre-core.m4

Comment by Xinliang Liu [ 21/Mar/23 ]

Oh, I see. Thanks for the info and update.

Comment by Xinliang Liu [ 24/Mar/23 ]

Verified the above patches on Arm64 kernel 6.1.

[openeuler@oe-mainline-test lustre-release]$ sudo mount -t lustre 192.168.1.203@tcp:/lustre /mnt/lustre
[openeuler@oe-mainline-test lustre-release]$ lfs df -h
UUID                       bytes        Used   Available Use% Mounted on
lustre-MDT0000_UUID       122.1M        1.6M      109.5M   2% /mnt/lustre[MDT:0]
lustre-OST0000_UUID       305.8M        1.2M      278.0M   1% /mnt/lustre[OST:0]
lustre-OST0001_UUID       305.8M        1.2M      278.0M   1% /mnt/lustre[OST:1]
filesystem_summary:       611.5M        2.4M      556.0M   1% /mnt/lustre
[openeuler@oe-mainline-test lustre-release]$ uname -r
6.1.8-3.0.0.7.oe1.aarch64

BTW, I met another configure issue: LU-16662

Comment by Gerrit Updater [ 01/May/23 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/49232/
Subject: LU-16351 llite: Linux 6.1 prandom, folios_contig, vma_iterator
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: ca992899d55fd13e65b75ace02931daaa29c18bd

Comment by Peter Jones [ 01/May/23 ]

is there more to come under this ticket?

Comment by Peter Jones [ 07/Jul/23 ]

Seems like other work being tracked under different tickets so marking as resolved for 2.16

Generated at Sat Feb 10 03:26:16 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.