From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 0/4] ext4 fixes
Date: Tue, 29 Oct 2019 10:10:25 +0100 [thread overview]
Message-ID: <20191029091029.22215-1-s.hauer@pengutronix.de> (raw)
This series fixes some issues with the ext4 code regarding to sparse
files.
Sascha
Sascha Hauer (4):
fs: ext4: Fix out of bounds memset
fs: ext4: remove unnecessarily clever file read
fs: ext4: Fix handling of sparse files
fs: ext4: return NULL instead of 0
fs/ext4/ext4_common.c | 32 +++++++++++------------
fs/ext4/ext4fs.c | 61 +++++--------------------------------------
2 files changed, 23 insertions(+), 70 deletions(-)
--
2.24.0.rc1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2019-10-29 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 9:10 Sascha Hauer [this message]
2019-10-29 9:10 ` [PATCH 1/4] fs: ext4: Fix out of bounds memset Sascha Hauer
2019-10-29 9:10 ` [PATCH 2/4] fs: ext4: remove unnecessarily clever file read Sascha Hauer
2019-10-29 9:10 ` [PATCH 3/4] fs: ext4: Fix handling of sparse files Sascha Hauer
2019-10-29 9:10 ` [PATCH 4/4] fs: ext4: return NULL instead of 0 Sascha Hauer
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=20191029091029.22215-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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