From: markus.suvanto@gmail.com
To: David Howells <dhowells@redhat.com>,
Marc Dionne <marc.dionne@auristor.com>
Cc: linux-afs@lists.infradead.org, keyrings@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] afs: Fix dynamic root interaction with failing DNS lookups
Date: Tue, 12 Dec 2023 21:53:48 +0200 [thread overview]
Message-ID: <e98a26355533de0beb463464c73fb8781ab089bb.camel@gmail.com> (raw)
In-Reply-To: <20231212144611.3100234-1-dhowells@redhat.com>
ti, 2023-12-12 kello 14:46 +0000, David Howells kirjoitti:
> Hi Markus, Marc,
>
> Here's a set of fixes to improve the interaction of arbitrary lookups in
> the AFS dynamic root that hit DNS lookup failures[1]:
>
> (1) Always delete unused (particularly negative) dentries as soon as
> possible so that they don't prevent future lookups from retrying.
>
> (2) Fix the handling of new-style negative DNS lookups in ->lookup() to
> make them return ENOENT so that userspace doesn't get confused when
> stat succeeds but the following open on the looked up file then fails.
>
> (3) Fix key handling so that DNS lookup results are reclaimed as soon as
> they expire rather than sitting round either forever or for an
> additional 5 mins beyond a set expiry time returning EKEYEXPIRED.
>
> The patches can be found here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=afs-fixes
>
> Thanks,
> David
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=216637 [1]
> Link: https://lore.kernel.org/r/20231211163412.2766147-1-dhowells@redhat.com # v1
> Link: https://lore.kernel.org/r/20231211213233.2793525-1-dhowells@redhat.com # v2
>
> Changes
> =======
> ver #3)
> - Rebased to v6.7-rc5 which has an additional afs patch.
> - Don't add to TIME64_MAX (ie. permanent) when checking expiry time.
>
> ver #2)
> - Fix signed-unsigned comparison when checking return val.
>
> David Howells (3):
> afs: Fix the dynamic root's d_delete to always delete unused dentries
> afs: Fix dynamic root lookup DNS check
> keys, dns: Allow key types (eg. DNS) to be reclaimed immediately on
> expiry
>
> fs/afs/dynroot.c | 31 +++++++++++++++++--------------
> include/linux/key-type.h | 1 +
> net/dns_resolver/dns_key.c | 10 +++++++++-
> security/keys/gc.c | 31 +++++++++++++++++++++----------
> security/keys/internal.h | 11 ++++++++++-
> security/keys/key.c | 15 +++++----------
> security/keys/proc.c | 2 +-
> 7 files changed, 64 insertions(+), 37 deletions(-)
>
masu@t470 ~ % uname -r
6.7.0-rc5-gb946001d3bb1
This fixes my problem :) https://bugzilla.kernel.org/show_bug.cgi?id=216637
Tested-by: Markus Suvanto <markus.suvanto@gmail.com>
-Markus
prev parent reply other threads:[~2023-12-12 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 14:46 [PATCH v3 0/3] afs: Fix dynamic root interaction with failing DNS lookups David Howells
2023-12-12 14:46 ` [PATCH v3 1/3] afs: Fix the dynamic root's d_delete to always delete unused dentries David Howells
2023-12-12 14:46 ` [PATCH v3 2/3] afs: Fix dynamic root lookup DNS check David Howells
2023-12-12 14:46 ` [PATCH v3 3/3] keys, dns: Allow key types (eg. DNS) to be reclaimed immediately on expiry David Howells
2023-12-20 13:35 ` Jeffrey E Altman
2023-12-12 19:53 ` markus.suvanto [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e98a26355533de0beb463464c73fb8781ab089bb.camel@gmail.com \
--to=markus.suvanto@gmail.com \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).