Bug 1672922 - [GSS] problems adding bricks to a volume
Summary: [GSS] problems adding bricks to a volume
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: ---
: ---
Assignee: Srijan Sivakumar
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1780288
Blocks: 1935046
TreeView+ depends on / blocked
 
Reported: 2019-02-06 08:43 UTC by amansan
Modified: 2024-10-01 16:13 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1780288 (view as bug list)
Environment:
Last Closed: 2021-09-01 06:29:59 UTC
Embargoed:


Attachments (Terms of Use)

Description amansan 2019-02-06 08:43:37 UTC
Description of problem:

This BZ has been opened to allow access to servers even if they are not part of the auth.allow (if exist) list.

Related with BZ 1665873

Comment 4 amansan 2019-03-14 13:07:40 UTC
Hi

Could you review anything regarding this bug ?

Thanks

Alicia

Comment 35 Srijan Sivakumar 2021-07-02 05:43:22 UTC
 Hi Satheesaran,

 One of the patches to be backported is required as it fixes a scenario wherein we could see buffer overflow when using auth.allow. That patch came in upstream recently. For reference : https://github.com/gluster/glusterfs/pull/2526

 Regards, 
 Srijan

Comment 36 SATHEESARAN 2021-07-05 11:27:01 UTC
(In reply to Srijan Sivakumar from comment #35)
>  Hi Satheesaran,
> 
>  One of the patches to be backported is required as it fixes a scenario
> wherein we could see buffer overflow when using auth.allow. That patch came
> in upstream recently. For reference :
> https://github.com/gluster/glusterfs/pull/2526
> 
>  Regards, 
>  Srijan

Hi Srijan,

The existing downstream codebase ( RHGS 3.5.5 ), doesn't carry the change.
So the buffer overflow problem when using auth.allow will not create any consequence.

If we could ignore the original patch which fixed the issue, we would not land up in this issue.
So I feel this is good to ignore the fix.

Can you kindly check this part, please ?


Note You need to log in before you can comment on or make changes to this bug.