From: Christoph Hellwig <hch@lst.de>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: CAN-2003-0018 vs 2.6?
Date: Mon, 29 Mar 2004 15:15:36 +0200 [thread overview]
Message-ID: <20040329131536.GA6296@lst.de> (raw)
CAN-2003-0018 (Linux O_DIRECT Direct Input/Output Information Leak
Vulnerability) is still not fixed in mainline 2.6.
Last time I pinged you you said you didn't like the fixes but we're
getting to the point where 2.6 gets seriously used and we should start
to care. In fact SuSE has been adding the patches to their tree now
which means an direct I/O API change which is kinda messy to maintain
for XFS (which isn't even affected by the vulnerability due to it's own
locking) that's supposed to supply vendors with uptodas.
So any plans to gets this in?
next reply other threads:[~2004-03-29 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 13:15 Christoph Hellwig [this message]
2004-03-29 18:50 ` CAN-2003-0018 vs 2.6? Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040329131536.GA6296@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox