Re: [Patch 14/18] fs/logfs/segment.c

On Sunday 03 June 2007, Jörn Engel wrote:
> +static DEFINE_MUTEX(compr_mutex);
> +

It seems you define a static compre_mutex in both segment.c and in compr.c,
and always lock them both at the same time. Is that a correct observation?
Is it intentional, or an oversight on your side?

	Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [Patch 14/18] fs/logfs/segment.c
    • From: Jörn Engel <[email protected]>

• References:
  • LogFS take four
    • From: Jörn Engel <[email protected]>
  • [Patch 14/18] fs/logfs/segment.c
    • From: Jörn Engel <[email protected]>

• Prev by Date: Re: LogFS take four
• Next by Date: Re: Define CONFIG_BOUNCE to avoid useless inclusion of bounce buffer logic.
• Previous by thread: [Patch 14/18] fs/logfs/segment.c
• Next by thread: Re: [Patch 14/18] fs/logfs/segment.c
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]