From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] Bug 603827 - GFS2: BUG in gfs2_adjust_quota
Date: Mon, 05 Jul 2010 14:49:20 +0100 [thread overview]
Message-ID: <1278337760.2447.3.camel@localhost> (raw)
In-Reply-To: <622206662.748471278221604852.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
Hi,
On Sun, 2010-07-04 at 01:33 -0400, Abhijith Das wrote:
> This patch is for inclusion upstream.
>
> HighMem pages on i686 do not get mapped to the buffer_heads and this was
> causing a NULL pointer dereference when we were trying to memset page buffers
> to zero.
> We now use zero_user() that kmaps the page and directly manipulates page data.
> This patch also fixes a boundary condition that was incorrect.
>
> Signed-off-by: Abhi Das <adas@redhat.com>
Now in the -nmw git tree. Thanks,
Steve.
prev parent reply other threads:[~2010-07-05 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <648608147.748451278221467098.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2010-07-04 5:33 ` [Cluster-devel] [GFS2 PATCH] Bug 603827 - GFS2: BUG in gfs2_adjust_quota Abhijith Das
2010-07-05 13:49 ` Steven Whitehouse [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=1278337760.2447.3.camel@localhost \
--to=swhiteho@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