From: Jan Kara <jack@suse.cz>
To: <linux-fsdevel@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>
Subject: [PATCH 0/2] quota: Handle corrupted quota file better
Date: Mon, 2 Nov 2020 18:27:31 +0100 [thread overview]
Message-ID: <20201102172733.23444-1-jack@suse.cz> (raw)
Hello,
syzbot has spotted that quota code does not handle corrupted quota files quite
well. Let's add some sanity checks to avoid kernel crashes when accessing
corrupted quota files.
Honza
next reply other threads:[~2020-11-02 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 17:27 Jan Kara [this message]
2020-11-02 17:27 ` [PATCH 1/2] quota: Don't overflow quota file offsets Jan Kara
2020-11-02 21:30 ` Andreas Dilger
2020-11-03 8:57 ` Jan Kara
2020-11-02 17:27 ` [PATCH 2/2] quota: Sanity-check quota file headers on load Jan Kara
2020-11-02 21:32 ` Andreas Dilger
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=20201102172733.23444-1-jack@suse.cz \
--to=jack@suse.cz \
--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).