From: "Jörn Engel" <joern@logfs.org>
To: Linus <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Please pull logfs tree for fixes
Date: Wed, 21 Apr 2010 14:19:32 +0200 [thread overview]
Message-ID: <20100421121932.GA18441@logfs.org> (raw)
Another set of fixes. Two of them are security relevant. But given
that an attacker needs mount access and few people have logfs compiled
in, that's unlikely to be a huge issue.
gc.c | 8 ++++++
journal.c | 29 ++++++++++++++---------
logfs.h | 15 ++++++++++--
readwrite.c | 75 +++++++++++++++++++++++++++++++++---------------------------
segment.c | 8 ------
super.c | 11 +++++++-
6 files changed, 91 insertions(+), 55 deletions(-)
Jörn
--
More computing sins are committed in the name of efficiency (without
necessarily achieving it) than for any other single reason - including
blind stupidity.
-- W. A. Wulf
next reply other threads:[~2010-04-21 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 12:19 Jörn Engel [this message]
2010-04-21 14:09 ` Please pull logfs tree for fixes Daniel Walker
2010-04-21 14:24 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2010-05-17 17:19 Jörn Engel
2010-05-17 20:54 ` Linus Torvalds
2010-03-06 21:04 Please pull logfs tree Jörn Engel
2010-03-30 7:22 ` Please pull logfs tree for fixes Jörn Engel
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=20100421121932.GA18441@logfs.org \
--to=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.