Bug 218359 - [LTP & bisect] There is add_key with type "add_key" syscall failed in v6.7-rc8 kernel on a bare metal platform
Summary: [LTP & bisect] There is add_key with type "add_key" syscall failed in v6.7-rc...
Status: NEW
Alias: None
Product: Other
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: Bug Me Administrator
Depends on:
Reported: 2024-01-10 04:39 UTC by xupengfe
Modified: 2024-03-22 07:51 UTC (History)
0 users

See Also:
Kernel Version:
Regression: No
Bisected commit-id:


Description xupengfe 2024-01-10 04:39:14 UTC
Related link: https://lore.kernel.org/all/2592945.1703376169@warthog.procyon.org.uk/

 Above patch (upstream commit: 1997b3cb4217b09) seems causing a keyctl05 case
to fail in LTP:

  Bisected info between v6.7-rc7(keyctl05 passed) and v6.7-rc8(keyctl05 failed)
is in attached.

keyctl05 failed in add_key with type "dns_resolver" type syscall step tracked
by strace:
[pid 863107] add_key("dns_resolver", "desc", "\0\0\1\377\0", 5, KEY_SPEC_SESSION_KEYRING <unfinished ...>
[pid 863106] <... alarm resumed>)       = 30
[pid 863107] <... add_key resumed>)     = -1 EINVAL (Invalid argument)

Normal behavior in v6.7-rc7 kernel:
[pid  6726] add_key("dns_resolver", "desc", "\0\0\1\377\0", 5, KEY_SPEC_SESSION_KEYRING <unfinished ...>
[pid  6725] rt_sigreturn({mask=[]})     = 61
[pid  6726] <... add_key resumed>)      = 1029222644

Do you mind to take a look for this issue?


Note You need to log in before you can comment on or make changes to this bug.