>> > +_filesystem_timestamp_range()
>> > +{
>> > + device=${1:-$TEST_DEV}
>> > + case $FSTYP in
>> > + ext4) #dumpe2fs
>> > + if [ $(dumpe2fs -h $device 2>/dev/null | grep "Inode size:" |
>> > cut -d: -f2) -gt 128 ]; then
>> > + echo "-2147483648 15032385535"
> Need an entry in .gitignore file too.
Will add this.
>> SUBDIRS =
>>
>> diff --git a/src/y2038_futimens.c b/src/y2038_futimens.c
>> new file mode 100644
>> index 000..291e4fa
>> --- /dev/null
>> +++ b/src/y2038_futimens.c
>> @@ -0,0 +1,61 @@
>> +#include
>> +#include
>> +#include
>>
On Thursday, November 24, 2016 6:40:55 PM CET Eryu Guan wrote:
> On Wed, Nov 23, 2016 at 04:52:02PM -0800, Deepa Dinamani wrote:
> > +_filesystem_timestamp_range()
> > +{
> > + device=${1:-$TEST_DEV}
> > + case $FSTYP in
> > + ext4) #dumpe2fs
> > + if [ $(dumpe2fs -h $device
On Wed, Nov 23, 2016 at 04:52:02PM -0800, Deepa Dinamani wrote:
> The test helps to validate clamping and mount behaviors
> according to supported file system timestamp ranges.
>
> Note that the test can fail on 32-bit systems for a
> few file systems. This will be corrected when vfs is
>
The test helps to validate clamping and mount behaviors
according to supported file system timestamp ranges.
Note that the test can fail on 32-bit systems for a
few file systems. This will be corrected when vfs is
transitioned to use 64-bit timestamps.
Signed-off-by: Deepa Dinamani
