Opened 6 years ago

Closed 6 years ago

#9984 closed enhancement (fixed)

samba-4.7.2 (Critical data corruption issue)

Reported by: bdubbs@… Owned by: Douglas R. Reno
Priority: highest Milestone: 8.2
Component: BOOK Version: SVN
Severity: critical Keywords:


New point version.

Change History (5)

comment:1 by Douglas R. Reno, 6 years ago

Priority: normalhighest
Severity: normalcritical

Samba-4.7.2 "Emergency" release issued.

I'm right at it for gvfs. I'll take this now.

                   Release Notes for Samba 4.7.2
                         November 15, 2017

This is an additional bugfix release to address a possible data corruption
issue. Please update immediately! For details, please see

Samba 4.6.0 and newer is affected by this issue.

Changes since 4.7.1:

o  Jeremy Allison <>
   * BUG 13121: Non-smbd processes using kernel oplocks can hang smbd.

o  Joe Guo <>
   * BUG 13127: python: use communicate to fix Popen deadlock.

o  Volker Lendecke <>
   * BUG 13130: smbd on disk file corruption bug under heavy threaded load.

o  Stefan Metzmacher <>
   * BUG 13130: tevent: version 0.9.34.

o  Ralph Wuerthner <>
   * BUG 13118: s3: smbd: Fix delete-on-close after smb2_find.

Hi, Karolin!

Unfortunately I believe this makes an emergency interim release necessary. Sorry for that, but data corruption is really, really bad.

Yes, I'm afraid I concur with Volker. This can cause file corruption, and the *single* thing file servers must do is not corrupt files. So this is more important than a security release IMHO. Sorry :-(.
We need to backport full tevent releases, otherwise someone could still build against a broken system libtevent.

I'm preparing tevent 0.9.34 and push it to autobuild shortly.

comment:2 by Douglas R. Reno, 6 years ago

Owner: changed from blfs-book@… to Douglas R. Reno
Status: newassigned

comment:3 by Douglas R. Reno, 6 years ago

Summary: samba-4.7.1samba-4.7.2

comment:4 by Douglas R. Reno, 6 years ago

Summary: samba-4.7.2samba-4.7.2 (Critical data corruption issue)

comment:5 by Douglas R. Reno, 6 years ago

Resolution: fixed
Status: assignedclosed

Fixed at r19516

Note: See TracTickets for help on using tickets.