linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix.com>
To: Nate Straz <nate-ltp@refried.org>
Cc: subrata@linux.vnet.ibm.com, ltp-list@lists.sourceforge.net,
	John Williams <john.williams@petalogix.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [LTP] statvfs -> f_bavail
Date: Mon, 20 Apr 2009 08:16:50 +0200	[thread overview]
Message-ID: <49EC1352.6010900@petalogix.com> (raw)
In-Reply-To: <20090417173107.GA3590@refried.org>

Nate Straz wrote:
> On Apr 17 11:12, Michal Simek wrote:
>   
>>> don't you know what is the description of f_bavail in struct statvfs?
>>> On my system I am getting zero for this entry that's why fsync02 failed.
>>>   
>>>       
>> I track down where the problem comes from.
>> There is problem for all fs which use simple_statfs function from
>> fs/libfs.c.
>> In open.c in vfs_statfs function is whole structure set to zero and then
>> in simple_statfs not set this value.
>> I think we should fix it in ltp code.
>> Here is my proposed change. If is ok - I will generate proper patch.
>>     
>
> If the problem is in the kernel, then it should be fixed in the kernel.
> That's the whole point of LTP, pointing out problems in the kernel which
> need to be fixed.  Patching LTP to work around f_bavail not being set
> correctly is not the right thing to do.
>   
:-) And what about if is the kernel code ok? :-)
Then IMHO is the right time to fix LTP.

The main question is if is or not.

Hi guys from linux-fsdevel: Can you told us what is the right solution
for my problem above?

Thanks,
Michal

> Nate
>   


-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663


       reply	other threads:[~2009-04-20  6:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49E759FB.70103@petalogix.com>
     [not found] ` <49E847FB.1030801@petalogix.com>
     [not found]   ` <20090417173107.GA3590@refried.org>
2009-04-20  6:16     ` Michal Simek [this message]
2009-04-20  6:26       ` [LTP] statvfs -> f_bavail Al Viro
2009-04-20  6:42         ` Michal Simek
     [not found]           ` <49EC1945.1000805-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
2009-04-20 22:59             ` Nate Straz
2009-04-21  0:25           ` [LTP] " Al Viro
2009-04-21  0:38             ` Andreas Dilger
2009-04-21  0:47               ` Al Viro
2009-04-21  8:45             ` Michal Simek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49EC1352.6010900@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=john.williams@petalogix.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=nate-ltp@refried.org \
    --cc=subrata@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).