exofs: Double page_unlock BUG in write_begin/write_end
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | exofs: Fix double page_unlock BUG in write_begin/endfs/ | +7 | 0 replies | |
| 2/2 | exofs: Cleaup read path in regard with read_for_writefs/ | +14 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
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