Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add PNP info to PCI attachment of ae, age, ahci, amr, ale, an, bwi, bwn drivers #3

Merged
merged 0 commits into from May 31, 2018

Conversation

lakhanshiva
Copy link
Collaborator

@lakhanshiva lakhanshiva commented May 16, 2018

The device id table for ahci is

static const struct {
	uint32_t	id;
	uint8_t		rev;
	const char	*name;
	int		quirks;
} ahci_ids[]

Therefore i used "W32:vendor/device" as descriptor string in MODULE_PNP_INFO

The device id table for an is

struct an_type {
	u_int16_t		an_vid;
	u_int16_t		an_did;
	char			*an_name;
};

Therefore i used "U16:vendor;U16:device;D:#" as descriptor string in MODULE_PNP_INFO

The device id table for bwn is

struct bwn_pci_device {
	uint16_t	vendor;
	uint16_t	device;
	const char	*desc;
	uint32_t	quirks;
}

Therefore i used "U16:vendor;U16:device;D:#" as descriptor string in MODULE_PNP_INFO

The device id table for bwi is

static const struct bwi_dev {
	uint16_t	vid;
	uint16_t	did;
	const char	*desc;
}

Therefore i used "U16:vendor;U16:device;D:#" as descriptor string in MODULE_PNP_INFO

The device id table for ale is

static const struct ale_dev {
	uint16_t	ale_vendorid;
	uint16_t	ale_deviceid;
	const char	*ale_name;
}

Therefore i used "U16:vendor;U16:device;D:#" as descriptor string in MODULE_PNP_INFO

The device id table for amr is

static struct amr_ident
{
    int		vendor;
    int		device;
    int		flags;
#define AMR_ID_PROBE_SIG	(1<<0)	/* generic i960RD, check signature */
#define AMR_ID_DO_SG64		(1<<1)
#define AMR_ID_QUARTZ		(1<<2)
}

Therefore i used "U16:vendor;U16:device" as descriptor string in MODULE_PNP_INFO

The device id table for age is

static struct age_dev {
	uint16_t	age_vendorid;
	uint16_t	age_deviceid;
	const char	*age_name;
} age_devs[];

Therefore i used "U16:vendor;U16:device;D:#" as descriptor string in MODULE_PNP_INFO

The device id table for ae is

static struct ae_dev {
	uint16_t	vendorid;
	uint16_t	deviceid;
	const char	*name;
} ae_devs[];

Therefore i used "U16:vendor;U16:device;D:#" as descriptor string in MODULE_PNP_INFO

@lakhanshiva lakhanshiva requested a review from bsdimp May 16, 2018 07:19
@lakhanshiva lakhanshiva self-assigned this May 16, 2018
Copy link

@ctuffli ctuffli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lakhanshiva, there seem to be multiple iterations to the AHCI driver. Because they are all related, would you mind squashing them into a single commit to make the review easier?

Also, it would be worth discussing with @bsdimp if a pull request should have a single driver or if submitting changes for multiple drivers is OK.

