linux-kernel - Re: libata & no PCI: dma_[un]map

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070605154157.GH31565@havoc.gtf.org>
Date:	Tue, 5 Jun 2007 11:41:57 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Russell King <rmk+lkml@....linux.org.uk>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Christoph Hellwig <hch@...radead.org>,
	David Miller <davem@...emloft.net>, mroos@...ux.ee,
	linux-kernel@...r.kernel.org
Subject: Re: libata & no PCI: dma_[un]map_single undefined

On Tue, Jun 05, 2007 at 04:18:47PM +0100, Russell King wrote:
> Meanwhile you decide that you have a right over _MY_ personal preferences.
> It's the same argument I'm afraid, just a different point of view.  If
> _you_ do not wish to abide by the header then turn off that feature in
> your mailer.  That's _your_ preference and one which _you_ can set.

That clearly doesn't fix the MUAs of everyone else, which has the
stated behavior:  if Mail-Followup-To is present, stuff everyone into
the To header.  And who originates this header?

It's a broken behavior overall, and in a sane world, it would excise you
from the To: header, and leave everyone else on CC as per normal MUA
standards.  But it's not a sane world :)

As such, it is -your- responsibility to make sure breakage does not
occur, since the breakage is originated from -your- setup.

	Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/