All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
	gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] gfs2 fix
Date: Mon, 25 Mar 2024 13:10:16 +0100	[thread overview]
Message-ID: <20240325121020.337540-1-agruenba@redhat.com> (raw)

Hello Linus,

please consider pulling the following gfs2 fix.

Thank you very much,
Andreas

The following changes since commit e8f897f4afef0031fe618a8e94127a0934896aba:

  Linux 6.8 (2024-03-10 13:38:09 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v6.8-fix

for you to fetch changes up to c95346ac918c5badf51b9a7ac58a26d3bd5bb224:

  gfs2: Fix invalid metadata access in punch_hole (2024-03-11 17:11:18 +0100)

----------------------------------------------------------------
gfs2 fix

- Fix boundary check in punch_hole

----------------------------------------------------------------
Andrew Price (1):
      gfs2: Fix invalid metadata access in punch_hole

 fs/gfs2/bmap.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)


             reply	other threads:[~2024-03-25 12:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 12:10 Andreas Gruenbacher [this message]
2024-03-25 18:18 ` [GIT PULL] gfs2 fix pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-06-06 12:48 Andreas Gruenbacher
2023-06-06 12:55 ` Linus Torvalds
2023-06-06 13:32   ` Andreas Gruenbacher
2023-06-06 13:22 ` pr-tracker-bot
2022-04-26 14:54 Andreas Gruenbacher
2022-04-26 18:31 ` Linus Torvalds
2022-04-26 21:27   ` Andreas Gruenbacher
2022-04-26 23:33     ` Linus Torvalds
2022-04-27 12:29       ` Andreas Gruenbacher
2022-04-27 17:13         ` Linus Torvalds
2022-04-27 19:41           ` Andreas Gruenbacher
2022-04-27 20:25             ` Linus Torvalds
2022-04-27 21:26               ` Andreas Gruenbacher
2022-04-27 22:20                 ` Linus Torvalds
2022-04-28  0:00                   ` Linus Torvalds
2022-04-28 13:26                     ` Andreas Gruenbacher
2022-04-28 17:09                       ` Linus Torvalds
2022-04-28 17:17                         ` Linus Torvalds
2022-04-28 17:21                           ` Andreas Gruenbacher
2022-04-28 17:38                         ` Andreas Gruenbacher
2022-05-02 18:31                           ` Linus Torvalds
2022-05-02 18:58                             ` Linus Torvalds
2022-05-02 20:24                               ` Andreas Gruenbacher
2022-05-03  8:56                             ` Andreas Gruenbacher
2022-05-03 13:30                               ` Andreas Gruenbacher
2022-05-03 16:19                               ` Linus Torvalds
2022-05-03 16:41                                 ` Andreas Gruenbacher
2022-05-03 16:50                                   ` Linus Torvalds
2022-05-03 21:35                               ` Andreas Gruenbacher
2022-05-03 22:41                                 ` Linus Torvalds
2022-05-04 17:52                                   ` Andreas Gruenbacher
2022-04-26 19:07 ` pr-tracker-bot

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=20240325121020.337540-1-agruenba@redhat.com \
    --to=agruenba@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.