linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Christian Brauner <christian@brauner.io>
Cc: David Howells <dhowells@redhat.com>,
	Markus Suvanto <markus.suvanto@gmail.com>,
	Marc Dionne <marc.dionne@auristor.com>,
	Daniil Dulov <d.dulov@aladdin.ru>,
	linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] afs: Miscellaneous fixes
Date: Mon, 19 Feb 2024 14:39:01 +0000	[thread overview]
Message-ID: <20240219143906.138346-1-dhowells@redhat.com> (raw)

Hi Christian,

Here are some fixes for afs, if you could take them?

 (1) Fix searching for the AFS fileserver record for an incoming callback
     in a mixed IPv4/IPv6 environment.

 (2) Fix the size of a buffer in afs_update_volume_status() to avoid
     overrunning it and use snprintf() as well.

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

Daniil Dulov (1):
  afs: Increase buffer size in afs_update_volume_status()

Marc Dionne (1):
  afs: Fix ignored callbacks over ipv4

 fs/afs/internal.h |  6 ++----
 fs/afs/main.c     |  3 +--
 fs/afs/server.c   | 14 +++++---------
 fs/afs/volume.c   |  4 ++--
 4 files changed, 10 insertions(+), 17 deletions(-)


             reply	other threads:[~2024-02-19 14:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 14:39 David Howells [this message]
2024-02-19 14:39 ` [PATCH 1/2] afs: Fix ignored callbacks over ipv4 David Howells
2024-02-19 16:52   ` Matthew Wilcox
2024-02-19 14:39 ` [PATCH 2/2] afs: Increase buffer size in afs_update_volume_status() David Howells
2024-02-19 16:54   ` Matthew Wilcox
2024-02-20  8:51 ` [PATCH 0/2] afs: Miscellaneous fixes Christian Brauner
  -- strict thread matches above, loose matches on Subject: below --
2024-03-13  8:15 David Howells
2024-03-13 12:55 ` Marc Dionne
2024-03-14 11:13 ` Christian Brauner

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=20240219143906.138346-1-dhowells@redhat.com \
    --to=dhowells@redhat.com \
    --cc=christian@brauner.io \
    --cc=d.dulov@aladdin.ru \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --cc=markus.suvanto@gmail.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).