s3:smb2_create: fix allocation size return value when opening existing files
commit56664800e1858f6a7156a4f611dd6d02873892ff
authorChristian Ambach <ambi@samba.org>
Mon, 10 Oct 2011 15:48:18 +0000 (10 17:48 +0200)
committerKarolin Seeger <kseeger@samba.org>
Wed, 12 Oct 2011 18:56:39 +0000 (12 20:56 +0200)
tree34269a7ad325a9c17033b97e2cd938b18fb1d0fc
parent547fe474472feed43226c3d05219d93918631b59
s3:smb2_create: fix allocation size return value when opening existing files

at least on GPFS, using the stat information gave wrong results
example: FileInfo gave 12582912000, Create Response gave 25769803776000

This makes the create part use the same method as fileinfo,
matching up the replies of both calls

Autobuild-User: Jeremy Allison <jra@samba.org>
Autobuild-Date: Mon Oct 10 21:49:53 CEST 2011 on sn-devel-104
(cherry picked from commit ec0c1f2c34ea520b4a7d636ba284a9c7d3ecd96f)

Fix bug #8518 (SMB2 create call returns incorrect file allocation size).
(cherry picked from commit 762811de03b719ae9b69ac4e7b94a3db224c1ab9)
source3/smbd/smb2_create.c