public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey E Altman <jaltman@auristor.com>
To: David Howells <dhowells@redhat.com>,
	Marc Dionne <marc.dionne@auristor.com>
Cc: linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] afs: Miscellaneous small fixes
Date: Wed, 22 Nov 2023 13:58:51 -0500	[thread overview]
Message-ID: <931bf2cd-2690-4a2d-a34f-a49fbe696364@auristor.com> (raw)
In-Reply-To: <20231116155312.156593-1-dhowells@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

On 11/16/2023 10:53 AM, David Howells wrote:
> Hi Marc,
>
> Here are a set of miscellaneous small fixes to the afs filesystem
> including:
>
>   (1) Fix the afs_server_list struct to be cleaned up with RCU.
>
>   (2) Fix afs to translate a no-data result from a DNS lookup into ENOENT,
>       not EDESTADDRREQ for consistency with OpenAFS.
>
>   (3) Fix afs to translate a negative DNS lookup result into ENOENT rather
>       than EDESTADDRREQ.
>
>   (4) Fix file locking on R/O volumes to operate in local mode as the server
>       doesn't handle exclusive locks on such files.
>
>   (5) Not a fix per se, but set SB_RDONLY on superblocks for RO and Backup
>       volumes so that the VFS can see that they're read only.
>
> 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
>
> David Howells (5):
>    afs: Fix afs_server_list to be cleaned up with RCU
>    afs: Make error on cell lookup failure consistent with OpenAFS
>    afs: Return ENOENT if no cell DNS record can be found
>    afs: Fix file locking on R/O volumes to operate in local mode
>    afs: Mark a superblock for an R/O or Backup volume as SB_RDONLY
>
>   fs/afs/dynroot.c     |  4 ++--
>   fs/afs/internal.h    |  1 +
>   fs/afs/server_list.c |  2 +-
>   fs/afs/super.c       |  4 ++++
>   fs/afs/vl_rotate.c   | 10 ++++++++++
>   5 files changed, 18 insertions(+), 3 deletions(-)

Reviewed-by: Jeffrey Altman <jaltman@auristor.com>


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4039 bytes --]

      parent reply	other threads:[~2023-11-22 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 15:53 [PATCH 0/5] afs: Miscellaneous small fixes David Howells
2023-11-16 15:53 ` [PATCH 1/5] afs: Fix afs_server_list to be cleaned up with RCU David Howells
2023-11-17 15:57   ` Marc Dionne
2023-11-16 15:53 ` [PATCH 2/5] afs: Make error on cell lookup failure consistent with OpenAFS David Howells
2023-11-17 16:30   ` Marc Dionne
2023-11-16 15:53 ` [PATCH 3/5] afs: Return ENOENT if no cell DNS record can be found David Howells
2023-11-22 19:04   ` Marc Dionne
2023-11-16 15:53 ` [PATCH 4/5] afs: Fix file locking on R/O volumes to operate in local mode David Howells
2023-11-22 19:05   ` Marc Dionne
2023-11-16 15:53 ` [PATCH 5/5] afs: Mark a superblock for an R/O or Backup volume as SB_RDONLY David Howells
2023-11-17 15:56   ` Marc Dionne
2023-11-22 18:58 ` Jeffrey E Altman [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=931bf2cd-2690-4a2d-a34f-a49fbe696364@auristor.com \
    --to=jaltman@auristor.com \
    --cc=dhowells@redhat.com \
    --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