From: Boaz Harrosh <bharrosh@panasas.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>,
Benny Halevy <bhalevy@panasas.com>
Subject: [PATCH 0/2] exofs: Double page_unlock BUG in write_begin/write_end
Date: Fri, 08 Oct 2010 09:20:33 -0400 [thread overview]
Message-ID: <4CAF1AA1.1090801@panasas.com> (raw)
Testing at Bakeathon, I got a page_unlock BUG_ON triggered.
I've found a very old bug, back from the days of the empire.
It is time related and it only triggers since couple of
rc-releases.
The first patch is the bug fix and I'd want to push it to Linus
for this version. If it's already to late I'll get it to the
merge window with a CC for stable.
The second patch is a cleanup that opened up do to the new
variable introduced in the bugfix above. Which I'll push for
the next release.
[PATCH 1/2] exofs: Fix double page_unlock BUG in write_begin/end
[PATCH 2/2] exofs: Cleaup read path in regard with read_for_write
Thanks
Boaz
next reply other threads:[~2010-10-08 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 13:20 Boaz Harrosh [this message]
2010-10-08 13:53 ` [PATCH 1/2] exofs: Fix double page_unlock BUG in write_begin/end Boaz Harrosh
2010-10-08 14:04 ` [PATCH 2/2] exofs: Cleaup read path in regard with read_for_write Boaz Harrosh
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=4CAF1AA1.1090801@panasas.com \
--to=bharrosh@panasas.com \
--cc=bhalevy@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osd-dev@open-osd.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