Skip to content

exofs: Double page_unlock BUG in write_begin/write_end

Boaz Harrosh linux-fsdevel lkml 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2exofs: Fix double page_unlock BUG in write_begin/endfs/exofs/inode.c+7 -10 replies
2/2exofs: Cleaup read path in regard with read_for_writefs/exofs/inode.c+14 -200 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [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