Re: [PATCH] Rework /proc/locks via seq_files and seq_list helpers (v2)

Pavel Emelyanov wrote:
> Currently /proc/locks is shown with a proc_read function, but
> its behavior is rather complex as it has to manually handle
> current offset and buffer length. On the other hand, files 
> that show objects from lists can be easily reimplemented using
> the sequential files and the seq_list_XXX() helpers.
> 
> This saves (as usually) 16 lines of code and more than 200 from
> the .text section.
> 
> This patch looks rather ugly, as diff often uses curly braces
> as not-changed lines, but I haven't managed to organize the 
> code to make diff look better. Except for move the whole proc
> related stuff upper/lower in the locks.c file...
> 
> Fixed the problem, spotted by J. Bruce Fields, about the fl
> variable reuse.
> 
> Signed-off-by: Pavel Emelyanov <[email protected]>

OOPS! Please disregard, wrong comment was copied :(
-
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/

---

• References:
  • [PATCH] Rework /proc/locks via seq_files and seq_list helpers (v2)
    • From: Pavel Emelyanov <[email protected]>

• Prev by Date: [PATCH] Rework /proc/locks via seq_files and seq_list helpers (v2)
• Next by Date: [PATCH] Fix potential OOPS in generic_setlease() (v2)
• Previous by thread: [PATCH] Rework /proc/locks via seq_files and seq_list helpers (v2)
• Next by thread: [PATCH] Fix potential OOPS in generic_setlease() (v2)
• 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]