[rsbac] a few problems

Josh Beagley rsbac@rsbac.org
Fri Sep 20 18:31:17 2002


>=A0On Monday, 16. September 2002 09:37, Amon Ott wrote:
>=A0> On Friday, 13. September 2002 18:09, Josh Beagley wrote:
>=A0> > >=A0On Monday, 9. September 2002 09:25, Josh Beagley wrote:
>=A0> > >=A0> The first problem I seem to be having is enabling FF
>=A0flags > > >=A0add_inherited > and secure_delete on my home
>=A0directory. I am > > >=A0> Sep  7 02:13:02 Lynx kernel: Assertion
>=A0failure in > > >=A0ext3_sync_file() at > fsync.c:55:
>=A0"ext3_journal_current_handle() > > >=A0=3D=3D 0" > Sep  7 02:13:0=
2 Lynx
>=A0kernel: kernel BUG at fsync.c:55! > > >=A0
>=A0> > >=A0This is caused by the RSBAC secure delete code calling
>=A0fsync, > > >=A0although the  journal is currently open.
>=A0
>=A0> > well, after recompiling rsbac with the attached patch, I
>=A0created a file > > with the contents being the word "nongoword",
>=A0which I then deleted, and of > > course i enabled secure delete
>=A0for the directory the file was in. Using  the
>=A0> > lde tool, which examines and recoveres deleted files from a
>=A0ext2  partition,
>=A0> > i was able to search for the phrase "nongoword" and recover
>=A0the file. >=20
>=A0> OK, I will try to code my own fsync in ext3 to avoid the
>=A0problem.=20
>=A0The attached patch against rsbac/adf/adf_main.c (with the
>=A0previous patch,  please change fsync code by hand otherwise)
>=A0makes secdel on ext3 work fine on  my test system. Could you
>=A0please test it?=20
>=A0Unfortunately, secure delete seems to fail on reiserfs. Could
>=A0someone else  please try it there to verify? I'd better remove
>=A0the calls from there, if it  does not work anyway. Reiserfs seems
>=A0to optimize disk writes too well...=20
>=A0Amon.
>=A0--
>=A0http://www.rsbac.org
>=A0
>=A0[Attachment: secdel.diff]

secure delete is running fine on ext3

good job amon!