linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: akpm@osdl.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [bug report] [PATCH] sys_sync_file_range()
Date: Wed, 14 Mar 2018 22:36:21 +0300	[thread overview]
Message-ID: <20180314193621.GA2249@mwanda> (raw)

Hello Andrew Morton,

The patch f79e2abb9bd4: "[PATCH] sys_sync_file_range()" from Mar 31,
2006, leads to the following static checker warning:

	fs/sync.c:298 ksys_sync_file_range()
	warn: signed overflow undefined. 'offset + nbytes < offset'

fs/sync.c
   279  int ksys_sync_file_range(int fd, loff_t offset, loff_t nbytes,
   280                           unsigned int flags)
   281  {
   282          int ret;
   283          struct fd f;
   284          struct address_space *mapping;
   285          loff_t endbyte;                 /* inclusive */
   286          umode_t i_mode;
   287  
   288          ret = -EINVAL;
   289          if (flags & ~VALID_FLAGS)
   290                  goto out;
   291  
   292          endbyte = offset + nbytes;
   293  
   294          if ((s64)offset < 0)
   295                  goto out;
   296          if ((s64)endbyte < 0)
   297                  goto out;
   298          if (endbyte < offset)
                    ^^^^^^^^^^^^^^^^
This is undefined but I think it works with the kernel build options?

   299                  goto out;
   300  
   301          if (sizeof(pgoff_t) == 4) {
   302                  if (offset >= (0x100000000ULL << PAGE_SHIFT)) {
   303                          /*
   304                           * The range starts outside a 32 bit machine's
   305                           * pagecache addressing capabilities.  Let it "succeed"
   306                           */
   307                          ret = 0;
   308                          goto out;
   309                  }
   310                  if (endbyte >= (0x100000000ULL << PAGE_SHIFT)) {
   311                          /*
   312                           * Out to EOF
   313                           */
   314                          nbytes = 0;
   315                  }
   316          }

regards,
dan carpenter

             reply	other threads:[~2018-03-14 19:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 19:36 Dan Carpenter [this message]
2018-03-14 19:56 ` [bug report] [PATCH] sys_sync_file_range() Andrew Morton

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=20180314193621.GA2249@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).