{"push_id":1207407866,"size":21,"distinct_size":21,"ref":"refs/heads/master-GD","head":"027410c88e74ecd246ecaef98e5f4d70ae0897b8","before":"2ee30e541796c7613f1ba0ea4ef5c8ac859e970a","commits":[{"sha":"fa6669c14007f0d8c3faf0c7b365b11c1b5e5bfb","author":{"name":"gsstudios","email":"1f100d5dce64d598f1515e4b571bcc5c73a49e3f@exemail.com.au"},"message":"LZ4 support on the ZRAM thanks to @chhapil","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/fa6669c14007f0d8c3faf0c7b365b11c1b5e5bfb"},{"sha":"6e5c35cb9cf9413b32546817f2797726d968db1f","author":{"name":"gsstudios","email":"1f100d5dce64d598f1515e4b571bcc5c73a49e3f@exemail.com.au"},"message":"Synced chhapil's zram updates","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/6e5c35cb9cf9413b32546817f2797726d968db1f"},{"sha":"a29a1dd2d9df61046f2a8f9f497eb4fd255e8df3","author":{"name":"gsstudios","email":"1f100d5dce64d598f1515e4b571bcc5c73a49e3f@exemail.com.au"},"message":"Set lz4 as the default algorithm for zram","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/a29a1dd2d9df61046f2a8f9f497eb4fd255e8df3"},{"sha":"55993915e286cdeacbe9fa2f8852a9067d089156","author":{"name":"Sergey Senozhatsky","email":"570a3d76c58b9b54de6bb70914e873361b66b749@gmail.com"},"message":"zram: cut trailing newline in algorithm name\n\nSupplied sysfs values sometimes contain new-line symbols (echo vs.  echo\n-n), which we also copy as a compression algorithm name.  it works fine\nwhen we lookup for compression algorithm, because we use sysfs_streq()\nwhich takes care of new line symbols.  however, it doesn't look nice when\nwe print compression algorithm name if zcomp_create() failed:\n\n zram: Cannot initialise LXZ\n            compressing backend\n\ncut trailing new-line, so the error string will look like\n\n  zram: Cannot initialise LXZ compressing backend\n\nwe also now can replace sysfs_streq() in zcomp_available_show() with\nstrcmp().\n\nSigned-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCc: Minchan Kim <minchan@kernel.org>\nCc: Nitin Gupta <ngupta@vflare.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/55993915e286cdeacbe9fa2f8852a9067d089156"},{"sha":"27b58c83ee1c8539bd25cb2b555ceedccef41653","author":{"name":"Sergey Senozhatsky","email":"9251ceca1068cc8334161fa91b1f6065a5ee8fa4@gmail.com"},"message":"zram: check comp algorithm availability earlier\n\nImprovement idea by Marcin Jabrzyk.\n\ncomp_algorithm_store() silently accepts any supplied algorithm name,\nbecause zram performs algorithm availability check later, during the\ndevice configuration phase in disksize_store() and emits the following\nerror:\n\n  \"zram: Cannot initialise %s compressing backend\"\n\nthis error line is somewhat generic and, besides, can indicate a failed\nattempt to allocate compression backend's working buffers.\n\nadd algorithm availability check to comp_algorithm_store():\n\n  echo lzz > /sys/block/zram0/comp_algorithm\n  -bash: echo: write error: Invalid argument\n\nSigned-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nReported-by: Marcin Jabrzyk <m.jabrzyk@samsung.com>\nAcked-by: Minchan Kim <minchan@kernel.org>\nCc: Nitin Gupta <ngupta@vflare.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/27b58c83ee1c8539bd25cb2b555ceedccef41653"},{"sha":"7df8def1824fe75571ed973364c34161c86f0074","author":{"name":"Luis Henriques","email":"7a5998d586aec087b711f42268c96e34e1468fe0@canonical.com"},"message":"zram: fix possible use after free in zcomp_create()\n\nzcomp_create() verifies the success of zcomp_strm_{multi,single}_create()\nthrough comp->stream, which can potentially be pointing to memory that\nwas freed if these functions returned an error.\n\nWhile at it, replace a 'ERR_PTR(-ENOMEM)' by a more generic\n'ERR_PTR(error)' as in the future zcomp_strm_{multi,siggle}_create()\ncould return other error codes.  Function documentation updated\naccordingly.\n\nFixes: beca3ec71fe5 (\"zram: add multi stream functionality\")\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>\nAcked-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nAcked-by: Minchan Kim <minchan@kernel.org>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/7df8def1824fe75571ed973364c34161c86f0074"},{"sha":"269f3916378d588ab57e1a93c1eeaa3525a9ba94","author":{"name":"Weijie Yang","email":"8c97edccb1d93792b9d0c97c45d654274c724617@samsung.com"},"message":"zram: correct offset usage in zram_bio_discard\n\nWe want to skip the physical block(PAGE_SIZE) which is partially covered\nby the discard bio, so we check the remaining size and subtract it if\nthere is a need to goto the next physical block.\n\nThe current offset usage in zram_bio_discard is incorrect, it will cause\nits upper filesystem breakdown.  Consider the following scenario:\n\nOn some architecture or config, PAGE_SIZE is 64K for example, filesystem\nis set up on zram disk without PAGE_SIZE aligned, a discard bio leads to a\noffset = 4K and size=72K, normally, it should not really discard any\nphysical block as it partially cover two physical blocks.  However, with\nthe current offset usage, it will discard the second physical block and\nfree its memory, which will cause filesystem breakdown.\n\nThis patch corrects the offset usage in zram_bio_discard.\n\nSigned-off-by: Weijie Yang <weijie.yang@samsung.com>\nCc: Minchan Kim <minchan@kernel.org>\nCc: Nitin Gupta <ngupta@vflare.org>\nAcked-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nCc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCc: Bob Liu <bob.liu@oracle.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/269f3916378d588ab57e1a93c1eeaa3525a9ba94"},{"sha":"2f8fa768eb47b29b1b851d3cd941f4146a011ac5","author":{"name":"Minchan Kim","email":"513909c15f9d22f3704dca2f86978b287731f351@kernel.org"},"message":"zram: revalidate disk after capacity change\n\nAlexander reported mkswap on /dev/zram0 is failed if other process is\nopening the block device file.\n\nStep is as follows,\n\n0. Reset the unused zram device.\n1. Use a program that opens /dev/zram0 with O_RDWR and sleeps\n   until killed.\n2. While that program sleeps, echo the correct value to\n   /sys/block/zram0/disksize.\n3. Verify (e.g. in /proc/partitions) that the disk size is applied\n   correctly. It is.\n4. While that program still sleeps, attempt to mkswap /dev/zram0.\n   This fails: mkswap: error: swap area needs to be at least 40 KiB\n\nWhen I investigated, the size get by ioctl(fd, BLKGETSIZE64, xxx) on\nmkswap to get a size of blockdev was zero although zram0 has right size by\n2.\n\nThe reason is zram didn't revalidate disk after changing capacity so that\nsize of blockdev's inode is not uptodate until all of file is close.\n\nThis patch should fix the BUG.\n\nSigned-off-by: Minchan Kim <minchan@kernel.org>\nReported-by: Alexander E. Patrakov <patrakov@gmail.com>\nTested-by: Alexander E. Patrakov <patrakov@gmail.com>\nReviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCc: Nitin Gupta <ngupta@vflare.org>\nAcked-by: Jerome Marchand <jmarchan@redhat.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/2f8fa768eb47b29b1b851d3cd941f4146a011ac5"},{"sha":"9ca27b3293ccda7857b1b1bebef7d337a341ffdf","author":{"name":"Minchan Kim","email":"513909c15f9d22f3704dca2f86978b287731f351@kernel.org"},"message":"zram: avoid lockdep splat by revalidate_disk\n\nSasha reported lockdep warning [1] introduced by [2].\n\nIt could be fixed by doing disk revalidation out of the init_lock.  It's\nokay because disk capacity change is protected by init_lock so that\nrevalidate_disk always sees up-to-date value so there is no race.\n\n[1] https://lkml.org/lkml/2014/7/3/735\n[2] zram: revalidate disk after capacity change\n\nFixes 2e32baea46ce (\"zram: revalidate disk after capacity change\").\n\nSigned-off-by: Minchan Kim <minchan@kernel.org>\nReported-by: Sasha Levin <sasha.levin@oracle.com>\nCc: \"Alexander E. Patrakov\" <patrakov@gmail.com>\nCc: Nitin Gupta <ngupta@vflare.org>\nCc: Jerome Marchand <jmarchan@redhat.com>\nCc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCC: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/9ca27b3293ccda7857b1b1bebef7d337a341ffdf"},{"sha":"6de22d27dd23b1963c1766a27c672816a80ef5d2","author":{"name":"Minchan Kim","email":"513909c15f9d22f3704dca2f86978b287731f351@kernel.org"},"message":"zram: use size_t instead of u16\n\nSome architectures (eg, hexagon and PowerPC) could use PAGE_SHIFT of 16\nor more.  In these cases u16 is not sufficiently large to represent a\ncompressed page's size so use size_t.\n\nSigned-off-by: Minchan Kim <minchan@kernel.org>\nReported-by: Weijie Yang <weijie.yang@samsung.com>\nAcked-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCc: Jerome Marchand <jmarchan@redhat.com>\nCc: Nitin Gupta <ngupta@vflare.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/6de22d27dd23b1963c1766a27c672816a80ef5d2"},{"sha":"25951d2ff8c73e49456d8537543aaeb00a624a34","author":{"name":"Sergey Senozhatsky","email":"9251ceca1068cc8334161fa91b1f6065a5ee8fa4@gmail.com"},"message":"zram: rename struct `table' to `zram_table_entry'\n\nAndrew Morton has recently noted that `struct table' actually represents\ntable entry and, thus, should be renamed.  Rename to `zram_table_entry'.\n\nSigned-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCc: Minchan Kim <minchan@kernel.org>\nCc: Nitin Gupta <ngupta@vflare.org>\nCc: Weijie Yang <weijie.yang@samsung.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/25951d2ff8c73e49456d8537543aaeb00a624a34"},{"sha":"dcc3e4ca8400ba55ea85708bc36c9392ac654350","author":{"name":"Sergey Senozhatsky","email":"9251ceca1068cc8334161fa91b1f6065a5ee8fa4@gmail.com"},"message":"zram: remove unused SECTOR_SIZE define\n\nDrop SECTOR_SIZE define, because it's not used.\n\nSigned-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCc: Minchan Kim <minchan@kernel.org>\nCc: Nitin Gupta <ngupta@vflare.org>\nCc: Weijie Yang <weijie.yang@samsung.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/dcc3e4ca8400ba55ea85708bc36c9392ac654350"},{"sha":"e6015473fdcead1cb19d54112e2dda6d2689e587","author":{"name":"Weijie Yang","email":"8c97edccb1d93792b9d0c97c45d654274c724617@samsung.com"},"message":"zram: replace global tb_lock with fine grain lock\n\nCurrently, we use a rwlock tb_lock to protect concurrent access to the\nwhole zram meta table.  However, according to the actual access model,\nthere is only a small chance for upper user to access the same\ntable[index], so the current lock granularity is too big.\n\nThe idea of optimization is to change the lock granularity from whole\nmeta table to per table entry (table -> table[index]), so that we can\nprotect concurrent access to the same table[index], meanwhile allow the\nmaximum concurrency.\n\nWith this in mind, several kinds of locks which could be used as a\nper-entry lock were tested and compared:\n\nTest environment:\nx86-64 Intel Core2 Q8400, system memory 4GB, Ubuntu 12.04,\nkernel v3.15.0-rc3 as base, zram with 4 max_comp_streams LZO.\n\niozone test:\niozone -t 4 -R -r 16K -s 200M -I +Z\n(1GB zram with ext4 filesystem, take the average of 10 tests, KB/s)\n\n      Test       base      CAS    spinlock    rwlock   bit_spinlock\n-------------------------------------------------------------------\n Initial write  1381094   1425435   1422860   1423075   1421521\n       Rewrite  1529479   1641199   1668762   1672855   1654910\n          Read  8468009  11324979  11305569  11117273  10997202\n       Re-read  8467476  11260914  11248059  11145336  10906486\n  Reverse Read  6821393   8106334   8282174   8279195   8109186\n   Stride read  7191093   8994306   9153982   8961224   9004434\n   Random read  7156353   8957932   9167098   8980465   8940476\nMixed workload  4172747   5680814   5927825   5489578   5972253\n  Random write  1483044   1605588   1594329   1600453   1596010\n        Pwrite  1276644   1303108   1311612   1314228   1300960\n         Pread  4324337   4632869   4618386   4457870   4500166\n\nTo enhance the possibility of access the same table[index] concurrently,\nset zram a small disksize(10MB) and let threads run with large loop\ncount.\n\nfio test:\nfio --bs=32k --randrepeat=1 --randseed=100 --refill_buffers\n--scramble_buffers=1 --direct=1 --loops=3000 --numjobs=4\n--filename=/dev/zram0 --name=seq-write --rw=write --stonewall\n--name=seq-read --rw=read --stonewall --name=seq-readwrite\n--rw=rw --stonewall --name=rand-readwrite --rw=randrw --stonewall\n(10MB zram raw block device, take the average of 10 tests, KB/s)\n\n    Test     base     CAS    spinlock    rwlock  bit_spinlock\n-------------------------------------------------------------\nseq-write   933789   999357   1003298    995961   1001958\n seq-read  5634130  6577930   6380861   6243912   6230006\n   seq-rw  1405687  1638117   1640256   1633903   1634459\n  rand-rw  1386119  1614664   1617211   1609267   1612471\n\nAll the optimization methods show a higher performance than the base,\nhowever, it is hard to say which method is the most appropriate.\n\nOn the other hand, zram is mostly used on small embedded system, so we\ndon't want to increase any memory footprint.\n\nThis patch pick the bit_spinlock method, pack object size and page_flag\ninto an unsigned long table.value, so as to not increase any memory\noverhead on both 32-bit and 64-bit system.\n\nOn the third hand, even though different kinds of locks have different\nperformances, we can ignore this difference, because: if zram is used as\nzram swapfile, the swap subsystem can prevent concurrent access to the\nsame swapslot; if zram is used as zram-blk for set up filesystem on it,\nthe upper filesystem and the page cache also prevent concurrent access\nof the same block mostly.  So we can ignore the different performances\namong locks.\n\nAcked-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nReviewed-by: Davidlohr Bueso <davidlohr@hp.com>\nSigned-off-by: Weijie Yang <weijie.yang@samsung.com>\nSigned-off-by: Minchan Kim <minchan@kernel.org>\nCc: Jerome Marchand <jmarchan@redhat.com>\nCc: Nitin Gupta <ngupta@vflare.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/e6015473fdcead1cb19d54112e2dda6d2689e587"},{"sha":"4fbf43d280823dbe05bfd2d37cb9f0352b32b491","author":{"name":"Chao Yu","email":"5eeb15ae5b9723d14f20c023a7dd80da0cfa55a9@samsung.com"},"message":"zram: fix incorrect stat with failed_reads\n\nSince we allocate a temporary buffer in zram_bvec_read to handle partial\npage operations in commit 924bd88d703e (\"Staging: zram: allow partial\npage operations\"), our ->failed_reads value may be incorrect as we do\nnot increase its value when failing to allocate the temporary buffer.\n\nLet's fix this issue and correct the annotation of failed_reads.\n\nSigned-off-by: Chao Yu <chao2.yu@samsung.com>\nAcked-by: Minchan Kim <minchan@kernel.org>\nCc: Nitin Gupta <ngupta@vflare.org>\nAcked-by: Jerome Marchand <jmarchan@redhat.com>\nAcked-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/4fbf43d280823dbe05bfd2d37cb9f0352b32b491"},{"sha":"d580c91a20aa6d59c0026ecd8f4db3551bbc41d8","author":{"name":"Mike Snitzer","email":"ad2d170babf82633487ab777fab07770fbdc5ac8@redhat.com"},"message":"block: disable entropy contributions for nonrot devices\n\nClear QUEUE_FLAG_ADD_RANDOM in all block drivers that set\nQUEUE_FLAG_NONROT.\n\nHistorically, all block devices have automatically made entropy\ncontributions.  But as previously stated in commit e2e1a148 (\"block: add\nsysfs knob for turning off disk entropy contributions\"):\n    - On SSD disks, the completion times aren't as random as they\n      are for rotational drives. So it's questionable whether they\n      should contribute to the random pool in the first place.\n    - Calling add_disk_randomness() has a lot of overhead.\n\nThere are more reliable sources for randomness than non-rotational block\ndevices.  From a security perspective it is better to err on the side of\ncaution than to allow entropy contributions from unreliable \"random\"\nsources.\n\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/d580c91a20aa6d59c0026ecd8f4db3551bbc41d8"},{"sha":"8e66d4b65255be771696a421a0729cb6992372d8","author":{"name":"Sergey Senozhatsky","email":"9251ceca1068cc8334161fa91b1f6065a5ee8fa4@gmail.com"},"message":"zram: use notify_free to account all free notifications\n\n`notify_free' device attribute accounts the number of slot free\nnotifications and internally represents the number of zram_free_page()\ncalls.  Slot free notifications are sent only when device is used as a\nswap device, hence `notify_free' is used only for swap devices.  Since\nf4659d8e620d08 (zram: support REQ_DISCARD) ZRAM handles yet another one\nfree notification (also via zram_free_page() call) -- REQ_DISCARD\nrequests, which are sent by a filesystem, whenever some data blocks are\ndiscarded.  However, there is no way to know the number of notifications\nin the latter case.\n\nUse `notify_free' to account the number of pages freed by\nzram_bio_discard() and zram_slot_free_notify().  Depending on usage\nscenario `notify_free' represents:\n\n a) the number of pages freed because of slot free notifications, which is\n   equal to the number of swap_slot_free_notify() calls, so there is no\n   behaviour change\n\n b) the number of pages freed because of REQ_DISCARD notifications\n\nSigned-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nAcked-by: Minchan Kim <minchan@kernel.org>\nAcked-by: Jerome Marchand <jmarchan@redhat.com>\nCc: Nitin Gupta <ngupta@vflare.org>\nCc: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/8e66d4b65255be771696a421a0729cb6992372d8"},{"sha":"a9bb5a21f0f0ed6ad5c032bf7512394784830843","author":{"name":"Weijie Yang","email":"8c97edccb1d93792b9d0c97c45d654274c724617@samsung.com"},"message":"zram: avoid kunmap_atomic() of a NULL pointer\n\nzram could kunmap_atomic() a NULL pointer in a rare situation: a zram\npage becomes a full-zeroed page after a partial write io.  The current\ncode doesn't handle this case and performs kunmap_atomic() on a NULL\npointer, which panics the kernel.\n\nThis patch fixes this issue.\n\nSigned-off-by: Weijie Yang <weijie.yang@samsung.com>\nCc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCc: Dan Streetman <ddstreet@ieee.org>\nCc: Nitin Gupta <ngupta@vflare.org>\nCc: Weijie Yang <weijie.yang.kh@gmail.com>\nAcked-by: Jerome Marchand <jmarchan@redhat.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/a9bb5a21f0f0ed6ad5c032bf7512394784830843"},{"sha":"ea56315c63bbb6db1df5113da01b99e69074897e","author":{"name":"karam.lee","email":"9c66ddf6ebd32a33e19c912ea6a05ad62c81b63e@lge.com"},"message":"zram: remove bio parameter from zram_bvec_rw()\n\nRecently rw_page block device operation has been added.  This patchset\nimplements rw_page operation for zram block device and does some clean-up.\n\nThis patch (of 3):\n\nRemove an unnecessary parameter(bio) from zram_bvec_rw() and\nzram_bvec_read().  zram_bvec_read() doesn't use a bio parameter, so remove\nit.  zram_bvec_rw() calls a read/write operation not using bio, so a rw\nparameter replaces a bio parameter.\n\nSigned-off-by: karam.lee <karam.lee@lge.com>\nAcked-by: Minchan Kim <minchan@kernel.org>\nAcked-by: Jerome Marchand <jmarchan@redhat.com>\nCc: Matthew Wilcox <matthew.r.wilcox@intel.com>\nCc: Nitin Gupta <ngupta@vflare.org>\nCc: <seungho1.park@lge.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/ea56315c63bbb6db1df5113da01b99e69074897e"},{"sha":"778917c5adf6dc508bf12d57c5c417227d53cb9b","author":{"name":"karam.lee","email":"9c66ddf6ebd32a33e19c912ea6a05ad62c81b63e@lge.com"},"message":"zram: change parameter from vaild_io_request()\n\nThis patch changes parameter of valid_io_request for common usage.  The\npurpose of valid_io_request() is to determine if bio request is valid or\nnot.\n\nThis patch use I/O start address and size instead of a BIO parameter for\ncommon usage.\n\nSigned-off-by: karam.lee <karam.lee@lge.com>\nAcked-by: Minchan Kim <minchan@kernel.org>\nAcked-by: Jerome Marchand <jmarchan@redhat.com>\nCc: Matthew Wilcox <matthew.r.wilcox@intel.com>\nCc: Nitin Gupta <ngupta@vflare.org>\nCc: <seungho1.park@lge.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/778917c5adf6dc508bf12d57c5c417227d53cb9b"},{"sha":"0d6c59566d28480a73b0987f36fa5c6ffb597194","author":{"name":"Sergey Senozhatsky","email":"9251ceca1068cc8334161fa91b1f6065a5ee8fa4@gmail.com"},"message":"zram: clean up zram_meta_alloc()\n\nA trivial cleanup of zram_meta_alloc() error handling.\n\nSigned-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nAcked-by: Minchan Kim <minchan@kernel.org>\nCc: Nitin Gupta <ngupta@vflare.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/gsstudios/Dorimanx-SG2-I9100-Kernel/commits/0d6c59566d28480a73b0987f36fa5c6ffb597194"}]}
{"actor":{"display_login":"gsstudios"}}