Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Michael S <already5chosen@yahoo.com>
Newsgroups: comp.arch
Subject: Broken Date formats
Date: Mon, 11 Mar 2024 17:32:50 +0200
Organization: A noiseless patient Spider
Lines: 93
Message-ID: <20240311173250.0000096e@yahoo.com>
References: <usg40i$1udfo$3@dont-email.me>
	<_Y_GN.75295$LONb.13164@fx08.iad>
	<usibg4$2ffdn$1@dont-email.me>
	<usif12$2g7eq$1@dont-email.me>
	<usinhj$2i2nn$1@dont-email.me>
	<6b75cd0221ee827b49cd2275f2c65789@www.novabbs.org>
	<Qry*XE3Ez@news.chiark.greenend.org.uk>
	<7da2a6f0e0878f914dee2286db833dc2@www.novabbs.org>
	<Qry*d14Ez@news.chiark.greenend.org.uk>
	<bd0b3b879184fd66b2c90cf4da2491a1@www.novabbs.org>
	<Rry*LM7Ez@news.chiark.greenend.org.uk>
	<20240311161009.00000923@yahoo.com>
	<vSEHN.170443$JLvf.69218@fx44.iad>
	<20240311171818.000073f6@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Info: dont-email.me; posting-host="20135147cba2d202cd079ad5c3141fdd";
	logging-data="3784551"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/Oafx8bDxB71fHWzEKdlF92H6SHC1JHo4="
Cancel-Lock: sha1:ZSk6L4S2LOVSR5YZuIuDnk1rIsE=
X-Newsreader: Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-w64-mingw32)
Bytes: 5088

On Mon, 11 Mar 2024 17:18:18 +0200
Michael S <already5chosen@yahoo.com> wrote:

> On Mon, 11 Mar 2024 14:50:03 GMT
> scott@slp53.sl.home (Scott Lurndal) wrote:
> 
> > Michael S <already5chosen@yahoo.com> writes:  
> > >On 11 Mar 2024 11:10:15 +0000 (GMT)
> > >Theo Markettos <theom+news@chiark.greenend.org.uk> wrote:
> > >    
> > >> MitchAlsup1 <mitchalsup@aol.com> wrote:    
> > >> > Theo Markettos wrote:      
> > >> > > The bounds have a certain representation limits, because
> > >> > > they're packing 192+ bits of information into a 128 bit
> > >> > > space. This boils down to an alignment granularity: eg if you
> > >> > > allocate a (1MiB+1) byte buffer the bounds might be 1MiB+64
> > >> > > (or whatever, I can't remember what the rounding is at this
> > >> > > size).  malloc() should ensure it doesn't hand out that
> > >> > > memory to somebody else; allocators typically do this anyway
> > >> > > since they use slab allocators which round up the allocation
> > >> > > to a certain number of slabs.      
> > >> > 
> > >> > So how to you "encode" a petaByte array ?? of megaByte structs
> > >> > in a capability ??      
> > >> 
> > >> You create a capability with petabyte-scale bounds.  The
> > >> precision of the bounds may be limited, which means that you
> > >> can't ram something else right up against the end or beginning
> > >> of the array if they aren't sufficiently aligned.  This is in
> > >> practice not a problem: slab allocators will round up your
> > >> address before they allocate the next thing, and most OSes won't
> > >> populate the rounded up space with pages anyway.
> > >> 
> > >> When you take a pointer to an array element, then it has megabyte
> > >> scale bounds and they can be represented with more precision.  If
> > >> your struct elements are of an arbitrary size and packed together
> > >> at the byte level then you either have to live with the bounds
> > >> giving rights to slightly more than a single struct element, or
> > >> you decide that is unacceptable and pad the struct size up to the
> > >> next representable size (just like regular non-packed structs
> > >> enforce certain alignment), and pay a small memory overhead for
> > >> that (<0.25%).  That's a security decision you can make one way
> > >> or another.
> > >> 
> > >> Theo    
> > >
> > >Your time stamp (most likely +0000 part) confuses my Claws
> > >Mail newsreader. I wonder if others see similar problem.
> > >    
> > 
> > xrn on linux is not confused (which is not surprising since
> > linux stores time internally as GMT anyway).
> > 
> > Date: 11 Mar 2024 11:10:15 +0000 (GMT)  
> 
> The issue does not appear to have anything to do with OS. It's all
> about parsing of 'Date' header.
> 
> For example, in your message it looks like:
> Date: Mon, 11 Mar 2024 14:50:03 GMT
> Claws mail understand it.
> 
> In message of Tim Rentsch it looks like:
> Date: Mon, 11 Mar 2024 07:54:07 -0700
> Claws mail understand it.
> 
> In my messages format is the same as in Tim's.
> 
> In messages of Theo the header looks like a mix of yours and ours:
> Date: 11 Mar 2024 11:10:15 +0000 (GMT)
> 
> The wonders of Postel's law.
> 
> 
> 
> 
> 

Another formats that Claws Mail can't handle:

Date: Thu, 18 Jan 24 09:45:05 UTC
User-Agent: Pluto/3.18 (RISC OS/5.29) NewsHound/v1.52-32

Date: Fri, 06 Oct 23 15:40:16 +0000
User-Agent: Nemo/0.999a

Date: Sun, 04 Feb 24 12:39:24 GMT
User-Agent: Newsgrouper 0.3

In all cases the badness of the header (absence of year) is rather
obvious. IMHO, such obvious cases should be rejected by news servers,
but... Postel's Law :(