GNU bug report logs - #75569
30.0.93; Large /proc/* file are read incompletely

Previous Next

Full log

Message #11 received at 75569 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juri Linkov <juri <at> linkov.net>, Paul Eggert <eggert <at> cs.ucla.edu>
Cc: mail <at> daniel-mendler.de, 75569 <at> debbugs.gnu.org
Subject: Re: bug#75569: 30.0.93; Large /proc/* file are read incompletely
Date: Wed, 15 Jan 2025 17:07:56 +0200

> Cc: 75569 <at> debbugs.gnu.org
> From: Juri Linkov <juri <at> linkov.net>
> Date: Wed, 15 Jan 2025 09:19:10 +0200
> 
> > When opening a large file in /proc/* like /proc/cpuinfo in Emacs via
> > find-file, the buffer content is incomplete, when comparing the output
> > to the output produced by /bin/cat. The Eshell command eshell/cat has
> > the same problem.The proc file system doesn't report file sizes since
> > the files are dynamically generated. ls -l /proc/cpuinfo reports size 0.
> > Emacs doesn't handle this well, limiting its reads to 16KiB.
> >
> > In Eshell:
> >
> > cat /proc/cpuinfo > #<buffer bug>  ==> truncated buffer (exactly 16KiB)
> > *cat /proc/cpuinfo > #<buffer bug> ==> complete buffer (larger than 16KiB)
> 
> Strange, bug#9800 was closed as fixed, but I confirm the buffer is still
> truncated.

It was closed because it was fixed back then.  But maybe commits
8650b3308dd and/or 3fb2c174d3a7 broke that later?

The /proc/cpuinfo file on the system to which I have access is smaller
than 16KB, so could someone who can access a larger cpuinfo file
please see if those commits broke the fix, or maybe bisect?

Adding Paul in case he has comments or suggestions.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.