From: Abhijith Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2] bz231369 - GFS2 will panic if you misspell any mount options
Date: Mon, 15 Sep 2008 09:01:23 -0500 [thread overview]
Message-ID: <48CE6AB3.8030302@redhat.com> (raw)
In-Reply-To: <48C94D5F.8080601@redhat.com>
Abhijith Das wrote:
> This is the upstream patch. RHEL5 patch posted to rhkernel-list.
> The gfs2 superblock pointer is NULL after a failed mount. When control
> eventually goes to gfs2_kill_sb, we dereference this NULL pointer. This
> patch ensures that the gfs2 superblock pointer is not NULL before being
> dereferenced in gfs2_kill_sb.
>
> Signed-off-by: Abhijith Das <adas@redhat.com>
>
Corrected upstream patch.
Signed-off-by: Abhijith Das <adas@redhat.com>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bz231369-git.patch
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20080915/8fabfad4/attachment.ksh>
next prev parent reply other threads:[~2008-09-15 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 9:34 [Cluster-devel] [GFS2] Fix rename locking issue Steven Whitehouse
2008-09-11 16:54 ` [Cluster-devel] [GFS2] bz231369 - GFS2 will panic if you misspell any mount options Abhijith Das
2008-09-15 14:01 ` Abhijith Das [this message]
2008-09-15 16:01 ` Steven Whitehouse
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=48CE6AB3.8030302@redhat.com \
--to=adas@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 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.