Back to bug 1319670

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-03-21 10:08:22 UTC Target Release RHGS 3.1.2 ---
Gaurav Kumar Garg 2016-03-21 10:09:33 UTC Status NEW ASSIGNED
Blocks 1260783 1311817
Depends On 1269203
Assignee rhs-bugs ggarg
Gaurav Kumar Garg 2016-03-21 10:12:31 UTC Status ASSIGNED POST
SATHEESARAN 2016-03-21 14:23:35 UTC CC sasundar
Component glusterfs glusterfs-server
Link ID Red Hat Knowledge Base (Solution) 1985993
QA Contact annair bsrirama
SATHEESARAN 2016-03-21 14:24:02 UTC Sub Component core glusterd
SATHEESARAN 2016-03-21 14:24:17 UTC Severity unspecified medium
Rahul Hinduja 2016-03-21 14:51:45 UTC CC rhinduja
Rejy M Cyriac 2016-03-21 16:09:48 UTC CC rcyriac
Atin Mukherjee 2016-03-21 16:37:49 UTC Status POST MODIFIED
Red Hat Bugzilla Rules Engine 2016-03-21 16:37:57 UTC Target Release --- RHGS 3.1.3
Satish Mohan 2016-03-24 13:24:12 UTC Status MODIFIED ON_QA
Fixed In Version glusterfs-3.7.9-1
Byreddy 2016-04-05 04:51:58 UTC Status ON_QA VERIFIED
Gaurav Kumar Garg 2016-05-04 09:56:02 UTC Doc Text Previously if user set an option where length of key=value goes beyond PATH_MAX (4096) character then tokenizing the option at the time of reading configuration file will fail.
This is because of the we was having restriction in fgets to read maximum of PATH_MAX (4096) length of character.
Consequence of this is when user try to restart glusterd, after setting key=value length beyond PATH_MAX (4096) character, glusterd will not restart.

With this fix instead of PATH_MAX, consumer of gf_store_read_and_tokenize function will decide the size of the buffer length.
John Skeoch 2016-06-05 23:40:17 UTC Assignee ggarg smohan
Laura Bailey 2016-06-14 02:01:35 UTC Doc Text Previously if user set an option where length of key=value goes beyond PATH_MAX (4096) character then tokenizing the option at the time of reading configuration file will fail.
This is because of the we was having restriction in fgets to read maximum of PATH_MAX (4096) length of character.
Consequence of this is when user try to restart glusterd, after setting key=value length beyond PATH_MAX (4096) character, glusterd will not restart.

With this fix instead of PATH_MAX, consumer of gf_store_read_and_tokenize function will decide the size of the buffer length.
Previously, if a user set an option where the number of characters in the key/value pair was greater than the value of PATH_MAX (4096), a restriction in the fgets operation meant that tokenizing the option failed. This meant that when users attempted to restart glusterd after setting a very long key/value pair, glusterd did not restart. This update ensures that the buffer length is controlled by the gf_store_read_and_tokenize operation so that tokenizing succeeds.
Flags needinfo?(amukherj)
Atin Mukherjee 2016-06-14 03:47:55 UTC Flags needinfo?(amukherj)
errata-xmlrpc 2016-06-23 00:50:27 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-06-23 05:04:46 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-06-23 01:04:46 UTC
Rejy M Cyriac 2016-09-17 16:33:10 UTC Sub Component glusterd
Component glusterd glusterd-transition
Rejy M Cyriac 2016-09-17 16:45:53 UTC CC rhs-bugs, storage-qa-internal, vbellur
Component glusterd-transition glusterd

Back to bug 1319670