From: Richard Weinberger <richard@nod.at>
To: torvalds <torvalds@linux-foundation.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] JFFS2 changes for v6.10-rc1
Date: Fri, 24 May 2024 23:26:17 +0200 (CEST) [thread overview]
Message-ID: <1964508139.144819.1716585977753.JavaMail.zimbra@nod.at> (raw)
Linus,
The following changes since commit e67572cd2204894179d89bd7b984072f19313b03:
Linux 6.9-rc6 (2024-04-28 13:47:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git tags/jffs2-for-linus-6.10-rc1
for you to fetch changes up to af9a8730ddb6a4b2edd779ccc0aceb994d616830:
jffs2: Fix potential illegal address access in jffs2_free_inode (2024-05-12 22:57:04 +0200)
----------------------------------------------------------------
This pull request contains the following changes for JFFS2:
- Fix Illegal memory access jffs2_free_inode()
- Kernel-doc fixes
- Print symbolic error names
----------------------------------------------------------------
Christian Heusel (1):
jffs2: print symbolic error name instead of error code
Kunwu Chan (1):
jffs2: Simplify the allocation of slab caches
Randy Dunlap (1):
jffs2: nodemgmt: fix kernel-doc comments
Wang Yong (1):
jffs2: Fix potential illegal address access in jffs2_free_inode
fs/jffs2/background.c | 4 ++--
fs/jffs2/malloc.c | 32 ++++++++------------------------
fs/jffs2/nodemgmt.c | 24 +++++++++++++++---------
fs/jffs2/super.c | 1 +
4 files changed, 26 insertions(+), 35 deletions(-)
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2024-05-24 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 21:26 Richard Weinberger [this message]
2024-05-25 21:08 ` [GIT PULL] JFFS2 changes for v6.10-rc1 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=1964508139.144819.1716585977753.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox