Subject: Re: linux-next: build warnings after merge of the block tree

From: Josh Poimboeuf <[email-masked]>
Date: Tue, 11 Apr 2023 14:55:18 -0700

On Wed, Apr 12, 2023 at 07:34:16AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Tue, 28 Mar 2023 10:47:19 +1100 Stephen Rothwell <[email-masked]> wrote:
> >
> > On Mon, 27 Mar 2023 09:26:30 -0700 Josh Poimboeuf <[email-masked]> wrote:
> > >
> > > On Mon, Mar 27, 2023 at 12:00:17PM +1100, Stephen Rothwell wrote:  
> > > > 
> > > > After merging the block tree, today's linux-next build (x86_64
> > > > allnoconfig) produced these warnings:
> > > > 
> > > > lib/iov_iter.o: warning: objtool: .altinstr_replacement+0x0: redundant UACCESS d
> > > > isable
> > > > lib/iov_iter.o: warning: objtool: iovec_from_user.part.0+0xc7: call to copy_comp
> > > > at_iovec_from_user.part.0() with UACCESS enabled
> > > > lib/iov_iter.o: warning: objtool: __import_iovec+0x21d: call to copy_compat_iovec_from_user.part.0() with UACCESS enabled
> > > > 
> > > > Presumably introduced by commit
> > > > 
> > > >   6376ce56feb6 ("iov_iter: import single vector iovecs as ITER_UBUF")    
> > > 
> > > I'm not able to recreate.  What's your compiler version?  
> > 
> > $ x86_64-linux-gnu-gcc --version
> > x86_64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0
> 
> Any progress?

I still wasn't able to recreate with gcc version 12.2.1 20221121 (Red
Hat 12.2.1-4) (GCC) .

Is it a cross-compile?

Can you share the .o file?

-- 
Josh