mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Nikanth Karthikesan <knikanth@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] loop: Update mtime when writing using aops
Date: Thu, 8 Apr 2010 15:15:55 +0100	[thread overview]
Message-ID: <201004081515.56161.tvrtko.ursulin@sophos.com> (raw)
In-Reply-To: <20100408124539.GM10103@kernel.dk>

On Thursday 08 April 2010 13:45:39 Jens Axboe wrote:
> On Thu, Apr 08 2010, Nikanth Karthikesan wrote:
> > Update mtime when writing to backing filesystem using the address space
> > operations write_begin and write_end.
>
> You forgot to include a 'why' :-)
>
> Not that I disagree with the patch, just curious what made you make the
> change.

You mean how the bug was found? I originally reported this problem against
openSUSE 11.2 kernel, where when you have a dm-crypt loop filesystem the
container file modification time does not get updated with use. Consequence
of that is that backup runs would miss the fact container has changed.

Maybe one could argue it is a security feature in this scenario :), but as the
problem turns out to be unrelated to the crypto case, rather contained in the
loop driver itself, it looks like that would not hold.

Tvrtko

Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.

  reply	other threads:[~2010-04-08 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 10:21 Nikanth Karthikesan
2010-04-08 12:45 ` Jens Axboe
2010-04-08 14:15   ` Tvrtko Ursulin [this message]
2010-04-08 19:38     ` Jens Axboe
2010-04-09  5:22       ` Nikanth Karthikesan

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=201004081515.56161.tvrtko.ursulin@sophos.com \
    --to=tvrtko.ursulin@sophos.com \
    --cc=jens.axboe@oracle.com \
    --cc=knikanth@suse.de \
    --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

all inboxes | Powered by JetHome®