FS/XFS testing framework
 help / color / mirror / Atom feed
From: Shiyang Ruan <ruansy.fnst@fujitsu.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org, "Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [PATCH] include/builddefs.in: ignore unused-result warning
Date: Thu, 16 Jan 2025 17:55:49 +0800	[thread overview]
Message-ID: <f514fa8b-0ed7-40c7-82ed-71fc54dd2dd6@fujitsu.com> (raw)
In-Reply-To: <20250115153327.izjczrhtpd2yjfjc@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>



在 2025/1/15 23:33, Zorro Lang 写道:
> On Mon, Jan 06, 2025 at 05:59:06PM +0800, Shiyang Ruan wrote:
>> When build xfstests, a lot of "unused result" warning are reported:
>>
>>      [CC] write_log.lo
>> write_log.c: In function 'wlog_record_write':
>> write_log.c:205:13: warning: ignoring return value of 'write' declared with attribute 'warn_unused_result' [-Wunused-result]
>>    205 |             write(wfile->w_afd, wbuf, reclen);
>>        |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> write_log.c:209:13: warning: ignoring return value of 'write' declared with attribute 'warn_unused_result' [-Wunused-result]
>>    209 |             write(wfile->w_rfd, wbuf, reclen);
>>        |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>      [CC] random.lo
> 
> Hi,
> 
> I never hit this build warning:
> 
> # make
> ...
> Building lib
>      [LTDEP]
>      [CC] write_log.lo
>      [LD]
> Building ltp
>      [CC]    doio
>      [CC]    fsstress
> ...
> 
> Besides that ...

Could you share me the info of your build environment?  Such as OS, 
kernel, gcc version.  I'd like to find out what wrong with mine.


--
Thanks,
Ruan.

> 
>>
>> Mostly are calused by not using the return value of read()/write()/...
>> Ignore this warning by adding `-Wno-unused-result` to CCFLAGS.  This
>> won't cause other problem but make the log clean.
>>
>> Signed-off-by: Shiyang Ruan <ruansy.fnst@fujitsu.com>
>> ---
>>   include/builddefs.in | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/builddefs.in b/include/builddefs.in
>> index 7274cde8d..edf87ff00 100644
>> --- a/include/builddefs.in
>> +++ b/include/builddefs.in
>> @@ -75,7 +75,7 @@ HAVE_RLIMIT_NOFILE = @have_rlimit_nofile@
>>   NEED_INTERNAL_XFS_IOC_EXCHANGE_RANGE = @need_internal_xfs_ioc_exchange_range@
>>   HAVE_FICLONE = @have_ficlone@
>>   
>> -GCCFLAGS = -funsigned-char -fno-strict-aliasing -Wall
>> +GCCFLAGS = -funsigned-char -fno-strict-aliasing -Wall -Wno-unused-result
> 
> I'm not an expert of gcc. From the manual of gcc, it says:
> 
>         -Wno-unused-result
>             Do not warn if a caller of a function marked with attribute "warn_unused_result" does not use its return value. The default is -Wunused-result.
> 
> Looks like the "-Wno-unused-result" works for "a function marked with
> attribute warn_unused_result", e.g.
> 
>      int __attribute__((warn_unused_result)) foo(void)
> 
> I think fstests doesn't use that attribute.
> 
> Thanks,
> Zorro
> 
> 
>>   
>>   ifeq ($(PKG_PLATFORM),linux)
>>   PCFLAGS = -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 $(GCCFLAGS)
>> -- 
>> 2.43.0
>>
>>
> 

  parent reply	other threads:[~2025-01-16  9:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06  9:59 [PATCH] include/builddefs.in: ignore unused-result warning Shiyang Ruan
2025-01-15  9:15 ` Shiyang Ruan
2025-01-15 15:33 ` Zorro Lang
2025-01-15 21:45   ` Darrick J. Wong
2025-01-17  4:11     ` Zorro Lang
2025-01-16  9:55   ` Shiyang Ruan [this message]
2025-01-17  4:01     ` Zorro Lang
2025-01-17  5:55       ` Shiyang Ruan

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=f514fa8b-0ed7-40c7-82ed-71fc54dd2dd6@fujitsu.com \
    --to=ruansy.fnst@fujitsu.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=zlang@redhat.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