Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Jan 15, 2015
  1. pstore: selinux: add security in-core xattr support for rootfs, pstor…

    Mark Salyzyn authored
    …e and debugfs
    - add "rootfs", "pstore" and "debugfs" to list of in-core exceptions
    - change fstype checks to boolean equation
    - change from strncmp to strcmp for checking
    (Cherry Pick from commit 2294d49)
    Signed-off-by: Mark Salyzyn <>
    Bug: 18917345
    Bug: 18935184
    Change-Id: Ib648f30ce4b5d6c96f11465836d6fee89bec1c72
Commits on Jul 8, 2014
  1. net: wireless: bcmdhd: Add WIPHY_WOWLAN_ANY support

    Dmitry Shmidt authored
    Change-Id: I4a9de9ab40f6de2e5ef5830529cfb066d6c75b57
    Signed-off-by: Dmitry Shmidt <>
Commits on Feb 28, 2014
  1. android: base-cfg: enable DM_VERITY (used for secureboot)

    JP Abgrall authored
    Change-Id: I68d769f97ffa76bb45e65d34a96dd7f558c02d08
    Signed-off-by: JP Abgrall <>
    (cherry picked from commit 37cb5be)

    Ashish Sharma authored JP Abgrall committed
    Signed-off-by: Ashish Sharma <>
  3. android: configs: Grab the android/configs from kernel/common

    JP Abgrall authored
    This is a squash of all changes from kernel/common android-3.4 up to
      5e35d66 android: configs: add IPV6 ROUTE INFO
    Change-Id: I848f1865ec7da1dfc3338a3e9d7f944a6f00f2a6
    Signed-off-by: JP Abgrall <>
Commits on Feb 19, 2014
  1. tcp: add a sysctl to config the tcp_default_init_rwnd

    JP Abgrall authored
    The default initial rwnd was hardcoded to 10.
    Now we allow it to be controlled via
    which limits the values from 3 to 100
    This is somewhat needed because ipv6 routes are
    autoconfigured by the kernel.
    See "An Argument for Increasing TCP's Initial Congestion Window"
    Change-Id: I7eac8a0a5133371aea9ecb9aec0b608bd7f2cc57
    Signed-off-by: JP Abgrall <>
Commits on Feb 13, 2014
  1. fix false disconnect due to a signal sent to the reading process

    keunyoung authored JP Abgrall committed
    - In the current implementation, when a signal is sent to the reading process,
      read is cancelled by calling usb_ep_dequeue, which lead into calling
      acc_complete_out with ECONNRESET, but the current logic treats it as
      disconnection, which makes the device inaccessible until cable is actually
    - The fix calls disconnect only when ESHUTDOWN error is passed.
    - If data has already arrived while trying cancelling, the data is marked
      as available, and it will be read out on the next read. This is necessary
      as USB bulk is assumed to guarantee no data loss.
    Signed-off-by: keunyoung <>
Commits on Feb 8, 2014
  1. @stephensmalley

    SELinux: Fix kernel BUG on empty security contexts.

    stephensmalley authored JP Abgrall committed
    Setting an empty security context (length=0) on a file will
    lead to incorrectly dereferencing the type and other fields
    of the security context structure, yielding a kernel BUG.
    As a zero-length security context is never valid, just reject
    all such security contexts whether coming from userspace
    via setxattr or coming from the filesystem upon a getxattr
    request by SELinux.
    Setting a security context value (empty or otherwise) unknown to
    SELinux in the first place is only possible for a root process
    (CAP_MAC_ADMIN), and, if running SELinux in enforcing mode, only
    if the corresponding SELinux mac_admin permission is also granted
    to the domain by policy.  In Fedora policies, this is only allowed for
    specific domains such as livecd for setting down security contexts
    that are not defined in the build host policy.
    [On Android, this can only be set by root/CAP_MAC_ADMIN processes,
    and if running SELinux in enforcing mode, only if mac_admin permission
    is granted in policy.  In Android 4.4, this would only be allowed for
    root/CAP_MAC_ADMIN processes that are also in unconfined domains. In current
    AOSP master, mac_admin is not allowed for any domains except the recovery
    console which has a legitimate need for it.  The other potential vector
    is mounting a maliciously crafted filesystem for which SELinux fetches
    xattrs (e.g. an ext4 filesystem on a SDcard).  However, the end result is
    only a local denial-of-service (DOS) due to kernel BUG.  This fix is
    queued for 3.14.]
    setenforce 0
    touch foo
    setfattr -n security.selinux foo
    Relabeling or removing foo after doing the above may not be possible
    without booting with SELinux disabled.  Any subsequent access to foo
    after doing the above will also trigger the BUG.
    BUG output from Matthew Thode:
    [  473.893141] ------------[ cut here ]------------
    [  473.962110] kernel BUG at security/selinux/ss/services.c:654!
    [  473.995314] invalid opcode: 0000 [#6] SMP
    [  474.027196] Modules linked in:
    [  474.058118] CPU: 0 PID: 8138 Comm: ls Tainted: G      D   I
    3.13.0-grsec #1
    [  474.116637] Hardware name: Supermicro X8ST3/X8ST3, BIOS 2.0
    [  474.149768] task: ffff8805f50cd010 ti: ffff8805f50cd488 task.ti:
    [  474.183707] RIP: 0010:[<ffffffff814681c7>]  [<ffffffff814681c7>]
    [  474.219954] RSP: 0018:ffff8805c0ac3c38  EFLAGS: 00010246
    [  474.252253] RAX: 0000000000000000 RBX: ffff8805c0ac3d94 RCX:
    [  474.287018] RDX: ffff8805e8aac000 RSI: 00000000ffffffff RDI:
    [  474.321199] RBP: ffff8805c0ac3cb8 R08: 0000000000000010 R09:
    [  474.357446] R10: 0000000000000000 R11: ffff8805c567a000 R12:
    [  474.419191] R13: ffff8805c2b74e88 R14: 00000000000001da R15:
    [  474.453816] FS:  00007f2e75220800(0000) GS:ffff88061fc00000(0000)
    [  474.489254] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [  474.522215] CR2: 00007f2e74716090 CR3: 00000005c085e000 CR4:
    [  474.556058] Stack:
    [  474.584325]  ffff8805c0ac3c98 ffffffff811b549b ffff8805c0ac3c98
    [  474.618913]  ffff8805a6202f08 ffff8805c2b74e88 00068800d0464990
    [  474.653955]  ffff8805c0ac3cb8 000700068113833a ffff880606c75060
    [  474.690461] Call Trace:
    [  474.723779]  [<ffffffff811b549b>] ? lookup_fast+0x1cd/0x22a
    [  474.778049]  [<ffffffff81468824>] security_compute_av+0xf4/0x20b
    [  474.811398]  [<ffffffff8196f419>] avc_compute_av+0x2a/0x179
    [  474.843813]  [<ffffffff8145727b>] avc_has_perm+0x45/0xf4
    [  474.875694]  [<ffffffff81457d0e>] inode_has_perm+0x2a/0x31
    [  474.907370]  [<ffffffff81457e76>] selinux_inode_getattr+0x3c/0x3e
    [  474.938726]  [<ffffffff81455cf6>] security_inode_getattr+0x1b/0x22
    [  474.970036]  [<ffffffff811b057d>] vfs_getattr+0x19/0x2d
    [  475.000618]  [<ffffffff811b05e5>] vfs_fstatat+0x54/0x91
    [  475.030402]  [<ffffffff811b063b>] vfs_lstat+0x19/0x1b
    [  475.061097]  [<ffffffff811b077e>] SyS_newlstat+0x15/0x30
    [  475.094595]  [<ffffffff8113c5c1>] ? __audit_syscall_entry+0xa1/0xc3
    [  475.148405]  [<ffffffff8197791e>] system_call_fastpath+0x16/0x1b
    [  475.179201] Code: 00 48 85 c0 48 89 45 b8 75 02 0f 0b 48 8b 45 a0 48
    8b 3d 45 d0 b6 00 8b 40 08 89 c6 ff ce e8 d1 b0 06 00 48 85 c0 49 89 c7
    75 02 <0f> 0b 48 8b 45 b8 4c 8b 28 eb 1e 49 8d 7d 08 be 80 01 00 00 e8
    [  475.255884] RIP  [<ffffffff814681c7>]
    [  475.296120]  RSP <ffff8805c0ac3c38>
    [  475.328734] ---[ end trace f076482e9d754adc ]---
    [sds:  commit message edited to note Android implications and
    to generate a unique Change-Id for gerrit]
    Change-Id: I4d5389f0cfa72b5f59dada45081fa47e03805413
    Reported-by:  Matthew Thode <>
    Signed-off-by: Stephen Smalley <>
    Signed-off-by: Paul Moore <>
Commits on Feb 5, 2014
  1. netfilter: xt_IDLETIMER: Revert to retain the kernel API format.

    Ashish Sharma authored JP Abgrall committed
    Reverted Change-Id: Iaeca5dd2d7878c0733923ae03309a2a7b86979ca
    Change-Id: I0e0a4f60ec14330d8d8d1c5a508fa058d9919e07
    Signed-off-by: Ashish Sharma <>
  2. @rostedt

    SELinux: Fix possible NULL pointer dereference in selinux_inode_permi…

    rostedt authored JP Abgrall committed
    While running stress tests on adding and deleting ftrace instances I hit
    this bug:
      BUG: unable to handle kernel NULL pointer dereference at 0000000000000020
      IP: selinux_inode_permission+0x85/0x160
      PGD 63681067 PUD 7ddbe067 PMD 0
      Oops: 0000 [#1] PREEMPT
      CPU: 0 PID: 5634 Comm: ftrace-test-mki Not tainted 3.13.0-rc4-test-00033-gd2a6dde-dirty #20
      Hardware name:                  /DG965MQ, BIOS MQ96510J.86A.0372.2006.0605.1717 06/05/2006
      task: ffff880078375800 ti: ffff88007ddb0000 task.ti: ffff88007ddb0000
      RIP: 0010:[<ffffffff812d8bc5>]  [<ffffffff812d8bc5>] selinux_inode_permission+0x85/0x160
      RSP: 0018:ffff88007ddb1c48  EFLAGS: 00010246
      RAX: 0000000000000000 RBX: 0000000000800000 RCX: ffff88006dd43840
      RDX: 0000000000000001 RSI: 0000000000000081 RDI: ffff88006ee46000
      RBP: ffff88007ddb1c88 R08: 0000000000000000 R09: ffff88007ddb1c54
      R10: 6e6576652f6f6f66 R11: 0000000000000003 R12: 0000000000000000
      R13: 0000000000000081 R14: ffff88006ee46000 R15: 0000000000000000
      FS:  00007f217b5b6700(0000) GS:ffffffff81e21000(0000) knlGS:0000000000000000
      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033^M
      CR2: 0000000000000020 CR3: 000000006a0fe000 CR4: 00000000000007f0
      Call Trace:
      Code: 84 a1 00 00 00 81 e3 00 20 00 00 89 d8 83 c8 02 40 f6 c6 04 0f 45 d8 40 f6 c6 08 74 71 80 cf 02 49 8b 46 38 4c 8d 4d cc 45 31 c0 <0f> b7 50 20 8b 70 1c 48 8b 41 70 89 d9 8b 78 04 e8 36 cf ff ff
      RIP  selinux_inode_permission+0x85/0x160
      CR2: 0000000000000020
    Investigating, I found that the inode->i_security was NULL, and the
    dereference of it caused the oops.
    in selinux_inode_permission():
    	isec = inode->i_security;
    	rc = avc_has_perm_noaudit(sid, isec->sid, isec->sclass, perms, 0, &avd);
    Note, the crash came from stressing the deletion and reading of debugfs
    files.  I was not able to recreate this via normal files.  But I'm not
    sure they are safe.  It may just be that the race window is much harder
    to hit.
    What seems to have happened (and what I have traced), is the file is
    being opened at the same time the file or directory is being deleted.
    As the dentry and inode locks are not held during the path walk, nor is
    the inodes ref counts being incremented, there is nothing saving these
    structures from being discarded except for an rcu_read_lock().
    The rcu_read_lock() protects against freeing of the inode, but it does
    not protect freeing of the inode_security_struct.  Now if the freeing of
    the i_security happens with a call_rcu(), and the i_security field of
    the inode is not changed (it gets freed as the inode gets freed) then
    there will be no issue here.  (Linus Torvalds suggested not setting the
    field to NULL such that we do not need to check if it is NULL in the
    permission check).
    Note, this is a hack, but it fixes the problem at hand.  A real fix is
    to restructure the destroy_inode() to call all the destructor handlers
    from the RCU callback.  But that is a major job to do, and requires a
    lot of work.  For now, we just band-aid this bug with this fix (it
    works), and work on a more maintainable solution in the future.
    Signed-off-by: Steven Rostedt <>
    Signed-off-by: Linus Torvalds <>
Commits on Feb 3, 2014
  1. nf: xt_qtaguid: fix handling for cases where tunnels are used.

    JP Abgrall authored
    * fix skb->dev vs par->in/out
    When there is some forwarding going on, it introduces extra state
    around devs associated with xt_action_param->in/out and sk_buff->dev.
       par->in and par->out are both set, or
       skb->dev and par->out are both set (and different)
    This would lead qtaguid to make the wrong assumption about the
    direction and update the wrong device stats.
    Now we rely more on par->in/out.
    * Fix handling when qtaguid is used as "owner"
    When qtaguid is used as an owner module, and sk_socket->file is
    not there (happens when tunnels are involved), it would
    incorrectly do a tag stats update.
    * Correct debug messages.
    Bug: 11687690
    Change-Id: I2b1ff8bd7131969ce9e25f8291d83a6280b3ba7f
    Signed-off-by: JP Abgrall <>
    (cherry picked from commit 2b71479)
Commits on Jan 29, 2014
  1. @hannes @lcolitti

    ping: prevent NULL pointer dereference on write to msg_name

    hannes authored lcolitti committed
    A plain read() on a socket does set msg->msg_name to NULL. So check for
    NULL pointer first.
    [Backport of net-next cf970c0]
    Bug: 12780426
    Change-Id: I29d9cb95ef05ec76d37517e01317f4a29e60931c
    Signed-off-by: Hannes Frederic Sowa <>
    Signed-off-by: David S. Miller <>
    Signed-off-by: Lorenzo Colitti <>
Commits on Sep 4, 2013
  1. net: wireless: bcmdhd: Clean scan status if request is empty

    Dmitry Shmidt authored
    Change-Id: I1c00b5a84846faf316305f57a6a74ded2288a6fd
    Signed-off-by: Dmitry Shmidt <>
Commits on Aug 22, 2013
  1. net: wireless: bcmdhd: Inject EID value if it has 0 length

    Dmitry Shmidt authored
    Change-Id: Ifd102bee45e1a1e04ba015c39631a741ca74d6ee
    Signed-off-by: Dmitry Shmidt <>
Commits on Aug 21, 2013
  1. net: wireless: bcmdhd: Fix roaming to hidden AP

    Dmitry Shmidt authored
    Change-Id: Id64d12962049833e19705fbe109ef04b60014079
    Signed-off-by: Dmitry Shmidt <>
Commits on Aug 5, 2013
  1. @lcolitti

    net: ipv6: fix wrong ping_v6_sendmsg return value

    lcolitti authored
    [net-next commit fbfe80c]
    ping_v6_sendmsg currently returns 0 on success. It should return
    the number of bytes written instead.
    Bug: 9469865
    Change-Id: I82b7d3a37ba91ad24e6dbd97a4880745ce16ad31
    Signed-off-by: Lorenzo Colitti <>
    Signed-off-by: David S. Miller <>
  2. @lcolitti

    net: ipv6: add missing lock in ping_v6_sendmsg

    lcolitti authored
    [net-next commit a1bdc45]
    Bug: 9469865
    Change-Id: I480f8ce95956dd8f17fbbb26dc60cc162f8ec933
    Signed-off-by: Lorenzo Colitti <>
    Signed-off-by: David S. Miller <>
Commits on Jul 23, 2013
  1. net: wireless: bcmdhd: Enable p2p support bits for p2p device

    Dmitry Shmidt authored
    Change-Id: Ie3537aaeecdbbddb5219b41c42f2f6ac5d85f5b4
    Signed-off-by: Dmitry Shmidt <>
Commits on Jun 26, 2013
  1. ping: always initialize ->sin6_scope_id and ->sin6_flowinfo

    Cong Wang authored jp abgrall committed
    [net-next commit c26d6b4]
    If we don't need scope id, we should initialize it to zero.
    Same for ->sin6_flowinfo.
    Change-Id: I28e4bc9593e76fc3434052182466fab4bb8ccf3a
    Cc: Lorenzo Colitti <>
    Cc: David S. Miller <>
    Signed-off-by: Cong Wang <>
    Acked-by: Lorenzo Colitti <>
    Signed-off-by: David S. Miller <>
  2. @lcolitti

    net: ipv6: Add IPv6 support to the ping socket.

    lcolitti authored JP Abgrall committed
    [backport of net-next 6d0bfe2]
    This adds the ability to send ICMPv6 echo requests without a
    raw socket. The equivalent ability for ICMPv4 was added in
    Instead of having separate code paths for IPv4 and IPv6, make
    most of the code in net/ipv4/ping.c dual-stack and only add a
    few IPv6-specific bits (like the protocol definition) to a new
    net/ipv6/ping.c. Hopefully this will reduce divergence and/or
    duplication of bugs in the future.
    - Setting options via ancillary data (e.g., using IPV6_PKTINFO
      to specify the outgoing interface) is not yet supported.
    - There are no separate security settings for IPv4 and IPv6;
      everything is controlled by /proc/net/ipv4/ping_group_range.
    - The proc interface does not yet display IPv6 ping sockets
    Tested with a patched copy of ping6 and using raw socket calls.
    Compiles and works with all of CONFIG_IPV6={n,m,y}.
    Change-Id: Ia359af556021344fc7f890c21383aadf950b6498
    Signed-off-by: Lorenzo Colitti <>
    Signed-off-by: David S. Miller <>
    [ backported to 3.0]
    Signed-off-by: Lorenzo Colitti <>
  3. @hannes

    ipv6: introdcue __ipv6_addr_needs_scope_id and ipv6_iface_scope_id he…

    hannes authored jp abgrall committed
    …lper functions
    [net-next commit b7ef213]
    __ipv6_addr_needs_scope_id checks if an ipv6 address needs to supply
    a 'sin6_scope_id != 0'. 'sin6_scope_id != 0' was enforced in case
    of link-local addresses. To support interface-local multicast these
    checks had to be enhanced and are now consolidated into these new helper
    a) migrated to struct ipv6_addr_props
    a) reverted changes for ipv6_addr_props
    b) test for address type instead of comparing scope
    a) unchanged
    Change-Id: Id6fc54cec61f967928e08a9eba4f857157d973a3
    Suggested-by: YOSHIFUJI Hideaki <>
    Cc: YOSHIFUJI Hideaki <>
    Acked-by: YOSHIFUJI Hideaki <>
    Signed-off-by: Hannes Frederic Sowa <>
    Acked-by: YOSHIFUJI Hideaki <>
    Signed-off-by: David S. Miller <>
  4. misc: uidstat: avoid create_stat() race and blockage.

    JP Abgrall authored
    * create_stat() race would lead to:
      [   58.132324] proc_dir_entry 'uid_stat/10061' already registered
    * blocking kmalloc reported by sbranden
    Signed-off-by: JP Abgrall <>
