[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1079443: Processed: Re: dracut-install ... -m =drivers/XXX is ignored



On 2024-08-24 19:57, Aurelien Jarno wrote:
> control: unmerge 1079443 
> control: retitle 1079443 fts_* calling non-LFS __readdir
> 
> On 2024-08-24 21:40, Stepan Golosunov wrote:
> > On Sat, Aug 24, 2024 at 05:20:44PM +0200, Aurelien Jarno wrote:
> > > control: forcemerge 916276 1079443
> > > 
> > > Hi
> > > 
> > > On 2024-08-24 10:27, Debian Bug Tracking System wrote:
> > > > Processing control commands:
> > > > 
> > > > > reassign -1 glibc
> > > > Bug #1079443 [dracut-install] dracut-install ... -m =drivers/XXX is ignored
> > > > Bug reassigned from package 'dracut-install' to 'glibc'.
> > > > No longer marked as found in versions dracut/103-1.1.
> > > > Ignoring request to alter fixed versions of bug #1079443 to the same values previously set
> > > 
> > > This bug keeps coming, but porters do not work on getting it fixed
> > > upstream. 
> > > 
> > > My position explained in the two other merged bugs still stands. Given
> > > it only affects the qemu-user case, I do not want to take any risk
> > > applying a patch that has not been reviewed and merged upstream. If we
> > > end up "missing" files in the non qemu-user case, it might have some
> > > security implications.
> > 
> > I think #1079443 is different from the other two bugs: LFS versions of
> > the fts_* functions are calling non-LFS __readdir. This will also fail on
> > large inode numbers, even without qemu.
> 
> Ok, then I got misled by the earlier messages in that bug that pointed
> the same upstream bugs. Unmerging them, and retitling because the
> existing title is also misleading.
> 
> As you seems to have investigated seems more than me could you please
> take care of reporting the bug in the upstream bugzilla? A simple
> reproducer would be ideal.

Any news on that?

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net


Reply to: