Re: [PATCH] [afs] Add lock annotations to afs_proc_cell_servers_{start,stop}

Josh Triplett <[email protected]> wrote:

> afs_proc_cell_servers_start acquires a lock, and afs_proc_cell_servers_stop
> releases that lock.  Add lock annotations to these two functions so that
> sparse can check callers for lock pairing, and so that sparse will not
> complain about these functions since they intentionally use locks in this
> manner.

Looks reasonable, though I'm surprised you can get this sort of checking to
work in sparse.

Acked-By: David Howells <[email protected]>
-
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] [afs] Add lock annotations to afs_proc_cell_servers_{start,stop}
    • From: Josh Triplett <[email protected]>

• Prev by Date: RE: [PATCH] CCISS: Don't print driver version until we actually find a device
• Next by Date: Re: hwrng on 82801EB/ER (ICH5/ICH5R) fails rngtest checks
• Previous by thread: [PATCH] [afs] Add lock annotations to afs_proc_cell_servers_{start,stop}
• Next by thread: [PATCH] [fuse] Add lock annotations to request_end and fuse_read_interrupt
• 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]