Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L linux-coresight-backports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linux-arm
  • linux-coresight-backports
  • Repository
  • linux-coresight-backports
  • drivers
  • scsi
  • fnic
  • fnic_scsi.c
Find file BlameHistoryPermalink
  • Sesidhar Beddel's avatar
    [SCSI] fnic: Kernel panic while running sh/nosh with max lun cfg · d0385d92
    Sesidhar Beddel authored Sep 09, 2013
    
    
    Kernel panics due to NULL lport while executing the log message because
    of synchronization issues between libfc and scsi transport fc. Checking
    for NULL pointers at the beginning of this routine would resolve the issue
    from kernel panic point of view.
    
    Signed-off-by: default avatarSesidhar Baddel <sebaddel@cisco.com>
    Signed-off-by: default avatarHiral Patel <hiralpat@cisco.com>
    Signed-off-by: default avatarJames Bottomley <JBottomley@Parallels.com>
    d0385d92