LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Matthew Wilcox <willy@infradead.org>,
David Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org, Dave Chinner <dchinner@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the folio tree with the xfs tree
Date: Wed, 11 Aug 2021 07:44:46 -0700 [thread overview]
Message-ID: <20210811144446.GD3601443@magnolia> (raw)
In-Reply-To: <20210811144345.GC3601443@magnolia>
On Wed, Aug 11, 2021 at 07:43:45AM -0700, Darrick J. Wong wrote:
> On Wed, Aug 11, 2021 at 05:42:31PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the folio tree got a conflict in:
> >
> > mm/util.c
> >
> > between commit:
> >
> > de2860f46362 ("mm: Add kvrealloc()")
> >
> > from the xfs tree and commit:
> >
> > 3bc0556bade4 ("mm: Add folio_raw_mapping()")
> >
> > from the folio tree.
> >
> > I fixed it up (see below) and can carry the fix as necessary. This
> > is now fixed as far as linux-next is concerned, but any non trivial
> > conflicts should be mentioned to your upstream maintainer when your tree
> > is submitted for merging. You may also want to consider cooperating
> > with the maintainer of the conflicting tree to minimise any particularly
> > complex conflicts.
>
> Hmmm. Seeing as krealloc lives in mm/slab_common.c anyway, I might just
> move this function there, and (hopefully) avoid this conflict.
Never mind, didn't work.
--D
>
> --D
>
> >
> > --
> > Cheers,
> > Stephen Rothwell
> >
> > diff --cc mm/util.c
> > index d06e48b28eec,e8fa30e48447..000000000000
> > --- a/mm/util.c
> > +++ b/mm/util.c
> > @@@ -660,31 -635,6 +660,21 @@@ void kvfree_sensitive(const void *addr
> > }
> > EXPORT_SYMBOL(kvfree_sensitive);
> >
> > +void *kvrealloc(const void *p, size_t oldsize, size_t newsize, gfp_t flags)
> > +{
> > + void *newp;
> > +
> > + if (oldsize >= newsize)
> > + return (void *)p;
> > + newp = kvmalloc(newsize, flags);
> > + if (!newp)
> > + return NULL;
> > + memcpy(newp, p, oldsize);
> > + kvfree(p);
> > + return newp;
> > +}
> > +EXPORT_SYMBOL(kvrealloc);
> > +
> > - static inline void *__page_rmapping(struct page *page)
> > - {
> > - unsigned long mapping;
> > -
> > - mapping = (unsigned long)page->mapping;
> > - mapping &= ~PAGE_MAPPING_FLAGS;
> > -
> > - return (void *)mapping;
> > - }
> > -
> > /* Neutral page->mapping pointer to address_space or anon_vma or other */
> > void *page_rmapping(struct page *page)
> > {
>
>
prev parent reply other threads:[~2021-08-11 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 7:42 Stephen Rothwell
2021-08-11 14:43 ` Darrick J. Wong
2021-08-11 14:44 ` Darrick J. Wong [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=20210811144446.GD3601443@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=willy@infradead.org \
--subject='Re: linux-next: manual merge of the folio tree with the xfs tree' \
/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
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).