From: phcoder <phcoder@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH]: grub: Fix ofdisk disk cache corruption.
Date: Mon, 13 Apr 2009 03:09:20 +0200 [thread overview]
Message-ID: <49E290C0.9030700@gmail.com> (raw)
In-Reply-To: <20090412.180208.121488309.davem@davemloft.net>
David Miller wrote:
> From: phcoder <phcoder@gmail.com>
> Date: Sun, 12 Apr 2009 12:44:10 +0200
>
>> David Miller wrote:
>>> From: Pavel Roskin <proski@gnu.org>
>>> Date: Sun, 12 Apr 2009 02:29:15 -0400
>>>
>>>> On Sat, 2009-04-11 at 01:08 -0700, David Miller wrote:
>>> I think fixing disk cache corruption is more important than
>>> arguing over the distribution properties of the hash function
>>> I have choosen.
>>>
>> Yes, but weak hash has exactly the same problem, just on other systems
>
> Nobody has even shown that the hash is actually weak or
> not effective in any particular case, theoretical or otherwise.
>
> That's why it frustrates me that we're discussing this at all.
>
> "That hash might not be good, only 3 bits of entropy" meanwhile
> we have a disk cache corrupt bug still unfixed.
>
> Can't we bicker about these kinds of issues after the bug is
> fixed? And also, after some proof is given that the hash
> matters at all.
>
> Priorities are definitely wrong here.
>
>>>> If you can save the device names, then there is no point in using
>>>> hashes. You can use (long)devpath.
>>> Sure we need the hash, to find path entries we've saved beforehand.
>> You can maintain a table of devpathes in cache and use the index in
>> this table as id. This way is the safest
>
> Ummm, that's essentially what my code does, except that the "index"
> is the address of the cached path entry itself.
Sorry I totally misread your code. Now it's fine
--
Regards
Vladimir 'phcoder' Serbinenko
next prev parent reply other threads:[~2009-04-13 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 8:08 [PATCH]: grub: Fix ofdisk disk cache corruption David Miller
2009-04-12 6:29 ` Pavel Roskin
2009-04-12 8:01 ` David Miller
2009-04-12 10:44 ` phcoder
2009-04-13 1:02 ` David Miller
2009-04-13 1:09 ` phcoder [this message]
2009-04-13 6:42 ` David Miller
2009-04-12 21:01 ` Pavel Roskin
2009-04-13 1:04 ` David Miller
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=49E290C0.9030700@gmail.com \
--to=phcoder@gmail.com \
--cc=davem@davemloft.net \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.