@@ -684,3 +684,5 @@ static driver_t ahci_ata_driver = {
sizeof(struct ahci_controller)
};
DRIVER_MODULE(ahci, atapci, ahci_ata_driver, ahci_devclass, NULL, NULL);
MODULE_PNP_INFO("U32:id;U8:rev;D:#", pci, ahci, ahci_ids[],
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't the passed parameter be ahci_ids without the trailing []?

@lakhanshiva
Copy link
Collaborator Author

lakhanshiva commented May 16, 2018 via email

@lakhanshiva
Copy link
Collaborator Author

I have squashed the commits related to same driver into one commit. I will discuss with bsdimp regarding one driver per pull request.

Copy link

@ctuffli ctuffli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

@ctuffli ctuffli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -684,3 +684,5 @@ static driver_t ahci_ata_driver = {
sizeof(struct ahci_controller)
};
DRIVER_MODULE(ahci, atapci, ahci_ata_driver, ahci_devclass, NULL, NULL);
MODULE_PNP_INFO("U32:device;U8:rev;D:#", pci, ahci, ahci_ids,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As to your email question, I don't see an issue with using rev in the description string, but I'll defer to @bsdimp

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line needs to be just before the ahci_ata_methods table.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved it.

@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ahci, an drivers Add PNP info to PCI attachment of ahci, an, ata-isa drivers May 17, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ahci, an, ata-isa drivers Add PNP info to PCI attachment of ahci, an drivers May 18, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ahci, an drivers Add PNP info to PCI attachment of ahci, an, bwn drivers May 19, 2018
@lakhanshiva lakhanshiva force-pushed the lakhan-pnpinfo branch 2 times, most recently from 15e0a50 to 307caa4 Compare May 19, 2018 11:18
@@ -664,6 +664,8 @@ static driver_t ahci_driver = {
sizeof(struct ahci_controller)
};
DRIVER_MODULE(ahci, pci, ahci_driver, ahci_devclass, NULL, NULL);
MODULE_PNP_INFO("U32:device;U8:rev;D:#", pci, ahci, ahci_ids,
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs to be "W32:vendor/device;" We can leave out the U8:rev; stuff since it won't change which driver is loaded.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I've excluded U8:rev and later portion and changed it to W32

@@ -295,6 +295,10 @@ DEFINE_CLASS_0(bwn_pci, bwn_pci_driver, bwn_pci_methods,
sizeof(struct bwn_pci_softc));
DRIVER_MODULE_ORDERED(bwn_pci, pci, bwn_pci_driver, bwn_pci_devclass, NULL,
NULL, SI_ORDER_ANY);
MODULE_PNP_INFO("U16:vendor;U16:device;D:#", pci, bwn_pci,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the unique string, I'd be tempted to make this bwn_siba instead of bwn_pci to give a hint this is related to siba(4)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, changed it as bwn_siba

@@ -295,6 +295,10 @@ DEFINE_CLASS_0(bwn_pci, bwn_pci_driver, bwn_pci_methods,
sizeof(struct bwn_pci_softc));
DRIVER_MODULE_ORDERED(bwn_pci, pci, bwn_pci_driver, bwn_pci_devclass, NULL,
NULL, SI_ORDER_ANY);
MODULE_PNP_INFO("U16:vendor;U16:device;D:#", pci, bwn_pci,
siba_devices, sizeof(siba_devices[0]), nitems(siba_devices) - 1);
MODULE_PNP_INFO("U16:vendor;U16:device;D:#", pci, bwn,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar to the above, I'd be tempted to make this bwn_bcma to give a hint this is related to bmca(4)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, changed it as bwn_bcma

@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ahci, an, bwn drivers Add PNP info to PCI attachment of ahci, an, bwn, bwi drivers May 22, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ahci, an, bwn, bwi drivers Add PNP info to PCI attachment of ahci, an, ale, bwn, bwi drivers May 24, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ahci, an, ale, bwn, bwi drivers Add PNP info to PCI attachment of ahci, amr, ale, an, bwi, bwn drivers May 24, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ahci, amr, ale, an, bwi, bwn drivers Add PNP info to PCI attachment of age, ahci, amr, ale, an, bwi, bwn drivers May 24, 2018
@lakhanshiva lakhanshiva force-pushed the lakhan-pnpinfo branch 3 times, most recently from 0d9c7e0 to 59b0542 Compare May 26, 2018 04:39
@lakhanshiva lakhanshiva force-pushed the lakhan-pnpinfo branch 2 times, most recently from b04f295 to 22f6776 Compare May 26, 2018 05:38
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of age, ahci, amr, ale, an, bwi, bwn drivers Add PNP info to PCI attachment of ae, age, ahci, amr, ale, an, bwi, bwn drivers May 26, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ae, age, ahci, amr, ale, an, bwi, bwn drivers Add PNP info to PCI attachment of ae, age, ahci, alc, amr, ale, an, bwi, bwn drivers May 26, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ae, age, ahci, alc, amr, ale, an, bwi, bwn drivers Add PNP info to PCI attachment of ae, age, ahci, alc, amdsmb, amr, ale, an, bwi, bwn drivers May 27, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ae, age, ahci, alc, amdsmb, amr, ale, an, bwi, bwn drivers Add PNP info to PCI attachment of ae, age, ahci, alc, amdsmb, amr, ale, an, bfe, bwi, bwn drivers May 28, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ae, age, ahci, alc, amdsmb, amr, ale, an, bfe, bwi, bwn drivers Add PNP info to PCI attachment of ae, age, ahci, alc, amdsmb, amr, ale, an, bfe, bge, bwi, bwn drivers May 28, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ae, age, ahci, alc, amdsmb, amr, ale, an, bfe, bge, bwi, bwn drivers Add PNP info to PCI attachment of ae, age, ahci, alc, amdsmb, amr, ale, an, bfe, bge, bwi, bwn, ce drivers May 30, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ae, age, ahci, alc, amdsmb, amr, ale, an, bfe, bge, bwi, bwn, ce drivers Add PNP info to PCI attachment of ae, age, ahci, alc, amdsmb, amr, ale, an, bfe, bge, bwi, bwn, ce, dpt drivers May 31, 2018
@lakhanshiva lakhanshiva changed the title Add PNP info to PCI attachment of ae, age, ahci, alc, amdsmb, amr, ale, an, bfe, bge, bwi, bwn, ce, dpt drivers Add PNP info to PCI attachment of ae, age, ahci, amr, ale, an, bwi, bwn drivers May 31, 2018
@@ -144,6 +139,13 @@ static struct amr_ident
{0, 0, 0}
};

static devclass_t amr_devclass;
DRIVER_MODULE(amr, pci, amr_pci_driver, amr_devclass, 0, 0);
MODULE_PNP_INFO("U16:vendor;U16:device", pci, amr, amr_device_ids,
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this string is right...

DRIVER_MODULE(amr, pci, amr_pci_driver, amr_devclass, 0, 0);
MODULE_DEPEND(amr, pci, 1, 1, 1);
MODULE_DEPEND(amr, cam, 1, 1, 1);

static struct amr_ident
{
int vendor;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but we need to change vendor and device here to be uint16_t's rather than int's. int's are 32-bits, but a poor fit for this data.

@lakhanshiva
Copy link
Collaborator Author

lakhanshiva commented May 31, 2018 via email

@lakhanshiva lakhanshiva merged this pull request into bsdimp:lakhan-pnpinfo May 31, 2018
bsdimp pushed a commit that referenced this pull request May 10, 2023
Under certain loads, the following panic is hit:

    panic: page fault
    KDB: stack backtrace:
    #0 0xffffffff805db025 at kdb_backtrace+0x65
    #1 0xffffffff8058e86f at vpanic+0x17f
    #2 0xffffffff8058e6e3 at panic+0x43
    #3 0xffffffff808adc15 at trap_fatal+0x385
    #4 0xffffffff808adc6f at trap_pfault+0x4f
    #5 0xffffffff80886da8 at calltrap+0x8
    #6 0xffffffff80669186 at vgonel+0x186
    #7 0xffffffff80669841 at vgone+0x31
    #8 0xffffffff8065806d at vfs_hash_insert+0x26d
    #9 0xffffffff81a39069 at sfs_vgetx+0x149
    #10 0xffffffff81a39c54 at zfsctl_snapdir_lookup+0x1e4
    #11 0xffffffff8065a28c at lookup+0x45c
    #12 0xffffffff806594b9 at namei+0x259
    #13 0xffffffff80676a33 at kern_statat+0xf3
    #14 0xffffffff8067712f at sys_fstatat+0x2f
    #15 0xffffffff808ae50c at amd64_syscall+0x10c
    freebsd#16 0xffffffff808876bb at fast_syscall_common+0xf8

The page fault occurs because vgonel() will call VOP_CLOSE() for active
vnodes. For this reason, define vop_close for zfsctl_ops_snapshot. While
here, define vop_open for consistency.

After adding the necessary vop, the bug progresses to the following
panic:

    panic: VERIFY3(vrecycle(vp) == 1) failed (0 == 1)
    cpuid = 17
    KDB: stack backtrace:
    #0 0xffffffff805e29c5 at kdb_backtrace+0x65
    #1 0xffffffff8059620f at vpanic+0x17f
    #2 0xffffffff81a27f4a at spl_panic+0x3a
    #3 0xffffffff81a3a4d0 at zfsctl_snapshot_inactive+0x40
    #4 0xffffffff8066fdee at vinactivef+0xde
    #5 0xffffffff80670b8a at vgonel+0x1ea
    #6 0xffffffff806711e1 at vgone+0x31
    #7 0xffffffff8065fa0d at vfs_hash_insert+0x26d
    #8 0xffffffff81a39069 at sfs_vgetx+0x149
    #9 0xffffffff81a39c54 at zfsctl_snapdir_lookup+0x1e4
    #10 0xffffffff80661c2c at lookup+0x45c
    #11 0xffffffff80660e59 at namei+0x259
    #12 0xffffffff8067e3d3 at kern_statat+0xf3
    #13 0xffffffff8067eacf at sys_fstatat+0x2f
    #14 0xffffffff808b5ecc at amd64_syscall+0x10c
    #15 0xffffffff8088f07b at fast_syscall_common+0xf8

This is caused by a race condition that can occur when allocating a new
vnode and adding that vnode to the vfs hash. If the newly created vnode
loses the race when being inserted into the vfs hash, it will not be
recycled as its usecount is greater than zero, hitting the above
assertion.

Fix this by dropping the assertion.

FreeBSD-issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252700
Reviewed-by: Andriy Gapon <avg@FreeBSD.org>
Reviewed-by: Mateusz Guzik <mjguzik@gmail.com>
Reviewed-by: Alek Pinchuk <apinchuk@axcient.com>
Reviewed-by: Ryan Moeller <ryan@iXsystems.com>
Signed-off-by: Rob Wing <rob.wing@klarasystems.com>
Co-authored-by: Rob Wing <rob.wing@klarasystems.com>
Submitted-by: Klara, Inc.
Sponsored-by: rsync.net
Closes #14501
bsdimp pushed a commit that referenced this pull request Aug 16, 2023
Avoid locking issues when if_allmulti() calls the driver's if_ioctl,
because that may acquire sleepable locks (while we hold a non-sleepable
rwlock).

Fortunately there's no pressing need to hold the mroute lock while we
do this, so we can postpone the call slightly, until after we've
released the lock.

This avoids the following WITNESS warning (with iflib drivers):

	lock order reversal: (sleepable after non-sleepable)
	 1st 0xffffffff82f64960 IPv4 multicast forwarding (IPv4 multicast forwarding, rw) @ /usr/src/sys/netinet/ip_mroute.c:1050
	 2nd 0xfffff8000480f180 iflib ctx lock (iflib ctx lock, sx) @ /usr/src/sys/net/iflib.c:4525
	lock order IPv4 multicast forwarding -> iflib ctx lock attempted at:
	#0 0xffffffff80bbd6ce at witness_checkorder+0xbbe
	#1 0xffffffff80b56d10 at _sx_xlock+0x60
	#2 0xffffffff80c9ce5c at iflib_if_ioctl+0x2dc
	#3 0xffffffff80c7c395 at if_setflag+0xe5
	#4 0xffffffff82f60a0e at del_vif_locked+0x9e
	#5 0xffffffff82f5f0d5 at X_ip_mrouter_set+0x265
	#6 0xffffffff80bfd402 at sosetopt+0xc2
	#7 0xffffffff80c02105 at kern_setsockopt+0xa5
	#8 0xffffffff80c02054 at sys_setsockopt+0x24
	#9 0xffffffff81046be8 at amd64_syscall+0x138
	#10 0xffffffff8101930b at fast_syscall_common+0xf8

See also:	https://redmine.pfsense.org/issues/12079
Reviewed by:	mjg
Sponsored by:	Rubicon Communications, LLC ("Netgate")
Differential Revision:	https://reviews.freebsd.org/D41209
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants