From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Don't leave s_fs_info pointing to freed memory in init_sbd
Date: Mon, 8 Oct 2018 16:10:58 -0400 (EDT) [thread overview]
Message-ID: <1685328847.19268680.1539029458489.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20181008115624.18173-1-anprice@redhat.com>
----- Original Message -----
> When alloc_percpu() fails, sdp gets freed but sb->s_fs_info still points
> to the same address. Move the assignment after that error check so that
> s_fs_info can only point to a valid sdp or NULL, which is checked for
> later in the error path, in gfs2_kill_super().
>
> Reported-by: syzbot+dcb8b3587445007f5808 at syzkaller.appspotmail.com
> Signed-off-by: Andrew Price <anprice@redhat.com>
> ---
Hi,
Thanks. This is now pushed to the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=4c62bd9cea7bcf10292f7e4c57a2bca332942697
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2018-10-08 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 11:56 [Cluster-devel] [PATCH] gfs2: Don't leave s_fs_info pointing to freed memory in init_sbd Andrew Price
2018-10-08 20:10 ` Bob Peterson [this message]
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=1685328847.19268680.1539029458489.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
/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).