linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <esandeen@redhat.com>
To: Dave Chinner <david@fromorbit.com>,
	"Darrick J. Wong" <djwong@kernel.org>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfsprogs for-next rebased to b4c6731a
Date: Mon, 18 Oct 2021 09:56:38 -0500	[thread overview]
Message-ID: <c686231d-f478-2737-793f-ae618e50b2ce@redhat.com> (raw)
In-Reply-To: <20211016062943.GX2361455@dread.disaster.area>

On 10/16/21 1:29 AM, Dave Chinner wrote:
> On Fri, Oct 15, 2021 at 09:10:17PM -0700, Darrick J. Wong wrote:
>> On Fri, Oct 15, 2021 at 03:32:41PM -0500, Eric Sandeen wrote:
>>> On 10/15/21 2:42 PM, Eric Sandeen wrote:
>>>> Hi folks,
>>>>
>>>> The for-next branch of the xfsprogs repository at:
>>>>
>>>>       git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
>>>>
>>>> has just been updated.
>>>>
>>>> Patches often get missed, so please check if your outstanding
>>>> patches were in this update. If they have not been in this update,
>>>> please resubmit them to linux-xfs@vger.kernel.org so they can be
>>>> picked up in the next update.
>>>>
>>>> This is really just the libxfs-5.14 sync (finally!).  Big thanks
>>>> to chandan, djwong, dchinner who all helped significantly with what
>>>> was a much more challenging libxfs sync this time.
>>>>
>>>> Odds are this will be the bulk of the final 5.14 release. I will just
>>>> add Darrick's deprecation warning, and anything else I get reminded
>>>> of in the next week.  :)
>>>
>>> I missed Derrick's "libxfs: fix crash on second attempt to initialize library"
>>> because my old userspace rcu library did not exhibit the problem. :/
>>>
>>> Rather than leave a few dozen commits with regressed behavior as a bisect bomb,
>>> I have force-pushed and anybody who pulled in the last hour will need to rebase.
>>> Sorry about that!
>>
>> Er... /me notices the following discrepancy between the kernel and
>> xfsprogs in libxfs/xfs_shared.h:
>>
>> --- a/libxfs/xfs_shared.h
>> +++ b/libxfs/xfs_shared.h
>> @@ -174,24 +174,4 @@ struct xfs_ino_geometry {
>>   
>>   };
>>   
>> -/* Faked up kernel bits */
>> -struct rb_root {
>> -};
>> -
>> -#define RB_ROOT                (struct rb_root) { }
>> -
>> -typedef struct wait_queue_head {
>> -} wait_queue_head_t;
>> -
>> -#define init_waitqueue_head(wqh)       do { } while(0)
>> -
>> -struct rhashtable {
>> -};
>> -
>> -struct delayed_work {
>> -};
>> -
>> -#define INIT_DELAYED_WORK(work, func)  do { } while(0)
>> -#define cancel_delayed_work_sync(work) do { } while(0)
>> -
>>   #endif /* __XFS_SHARED_H__ */
> 
> Shouldn't those be libxfs/libxfs_priv.h along with all the other
> faked up kernel bits?

IIRC that doesn't work but I don't remember why - has to do w/ the ag code move,
and use in userspace IIRC. And TBH I forgot that "xfs_shared" was uhhhh actually
shared with the kernel and failed to check.

I'll figure something out.  Tired of pushing this stuff from file to file,
subdir to subdir ... was trying to avoid libfrog.

But thanks for noticing, Darrick - and sorry for missing it.

-Eric


      reply	other threads:[~2021-10-18 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 19:42 [ANNOUNCE] xfsprogs for-next updated to 7189ee53 Eric Sandeen
2021-10-15 20:32 ` [ANNOUNCE] xfsprogs for-next rebased to b4c6731a Eric Sandeen
2021-10-16  4:10   ` Darrick J. Wong
2021-10-16  6:29     ` Dave Chinner
2021-10-18 14:56       ` Eric Sandeen [this message]

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=c686231d-f478-2737-793f-ae618e50b2ce@redhat.com \
    --to=esandeen@redhat.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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).