linux-kernel - [PATCH 0/2] exofs: Double page_unlock BUG in write_begin/write

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CAF1AA1.1090801@panasas.com>
Date:	Fri, 08 Oct 2010 09:20:33 -0400
From:	Boaz Harrosh <bharrosh@...asas.com>
To:	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	open-osd <osd-dev@...n-osd.org>,
	Benny Halevy <bhalevy@...asas.com>
Subject: [PATCH 0/2] exofs: Double page_unlock BUG in write_begin/write_end

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/