Commits on Jun 12, 2013
  1. @toddpoynor

    cpufreq: interactive: avoid underflow on active time calculation

    Minsung Kim authored toddpoynor committed
    Check for idle time delta less than elapsed time delta, avoid
    underflow computing active time.
    Change-Id: I3e4c6ef1ad794eec49ed379c0c50fa727fd6ad28
    Signed-off-by: Minsung Kim <>
  2. @toddpoynor

    cpufreq: interactive: reduce chance of zero time delta on load eval

    toddpoynor authored
    Reschedule load sampling timer after timestamp of sample start taken,
    hold spinlock across entire sequence to avoid preemption.  Avoid the
    WARN for zero time delta in the load sampling timer function.
    Change-Id: Idc10a756f09141decb6df92669521a1ebf0dbc10
    Signed-off-by: Todd Poynor <>
  3. @toddpoynor

    cpufreq: interactive: handle errors from cpufreq_frequency_table_target

    toddpoynor authored
    Add checks for error return from cpufreq_frequency_table_target, and be
    less noisy on the existing call with an error check.  CPU hotplug and
    system shutdown may cause this call to return -EINVAL.
    Bug: 8613560
    Change-Id: Id78d8829920462c0db1c7e14e717d91740d6cb44
    Signed-off-by: Todd Poynor <>
