aio_cancel/3-1: increase BUF_SIZE

When do aio_cancel, all the aio_write operations have finished on some
platforms. That cause the case return UNRESOLVED. So increase the BUF_SIZE
to delay aio_write finish that make one aio_write operation can be
cancelled at least.

Signed-off-by: Kang Kai <kai.kang@windriver.com>
Reviewed-by: Caspar Zhang <caspar@casparzhang.com>
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
hugeshmget02: remove the existent key before testing

We can't assume that the key (-1) is always non-existent,
if it is a existent key, the case can fail as the errno
EINVAL but not ENOENT.

Here is a example:
[root@gaowanlong hugeshmget]# cat /proc/sysvipc/shm
       key      shmid perms                  size  cpid  lpid nattch   uid   gid  cuid  cgid      atime      dtime      ctime                   rss                  swap
         0          0  1600                393216  5208 20444      2  1000  1000  1000  1000 1334025830 1334025830 1334017058                393216                     0
         0      32769  1600                393216  5290  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334017062                393216                     0
         0      65538  1600                393216  5663  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334017370                131072                     0
         0      98307  1600                393216  5728  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334017542                393216                     0
         0     393220  1600                   784  5803  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334018967                  4096                     0
         0     425989  1600                393216  6390  6936      2  1000  1000  1000  1000 1334019115 1334019115 1334018973                393216                     0
         0     262150  1600                393216  6120  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334018292                 86016                     0
         0     294919  1600                393216  6120  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334018293                 98304                     0
         0     327688  1600                   784  5803  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334018928                  4096                     0
         0     458761  1600                393216  6390  6936      2  1000  1000  1000  1000 1334019115 1334019115 1334018973                196608                     0
         0  726925322  1600                393216 12957   870      2  1000  1000  1000  1000 1334020771          0 1334020771                364544                     0
         0  726958091  1600                393216 12957   870      2  1000  1000  1000  1000 1334020771          0 1334020771                196608                     0
         0  727089164  1600                393216 18617   870      2  1000  1000  1000  1000 1334024696          0 1334024696                131072                     0
         0  727121933  1600                393216 18617   870      2  1000  1000  1000  1000 1334024696          0 1334024696                286720                     0
        -1  727285775   600              33554432 20447     0      0     0     0     0     0          0          0 1334025832                     0                     0
[root@gaowanlong hugeshmget]# ./hugeshmget02
hugeshmget02    0  TINFO  :  set nr_hugepages to 128
hugeshmget02    0  TINFO  :  Set shm_size to shmmax: 33554432
hugeshmget02    1  TPASS  :  shmget failed as expected: TEST_ERRNO=EINVAL(22): Invalid argument
hugeshmget02    2  TPASS  :  shmget failed as expected: TEST_ERRNO=EINVAL(22): Invalid argument
hugeshmget02    3  TPASS  :  shmget failed as expected: TEST_ERRNO=EEXIST(17): File exists
hugeshmget02    4  TFAIL  :  shmget succeeded unexpectedly
hugeshmget02    0  TINFO  :  set nr_hugepages to 0

Add some time I met,
hugeshmget02    4  TFAIL  :  shmget failed unexpectedly - expect
errno=2, got: TEST_ERRNO=EINVAL(22): Invalid argument
hugeshmget02    1  TPASS  :  shmget failed as expected:
TEST_ERRNO=EINVAL(22): Invalid argument
hugeshmget02    2  TPASS  :  shmget failed as expected:
TEST_ERRNO=EINVAL(22): Invalid argument
hugeshmget02    3  TPASS  :  shmget failed as expected:
TEST_ERRNO=EEXIST(17): File exists
hugeshmget02    4  TFAIL  :  shmget failed unexpectedly - expect
errno=2, got: TEST_ERRNO=EINVAL(22): Invalid argument

So, in this patch, we remove the key (-1) from shm entry firstly if it's a existent key.
After patch applied,

[root@gaowanlong hugeshmget]# ./hugeshmget02
hugeshmget02    0  TINFO  :  set nr_hugepages to 128
hugeshmget02    0  TINFO  :  Set shm_size to shmmax: 33554432
hugeshmget02    1  TPASS  :  shmget failed as expected: TEST_ERRNO=EINVAL(22): Invalid argument
hugeshmget02    2  TPASS  :  shmget failed as expected: TEST_ERRNO=EINVAL(22): Invalid argument
hugeshmget02    3  TPASS  :  shmget failed as expected: TEST_ERRNO=EEXIST(17): File exists
hugeshmget02    4  TPASS  :  shmget failed as expected: TEST_ERRNO=ENOENT(2): No such file or directory
hugeshmget02    0  TINFO  :  set nr_hugepages to 0
[root@gaowanlong hugeshmget]# cat /proc/sysvipc/shm
       key      shmid perms                  size  cpid  lpid nattch   uid   gid  cuid  cgid      atime      dtime      ctime                   rss                  swap
         0          0  1600                393216  5208 20713      2  1000  1000  1000  1000 1334025922 1334025922 1334017058                393216                     0
         0      32769  1600                393216  5290  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334017062                393216                     0
         0      65538  1600                393216  5663  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334017370                131072                     0
         0      98307  1600                393216  5728  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334017542                393216                     0
         0     393220  1600                   784  5803  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334018967                  4096                     0
         0     425989  1600                393216  6390  6936      2  1000  1000  1000  1000 1334019115 1334019115 1334018973                393216                     0
         0     262150  1600                393216  6120  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334018292                 86016                     0
         0     294919  1600                393216  6120  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334018293                 98304                     0
         0     327688  1600                   784  5803  6445      2  1000  1000  1000  1000 1334018979 1334018979 1334018928                  4096                     0
         0     458761  1600                393216  6390  6936      2  1000  1000  1000  1000 1334019115 1334019115 1334018973                196608                     0
         0  726925322  1600                393216 12957   870      2  1000  1000  1000  1000 1334020771          0 1334020771                364544                     0
         0  726958091  1600                393216 12957   870      2  1000  1000  1000  1000 1334020771          0 1334020771                196608                     0
         0  727089164  1600                393216 18617   870      2  1000  1000  1000  1000 1334024696          0 1334024696                131072                     0
         0  727121933  1600                393216 18617   870      2  1000  1000  1000  1000 1334024696          0 1334024696                286720                     0

Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
Reviewed-by: Caspar Zhang <caspar@casparzhang.com>
ld01: fix the error message of gcc

Gcc has changed the error message by adding a error level.

Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
Reviewed-by: Caspar Zhang <caspar@casparzhang.com>