From: Mike Marshall <hubcap@omnibond.com>
To: Linus Torvalds <linus971@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Mike Marshall <hubcap@omnibond.com>
Subject: [GIT PULL] orangefs: fix out-of-bounds fsid access
Date: Tue, 14 May 2024 09:10:50 -0400 [thread overview]
Message-ID: <CAOg9mSQBdCRjQYkPEdFFX0Hd43atzOsVALrxa=2NRSGjvkw9Xw@mail.gmail.com> (raw)
The following changes since commit dd5a440a31fae6e459c0d6271dddd62825505361:
Linux 6.9-rc7 (2024-05-05 14:06:01 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git
tags/for-linus-6.10-ofs1
for you to fetch changes up to 53e4efa470d5fc6a96662d2d3322cfc925818517:
orangefs: fix out-of-bounds fsid access (2024-05-06 10:10:36 -0400)
----------------------------------------------------------------
orangefs: fix out-of-bounds fsid access
Small fix to quiet warnings from string fortification helpers,
suggested by Arnd Bergmann.
----------------------------------------------------------------
Mike Marshall (1):
orangefs: fix out-of-bounds fsid access
fs/orangefs/super.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
reply other threads:[~2024-05-14 13:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAOg9mSQBdCRjQYkPEdFFX0Hd43atzOsVALrxa=2NRSGjvkw9Xw@mail.gmail.com' \
--to=hubcap@omnibond.com \
--cc=linus971@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).