Re: [PATCH 02/61] vfs: change i_ino from unsigned long to u64

[Jeff Layton]

On Thu, 2026-02-26 at 18:19 +0100, Jan Kara wrote:
> On Thu 26-02-26 11:45:16, Jeff Layton wrote:
> > On Thu, 2026-02-26 at 11:40 -0500, Mathieu Desnoyers wrote:
> > > On 2026-02-26 11:35, Jeff Layton wrote:
> > > > 
> > > > I'll let others chime in first, but I'm open to going back and doing it
> > > > that way if we don't want to live with the compiler warnings during a
> > > > bisect.
> > > 
> > > On 32-bit archs, I suspect it will do more than emit compiler warnings.
> > > Trying to boot a kernel in the middle of the series is likely to lead to
> > > interesting inode value printout results.
> > > 
> > 
> > Definitely. None of that would be trustworthy in the middle of the
> > series.
> 
> Yeah, I think defining kino_t in the beginning as unsigned long, convert
> everything (including special format string specifier) to it, then switch
> it to u64 and finally just 'sed-out' the format string specifier in the
> final patch shouldn't be harder than what you do here and should keep
> bisectability?
> 

Ok. I'll look at doing it in a way that doesn't break bisectability.

-- 
Jeff Layton <jlayton@xxxxxxxxxx>