Commits on Jun 5, 2013
  1. @toddpoynor

    ashmem: avoid deadlock between read and mmap calls

    toddpoynor authored
    Avoid holding ashmem_mutex across code that can page fault.  Page faults
    grab the mmap_sem for the process, which are also held by mmap calls
    prior to calling ashmem_mmap, which locks ashmem_mutex.  The reversed
    order of locking between the two can deadlock.
    The calls that can page fault are read() and the ASHMEM_SET_NAME and
    ASHMEM_GET_NAME ioctls.  Move the code that accesses userspace pages
    outside the ashmem_mutex.
    Bug: 9261835
    Change-Id: If1322e981d29c889a56cdc9dfcbc6df2729a45e9
    Signed-off-by: Todd Poynor <>
Commits on May 28, 2013
  1. ARM: Allow SoCs to enable scatterlist chaining

    Russell King authored Rom Lemarchand committed
    Allow SoCs to enable the scatterlist chaining support, which allows
    scatterlist tables to be broken up into smaller allocations.
    As support for this feature depends on the implementation details of
    the users of the scatterlists, we can't enable this globally without
    auditing all the users, which is a very big task.  Instead, let SoCs
    progressively switch over to using this.
    SoC drivers using scatterlists and SoC DMA implementations need
    auditing before this option can be enabled for the SoC.
    Signed-off-by: Russell King <>
  2. trace/events: fix gpu event timestamp formatting

    Jamie Gennis authored Rom Lemarchand committed
    This change fixes the how the gpu_sched_switch timestamp field is formatted.
    Signed-off-by: Jamie Gennis <>
    Change-Id: I273234935254ed15772c9e561c9af20e480004ae
  3. trace/events: add gpu trace events

    Jamie Gennis authored Rom Lemarchand committed
    Change-Id: I0607b9c776acf61cb796b8572cf8cfb8b2dc1377
    Signed-off-by: Jamie Gennis <>
  4. gpu: ion: Fix bug in ion shrinker

    Rebecca Schultz Zavin authored Rom Lemarchand committed
    The high variable was sometimes used uninitialized
    Change-Id: I2f51413fd2d063fdff325047e824dc8c749d9e0a
    Signed-off-by: Rebecca Schultz Zavin <>
  5. gpu: ion: ion_chunk_heap: Zero chunk heap memory at creation time

    Rebecca Schultz Zavin authored Rom Lemarchand committed
    Allocations from the ion heap need to be zeroed to protect userspace
    from seeing memory belonging to other processes.  First allocations
    from this heap were not zero'd allowing users to see memory from other
    processes on a warm reset.
    Change-Id: I524a7b79cb76c390c870fcf8b30d213185fc85a0
    Signed-off-by: Rebecca Schultz Zavin <>
  6. gpu: ion: fix kfree/list_del order

    JP Abgrall authored Rom Lemarchand committed
    With CONFIG_SLUB_DEBUG_ON it would panic during
    Signed-off-by: JP Abgrall <>
  7. gpu: ion: Make ion_free asynchronous

    Rebecca Schultz Zavin authored Rom Lemarchand committed
    Add the ability for a heap to free buffers asynchrounously.  Freed buffers
    are placed on a free list and freed from a low priority background thread.
    If allocations from a particular heap fail, the free list is drained.  This
    patch also enable asynchronous frees from the chunk heap.
    Change-Id: Idfdbc8608b6cbd9e27d2e31ea4fd84fea9f69f7d
    Signed-off-by: Rebecca Schultz Zavin <>
  8. gpu: ion: Add support for sharing buffers with dma buf kernel handles

    Johan Mossberg authored Rom Lemarchand committed
    Currently ion can only share buffers with dma buf fd's. Fd's can not be
    used inside the kernel as they are process specific so support for
    sharing buffers with dma buf kernel handles is needed to support kernel
    only use cases. An example use case could be a GPU driver using ion
    that wants to share its output buffers with a 3d party display
    controller driver supporting dma buf.
    Change-Id: If1b3753ddbd5b44c5a3e622055d5473e16fc1c48
    Signed-off-by: Johan Mossberg <>
  9. gpu: ion: Only flush buffers in the chunk heap if they were used cached

    Rebecca Schultz Zavin authored Rom Lemarchand committed
    Change-Id: I4ffcf81a6be09e968310bbd882fb017415d61b48
    Signed-off-by: Rebecca Schultz Zavin <>
Something went wrong with that request. Please try again.