All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [GIT PULL] fscrypt fix for 6.8-rc1
Date: Sat, 13 Jan 2024 09:56:04 -0800	[thread overview]
Message-ID: <20240113175604.GA1409@sol.localdomain> (raw)

The following changes since commit 38814330fedd778edffcabe0c8cb462ee365782e:

  Merge tag 'devicetree-for-6.8' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux (2024-01-12 15:05:30 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/fs/fscrypt/linux.git tags/fscrypt-for-linus

for you to fetch changes up to c919330dd57835970b37676d377de3eaaea2c1e9:

  f2fs: fix double free of f2fs_sb_info (2024-01-12 18:55:09 -0800)

----------------------------------------------------------------

Fix a bug in my change to how f2fs frees its superblock info (which was
part of changing the timing of fscrypt keyring destruction).

----------------------------------------------------------------
Eric Biggers (1):
      f2fs: fix double free of f2fs_sb_info

 fs/f2fs/super.c | 1 +
 1 file changed, 1 insertion(+)



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
	Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
	linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] fscrypt fix for 6.8-rc1
Date: Sat, 13 Jan 2024 09:56:04 -0800	[thread overview]
Message-ID: <20240113175604.GA1409@sol.localdomain> (raw)

The following changes since commit 38814330fedd778edffcabe0c8cb462ee365782e:

  Merge tag 'devicetree-for-6.8' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux (2024-01-12 15:05:30 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/fs/fscrypt/linux.git tags/fscrypt-for-linus

for you to fetch changes up to c919330dd57835970b37676d377de3eaaea2c1e9:

  f2fs: fix double free of f2fs_sb_info (2024-01-12 18:55:09 -0800)

----------------------------------------------------------------

Fix a bug in my change to how f2fs frees its superblock info (which was
part of changing the timing of fscrypt keyring destruction).

----------------------------------------------------------------
Eric Biggers (1):
      f2fs: fix double free of f2fs_sb_info

 fs/f2fs/super.c | 1 +
 1 file changed, 1 insertion(+)


             reply	other threads:[~2024-01-13 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13 17:56 Eric Biggers [this message]
2024-01-13 17:56 ` [GIT PULL] fscrypt fix for 6.8-rc1 Eric Biggers
2024-01-17 20:03 ` pr-tracker-bot
2024-01-17 20:03   ` [f2fs-dev] " 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=20240113175604.GA1409@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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.