lp:~timg-tpi/ubuntu/+source/linux-azure/+git/jammy

Owned by Tim Gardner
Get this repository:
git clone https://git.launchpad.net/~timg-tpi/ubuntu/+source/linux-azure/+git/jammy
Only Tim Gardner can upload to this repository. If you are Tim Gardner please log in for upload directions.

Branches

Name Last Modified Last Commit
azure-6.5-next-2024.03.04 2024-03-20 16:54:04 UTC
UBUNTU: Ubuntu-azure-6.5-6.5.0-1018.19~22.04.1

Author: Tim Gardner
Author Date: 2024-03-20 16:54:04 UTC

UBUNTU: Ubuntu-azure-6.5-6.5.0-1018.19~22.04.1

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

jammy-azure-6.2-fde-lp2017571 2023-05-03 13:57:20 UTC
UBUNTU: Ubuntu-azure-6.2-6.2.0-1004.4~22.04.2

Author: Tim Gardner
Author Date: 2023-05-03 13:57:20 UTC

UBUNTU: Ubuntu-azure-6.2-6.2.0-1004.4~22.04.2

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

master-next 2023-04-03 16:58:46 UTC
keys: Do not cache key in task struct if key is requested from kernel thread

Author: David Howells
Author Date: 2023-03-30 18:27:10 UTC

keys: Do not cache key in task struct if key is requested from kernel thread

BugLink: https://bugs.launchpad.net/bugs/2013349

The key which gets cached in task structure from a kernel thread does not
get invalidated even after expiry. Due to which, a new key request from
kernel thread will be served with the cached key if it's present in task
struct irrespective of the key validity. The change is to not cache key in
task_struct when key requested from kernel thread so that kernel thread
gets a valid key on every key request.

The problem has been seen with the cifs module doing DNS lookups from a
kernel thread and the results getting pinned by being attached to that
kernel thread's cache - and thus not something that can be easily got rid
of. The cache would ordinarily be cleared by notify-resume, but kernel
threads don't do that.

This isn't seen with AFS because AFS is doing request_key() within the
kernel half of a user thread - which will do notify-resume.

Fixes: 7743c48e54ee ("keys: Cache result of request_key*() temporarily in task_struct")
Signed-off-by: Bharath SM <bharathsm@microsoft.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
cc: Shyam Prasad N <nspmangalore@gmail.com>
cc: Steve French <smfrench@gmail.com>
cc: keyrings@vger.kernel.org
cc: linux-cifs@vger.kernel.org
cc: linux-fsdevel@vger.kernel.org
Link: https://lore.kernel.org/r/CAGypqWw951d=zYRbdgNR4snUDvJhWL=q3=WOyh7HhSJupjz2vA@mail.gmail.com/
(cherry picked from commit 47f9e4c924025c5be87959d3335e66fcbb7f6b5c)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
Acked-by: Philip Cox <philip.cox@canonical.com>
Acked-by: Andrei Gherzan <andrei.gherzan@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

azure-fde-5.19 2023-03-29 17:52:29 UTC
UBUNTU: Ubuntu-azure-fde-5.19-5.19.0-1023.24~22.04.1.1

Author: Tim Gardner
Author Date: 2023-03-29 17:52:29 UTC

UBUNTU: Ubuntu-azure-fde-5.19-5.19.0-1023.24~22.04.1.1

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

azure-fde 2023-03-29 17:37:35 UTC
UBUNTU: Ubuntu-azure-fde-5.15.0-1036.43.1

Author: Tim Gardner
Author Date: 2023-03-29 17:37:35 UTC

UBUNTU: Ubuntu-azure-fde-5.15.0-1036.43.1

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

azure-5.19-next 2023-03-29 16:36:33 UTC
UBUNTU: Ubuntu-azure-5.19-5.19.0-1023.24~22.04.1

Author: Tim Gardner
Author Date: 2023-03-29 16:36:33 UTC

UBUNTU: Ubuntu-azure-5.19-5.19.0-1023.24~22.04.1

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

azure-6.2-next 2023-03-28 14:44:09 UTC
UBUNTU: Ubuntu-azure-6.2-6.2.0-1002.2~22.04.1

Author: Tim Gardner
Author Date: 2023-03-28 14:44:09 UTC

UBUNTU: Ubuntu-azure-6.2-6.2.0-1002.2~22.04.1

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

master 2022-10-13 16:51:12 UTC
UBUNTU: Ubuntu-azure-5.15.0-1022.27

Author: Kleber Sacilotto de Souza
Author Date: 2022-10-13 16:51:12 UTC

UBUNTU: Ubuntu-azure-5.15.0-1022.27

Signed-off-by: Kleber Sacilotto de Souza <kleber.souza@canonical.com>

18 of 8 results
This repository contains Public information 
Everyone can see this information.

Subscribers