From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mike Waychison <mikew@google.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/1] Drop CAP_SYS_RAWIO requirement for FIBMAP
Date: Fri, 26 Oct 2007 01:43:25 +0100 [thread overview]
Message-ID: <20071026014325.14f5fe1c@the-village.bc.nu> (raw)
In-Reply-To: <47213668.50907@google.com>
> I found Chris's comment about negative block numbers, I'll send a patch
> out for that.
>
> You mentioned back in 99 about racing with ftruncate. Is it sufficient
> to mutex_lock(i_mutex) and down_read(i_alloc_sem)?
One for the fs guys. That code has changed far beyond anything I
understand any more 8)
next prev parent reply other threads:[~2007-10-26 0:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 23:06 Mike Waychison
2007-10-26 0:22 ` Alan Cox
2007-10-26 0:35 ` Mike Waychison
2007-10-26 0:43 ` Alan Cox [this message]
2007-10-26 21:55 ` Jason Uhlenkott
2007-10-26 21:59 ` Mike Waychison
2007-10-26 22:40 ` Jason Uhlenkott
2007-10-26 22:53 ` Mike Waychison
2007-10-29 19:08 ` Pavel Machek
2007-11-01 14:51 ` Ric Wheeler
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=20071026014325.14f5fe1c@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
/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®