Re: [PATCH v2] libfc: sanity check cpu number extracted from xid

2016-07-13 Thread Martin K. Petersen
> "Johannes" == Johannes Thumshirn writes: Johannes> @Martin, do you queue the libfc patches as well? Sure. (Sorry about the delay, been on vacation). -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH v2] libfc: sanity check cpu number extracted from xid

2016-07-13 Thread Martin K. Petersen
> "Chris" == Chris Leech writes: Chris> In the receive path libfc extracts a cpu number from the ox_id in Chris> the fiber channel header and uses that to do a per_cpu_ptr Chris> conversion. If, for some reason, a frame is received with an Chris> invalid ox_id,

Re: [PATCH v2] libfc: sanity check cpu number extracted from xid

2016-07-01 Thread Johannes Thumshirn
On Thu, Jun 30, 2016 at 08:32:36AM -0700, Chris Leech wrote: > In the receive path libfc extracts a cpu number from the ox_id in the > fiber channel header and uses that to do a per_cpu_ptr conversion. > If, for some reason, a frame is received with an invalid ox_id, > per_cpu_ptr will return an

[PATCH v2] libfc: sanity check cpu number extracted from xid

2016-06-30 Thread Chris Leech
In the receive path libfc extracts a cpu number from the ox_id in the fiber channel header and uses that to do a per_cpu_ptr conversion. If, for some reason, a frame is received with an invalid ox_id, per_cpu_ptr will return an invalid pointer and the libfc receive path will panic the system