| 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
| ||
|
Message-ID: <20061016062049.GE23144@vianova.fi> Date: Mon, 16 Oct 2006 09:20:49 +0300 From: Ville Herva <vherva@...nova.fi> To: Andries Brouwer <Andries.Brouwer@....nl> Cc: Neil Brown <neilb@...e.de>, linux-kernel@...r.kernel.org Subject: Re: Why aren't partitions limited to fit within the device? On Mon, Oct 16, 2006 at 08:02:27AM +0200, you [Andries Brouwer] wrote: > On Mon, Oct 16, 2006 at 09:50:15AM +1000, Neil Brown wrote: > > On Sunday October 15, vherva@...nova.fi wrote: > > > > I wonder if there's ever a change the kernel partition detection code could > > > _write_ on the disk, even when there's really no partition table? > > > > No, kernel partition detection never writes. > > There is something else that writes, however, that I have gotten complaints about. > (But I have not investigated.) > People doing forensics take a copy of a disk and want to preserve > that copy as-is, never changing a single bit, only looking at it. > But it is reported that also when a partition is mounted read-only, > the journaling code of ext3 will write to the journal. Yes, that's (sort of) known. As in "mentioned on lkml" - perhaps even in some documentation. In this case, the fs was ext2, though, and the problem occurred even when the fs was never mounted and the raid device was never started. -- v -- v@....fi - 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/
Powered by blists - more mailing lists