From kde-core-devel Sat Jan 17 23:38:35 2009 From: Michael Leupold Date: Sat, 17 Jan 2009 23:38:35 +0000 To: kde-core-devel Subject: Re: File corruption with KSaveFile on full disk Message-Id: <200901180038.36948.lemma () confuego ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=123223570328900 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1347161.LbvnBLJlLM" --nextPart1347161.LbvnBLJlLM Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 18 January 2009 00:19:44 Thiago Macieira wrote: > Michael Leupold wrote: > >I'm pretty much stuck because I couldn't reproduce myself but I assumed > > this couldn't happen as kwalletd's backend uses KSaveFile to make sure > > either the whole wallet gets saved or nothing. As KSaveFile seems to be > > currently unmaintained I hope someone of you knows if it's supposed to > > handle full disk and if there's a corner case where this might indeed > > lead to corruption. > It's supposed to. And if it doesn't, then it's a bug that has to be fixed. > But I am not aware of any such conditions left. I'm not convinced it's a KSaveFile bug yet. I'm just trying to learn about = the=20 possibilities this might originate from. After all it might still be a KWal= let=20 bug. Regards, Michael --nextPart1347161.LbvnBLJlLM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBJcmv8lfpzINIAlVsRAitnAKCVR+W//GvAeh8aP7GqjVY5o1pNewCdFFLW m5bzXeHeFIOc49ipduswp9c= =nxNS -----END PGP SIGNATURE----- --nextPart1347161.LbvnBLJlLM--