From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>,
Filipe Manana <fdmanana@suse.com>,
David Sterba <dsterba@suse.com>
Cc: stable <stable@vger.kernel.org>
Subject: Re: btrfs related build failures in stable queues
Date: Wed, 24 Jul 2019 18:15:34 +0200 [thread overview]
Message-ID: <20190724161534.GA10454@kroah.com> (raw)
In-Reply-To: <20190724154039.GB3050@kroah.com>
On Wed, Jul 24, 2019 at 05:40:39PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Jul 24, 2019 at 08:07:50AM -0700, Guenter Roeck wrote:
> > v4.9.y to v5.1.y:
> >
> > fs/btrfs/file.c: In function 'btrfs_punch_hole':
> > fs/btrfs/file.c:2787:27: error: invalid initializer
> > struct timespec64 now = current_time(inode);
> > ^~~~~~~~~~~~
> > fs/btrfs/file.c:2790:18: error: incompatible types when assigning to type 'struct timespec' from type 'struct timespec64'
>
> Oops, no, this looks like a 32bit issue, let me dig into that...
Ok, this makes no sense.
A few lines above this we do:
inode->i_mtime = inode->i_ctime = current_time(inode);
And here we are now doing:
struct timespec64 now = current_time(inode);
inode_inc_iversion(inode);
inode->i_mtime = now;
inode->i_ctime = now;
And current_time() is defined as:
extern struct timespec64 current_time(struct inode *inode);
I have no idea what is going on :(
This is caused by Felipe's patch: 179006688a7e ("Btrfs: add missing
inode version, ctime and mtime updates when punching hole"). Felipe,
any ideas?
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-24 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 15:07 btrfs related build failures in stable queues Guenter Roeck
2019-07-24 15:40 ` Greg Kroah-Hartman
2019-07-24 16:15 ` Guenter Roeck
2019-07-24 15:40 ` Greg Kroah-Hartman
2019-07-24 16:15 ` Greg Kroah-Hartman [this message]
2019-07-24 16:50 ` Guenter Roeck
2019-07-24 18:31 ` Greg Kroah-Hartman
2019-07-24 18:46 ` Guenter Roeck
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=20190724161534.GA10454@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=linux@roeck-us.net \
--cc=stable@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