📣 黑五价提前开抢|VIP一年通行证5折,蓝莓、Offer多多同步特惠
查看: 20907| 回复: 44
跳转到指定楼层
上一主题 下一主题
收起左侧

[职场感言] tesla看样子不是个好去处

   
全局:

注册一亩三分地论坛,查看更多干货!

您需要 登录 才可以下载或查看附件。没有帐号?注册账号

x
企业文化有毒. From 1point 3acres bbs


https://www.reddit.com/r/SelfDri ... eslas_work_culture/. 1point3acres


Some insight on Tesla's work culture
. .и
Context: A Tesla lead of Autopilot Data/Vision, AI quit today (06/17/2021). This was their outgoing message to the team chat:

    Management needs to change - from the top down. We say there is no chain of command and tell people they can email Elon if they want, and then hear - 'but know that doesn't usually turn out too well.'
.
    Leadership has NO clue how to do an analyst job - and they don't have to. BUT they HAVE to understand what it takes to do it. They cannot stand on the sidelines and piss and moan over stats if they couldn't do the job themselves. I have seen WAY too many Sups go into training and jump out not bothering to even try and certify in a workflow, then yell when people aren't living up to their unrealistic expectations. The Sups can't even answer a simple question on the workflow themselves - which leads to frustrations from analysts and NO support.

    Instead of berating people, how about we actively support them? Instead of issuing warnings for something that happened a year ago, how about we celebrate their achievements and what's happening NOW. Instead of constantly moving people from workflow to workflow every 6 - 8 weeks and expecting perfection, how about we train and get experts in workflows that can actually learn processes, and what it will take to make them more efficient.

    You are treating people like they work in a call center - and that will ONLY get you call center quality and results. Have a revolving door and see how quickly the data is compromised. Maybe treat people like you are invested in them, that you WANT them to be there - not that they are simple running on borrowed time. Right now people are constantly threatened with their jobs, for any and all reasons. "Elon hates CA so he is shutting it down, Buffalo is cheaper, we know the expectations are super high and expect to lose half our workforce - that's ok." I have heard all of those statements. Even 'well the job description says you need to be ok with change and ambiguity so if they cant do it they shouldn't be here.' These are people that have worked here for YEARS and have been fine and thrived. Juggling people around over and over this year, giving subpar training, unrealistic expectations, and adding hostility YOU made this. It didn't have to be this way. You are ruining good, valuable people - just because you can.

    I cannot tell you how disappointing it is to see people promoted who haven't worked into a role. The hiring Sup or Manager promotes them based on the fact that person will shut up, do what they are told, not have an opinion or idea, and just support that manager in whatever they ask - like little soldiers. When someone has an idea, an innovation, or questions why things are the way they are - not one wants to deal with that - or even be open to doing things in a better way. That's supposed to be what Tesla is about - but outside of corporate its completely shut down, and not open to having that conversation.

    Obviously, engineers cannot write code to fix the car and make it do what you need it to. So they are using people to annotate and process the info, sending it to the car. The car can then start predicting and the engineers have something to work with, and then can write their code. We all know that. What not treat those people with some respect instead of shuffling them every couple weeks, threatening and berating them constantly, treating them like they are disposable and worthless, and maybe giving them something to look forward to when they start their workday.

    This past year it has been heartbreaking to be in a leadership role and see so many broken people, no longer having pride in their company - just trying desperately not to lose their job - one that they have thrived in for years - all because of mismanagement. If you wanted to layoff the workforce in SM then you should have just done that. Put out a WARN notice and let everyone go. What you have done was unnecessarily cruel and uncalled for - especially from the people building the future of self-driving.
. From 1point 3acres bbs
    The handbook is wrong - there are assholes at Tesla - and it starts at the top. The quotes above come directly from Andre and Fabio. They have created the most toxic, hostile work environment treating people like cattle and having no regard for them whatsoever. I hope they are proud of what they have built. Personally, I can no longer support such an environment, management, and leadership - if this is ok with Tesla - its not ok with me.



上一篇:在美国如何远程入职
下一篇:求问,公司iOS版APP内测,去哪招有技术背景的seed user?
推荐
dylan_li 2021-6-19 04:49:46 | 只看该作者
全局:
老马开始搞虚拟货币就知道瓶颈到了

评分

参与人数 3大米 +3 收起 理由
amyyixu + 1 给你点个赞!
4x4 + 1 赞一个
好女不过百 + 1 赞一个!

查看全部评分

回复

使用道具 举报

地里匿名用户
推荐
匿名用户-6GBAI  | 添加认证 | 2021-6-19 08:17:40 来自APP
身为搞硬件的去特斯拉还挺满意的,可能是因为之前工作实在是不咋地;企业文化toxic和management有问题确实听说了但组里的老板组员都挺好的所以暂时也没被影响到。出问题时候确实强度大但平时朝九晚六还能做到,说是无限制休假但真正好意思狂休假的也没有。俗人一个当时跳槽就是选了钱给的最多的offer,总工资翻倍生活成本增加了百分之十,并且组员都挺上进的趋于年轻化比之前某养老车企里边一堆老油条不干活的要好。不是马教主的拥护者,就是纯为了找个工作混口饭吃拿完四年股票就打算走人了,未来发展怎样也不知道了

评分

参与人数 2大米 +2 收起 理由
4x4 + 1 赞一个
Angello + 1 赞一个

查看全部评分

回复

使用道具 举报

推荐
asterid 2021-6-19 05:53:34 | 只看该作者
全局:
i wrote a quick python/fabric script that ssh’d to as many cars as possible at a time to rm the file
. 1point3acres.com

太刺激了,直接 ssh 到车里去改文件!看完真的不敢买 Tesla 了。

评分

参与人数 3大米 +3 收起 理由
hbzzg + 1 赞一个
hxl930303 + 1 给你点个赞!
4x4 + 1 赞一个

查看全部评分

回复

使用道具 举报

🔗
 楼主| 4x4 2021-6-19 02:57:24 | 只看该作者
本楼:
全局:
回复

使用道具 举报

🔗
 楼主| 4x4 2021-6-19 03:02:22 | 只看该作者
全局:
https://www.reddit.com/r/EnoughM ... tes_about_problems/. Χ

两年前tesla 软工吐槽

Former Tesla Programmer's anecdotes about problems

**** I've added some more ****-baidu 1point3acres
I have no way of proving any of this to be true, but I thought it was worth sharing. Enjoy.

i used to work for tesla writing infotainment firmware and backend services - all of which runs in a single bottom tier Datacenter in a single location on the worst VMware deployment known to man.. From 1point 3acres bbs
. 1point3acres.com
fun fact: a jenkins pipeline once caused almost the entire fleet to reboot loop for about an hour

model s and x use openvpn to talk to their backend. inside that backend there are metadata services that feed info to the system, one of those things being a ~20MB+ (generated by the worst erp system) json payload that describes supercharger shit for the map in the touchscreen. somebody was smart enough to do automated linting but forgot to validate against the custom parser the car runs which caused a segfault in the qt app that runs the ui, which in turn for a variety of reasons forces a reboot of that component. I think we clocked about 15 seconds before it read the file and faulted after boot. it was doing that for an hour before everyone panicked and got me and qa on the phone to fix it. i wrote a quick python/fabric script that ssh’d to as many cars as possible at a time to rm the file

    why do the cars run a cluster of ubuntu vms? used to be centos 6 and Ruby on Rails. I haven’t worked there in 3 years, but last I heard it hadn’t changed much for s and x. model 3 uses newer tech, but still based out of a single Datacenter

.1point3acressome of what I wrote runs on the factory line - at the time we started the model s program, which has not changed to this day, we fake the backend to install and validate firmware as the car moves down the line. a tech runs over to the car, plugs an eth cable in diag and dumps an image on the car using curl and a tui app I wrote using python. as the car moves down the line it is installing firmware for about an hour. if that station for any reason can’t talk to the PKI system, erp, or a ruby webapp it halts the line

    can't you flash the storage before its installed in a car?

yes and no. the firmware update process in a car is complicated because you have a bunch of dumb components hanging off of CAN or LIN and they have to updated in very specific order and sometimes you have to retry 10s of times to get it to take. ( f*** you Bosch). Tesla never bothered to flash those things ahead of time before assembly so that gets done the first time as it rolls down the line. the infotainment system and gateway arbitrate that stuff. typically any update that tuned voltages becomes a one way - no downgrade is possible without frying something

    this is the thing, like i work with boards that have many devices on them that have firmware and they're all flashed well before the >board is installed in anything if not before even being soldered down they got smart eventually - model 3 does do this now, but doing that at scale with all the components for a car is a challenge when you have it being done with stations running yocto images and perl
-baidu 1point3acres
    like, for all the lols @ tesla, have they literally never heard of a process engineer?. 1point3acres

like everyone else who was smart they either quit or were fired through no fault of their own so what you’re left with are people fearing for their job who desperately don’t want to change status quo for fear it will break something

    they forgot that the unspoken part of "move fast and break things" is that you're supposed to fix what's broken

exactly this. we never really had time to address critical issues and were constantly short on staff because people were quitting or they just wouldn't give candidates competitive offers. this is why you hear about people burning out - they've managed to chase everyone away

more fun facts:
. ----
the infotainment system and gateway don't have a battery-backed rtc. when the system reboots (sleep, deep sleep, reboot, whatever) the car is at tyool 1970 until it gets ntp again. the logs themselves are written in a binary ring buffer format and when they come in they used to end up in a giant 700TB single mysql database after they were expanded. all of production after-sales service and engineering relies on that single log interpretation system which ran on centos 5 and python 2.4 until hbase/hadoop and friends were brought in.

the supercharger system uses ssh dss keys to "vpn" back to the datacenter to a single server over 2G wireless with very limited resources. the connection is essentially simplex for various reasons so getting data to and from the supercharger is usually a 1KB/s operation unless that site has had connection aggregation done. at one point i looked at the system and to pull data out for analysis, somebody had written a bash script that was printf'ing in a for loop across ~5k devices. it would usually take about 3 days to do a successful firmware update on any single supercharger.

we once patched openssl to ignore client cert expiry because somebody forgot to create a process to update keys in the field and all the customer cars started falling offline because their certs had expired. the quick and dirty was to just patch openssl quickly and make openvpn on the server side use that one while we created those processes for about 2 weeks.
. Χ. From 1point 3acres bbs
most of the time me and the other firmware folks were chasing elon's whims about what to do with firmware. where i should have been fixing critical issues in the system i was pulled off to do shit like add farting unicorns

    uh we literally do the same thing; well, yocto images and python

    tesla isn't the first to solder down SOMs running embedded linux and a bunch of MCUs hanging off an i2c/canbus/whatever line

they aren't the first - for what we were doing at the time it made sense and helped us get the program off the ground quickly. lots of room for improvement and in 8 years, they should have done so.

my issue was the fact that the systems doing the flashing were running the yocto images and perl and the guy writing the perl was also responsible for writing the thing that actually updates the car. that thing (the car-side updater) is about ~100k lines of C in a single file. code reviews were always a laugh riot

    i am SO GLAD your nda expired

99% of what i'm talking about is "public" anyway. tesla isn't encrypting their firmware and it's really easy to glean information from the vpn with a packet cap because nothing inside the vpn (was) encrypted. dumping tegra 3 model s and x is trivial and tesla's cars are nowhere near as secure as they'd have you believe. ..

for example, at one time you were able to root a model s with a usb stick and a gstreamer exploit.. 1point3acres.com

while tesla should be given credit for updating the car over the air to fix issues, that's also any connected car's biggest weakness - you're one exploit away (or malicious employee with access) from remote root.. 1point 3acres
. Χ
more fun stuff: there's limited space on the emmc in the touchscreen system so updating maps can't be done using an image or a binary diff. so the thing rsync's map updates (all 2GB of them) from various places. they may have fixed that in the newer intel-based boards, but who knows.
. 1point 3 acres
autopilot had really high turnover at one point before release because some guy from space x came in and gave the entire dept a C pointer/memory test because Elon said they were "late" to ship..
. ----
    There's the story online of that hacker who was pulling software images off through the door Ethernet port and found that his car's >firmware was remotely downgraded after he uncovered and posted the first references to the P100 models.

    Does that sound plausible to you?. Χ

yup, i'm the guy that installed the older versions. this was a marketing mistake really. if i recall correctly, he ended up getting a marketing car or his car got tagged in the update system as a trusted car and he ended up getting pre-release stuff. this happened from time to time - sometimes marketing would sell off a car and the shit erp system wouldn't record the change. that car would then get prerelease and sometimes very broken firmware. i seem to recall another case where we just forgot to remove the prerelease materials from the official build, so all you had to do was look around.

the early days of tesla, post-roadster, early model s and the start of model x were good times - everyone was trying to prove the technology worked, we were innovating and making something that hadn't been done before. things really started to shit the bed around the time we pivoted from model 3 plans to shipping model x first. the falcon wing doors were such a shitshow. they ended up delaying the program almost a year, hence why model 3 basically skipped all the usual phases a car goes through for validation. i mean, come on - you have bumpers falling off in the rain, the interior is a disaster, there's no instrument cluster which takes your eyes off the road - this list just goes on.. check 1point3acres for more.

tesla basically runs their entire business like a just in time compiler only they don't treat warnings or errors as failures. most groups in the company don't cross-communicate so there's a lot of duplication of effort.

i once got pulled into a meeting because a car burned down when it was attached to a supercharger and we didn't get a log out of the car. normally under some emergency circumstances the car will try to upload a log when it thinks shit has gone really badly, but in this particular case it was far enough away from a tower it had half 3G connection and had to upload a 30MB log via HTTPS POST. the car burned down before it even got to 10MB and the system was only designed for exponential backoff retries, not resumption of in-progress. elon was calm about it, but we had to justify why we never had time to address it - maybe it was because we were all busy making unsafe features work?

also on the supercharger note - you can get blacklisted from using them if you charge on them all the time. that's because the supercharger bypasses the charging regulator boards and dumps directly into the pack at 300A/450v which creates a ton of wear on the battery. want to keep your range high? don't supercharge often.

    do they define “too often”?

algorithm-based now - the ai shit i was working on took into account a lot of factors to determine if you were abusing it before i left. the criteria takes into account the state of many components in the car, your driving patterns and other details. or it did anyway. not even sure that stuff is running still - they rotated projects in and out of existence pretty rapidly.

    what is elon like when stuff goes wrong due to his idiotic micromanagement and big stupid ideas?. 1point3acres

he's never wrong. his "open door policy" was an invitation to catch you breaking rank.

tesla was also in the news because they were doing cute shit like spinning up k8s clusters which had AWS IAM access to sensitive S3 buckets but wasn't ssl'd and the k8s mgmt api was available publicly. there were other teams running industrial control equipment with centos 7 an no hardening at all.
. check 1point3acres for more.
there was one time where a canadian kid stole the domain and redirected emails and managed to take over slack and a bunch of other shit because the idiot IT team didn't hide the registrar information or use something like markmonitor. the car-side stuff at least did full mtls at the time so it was ok, but lol did that kid get a lot of info.

**** the new stuff:-baidu 1point3acres

Some more:

    thats just what i want, the car manufacturer monitoring how i drive the car i own and deciding that features should be turned off after i >have purchased it, that's a good feature. you have no idea. any connected car is ripe for data harvesting and you (the consumer) should expect it going forward. on that note, china has a law in place that mandates all electric cars send real time telemetry to their government servers - model s/x/3, NIO cars and any other electric car if they're driving already complies with that law to be road certified. don't be surprised if that becomes a mandate in other countries

for all the shit that went down at tesla, there were some positive aspects. everyone i worked with really cared about physical safety and we put a lot of effort into making sure the engineering was sound so nobody got hurt. if you subtract autopilot, and that's a big if, the car is generally well designed minus the fit and finish issues + interior, but i'd argue that's never been tesla's strong point anyway. the cars are fast, the 2013-2014 model s lines were really good, solid, basic cars. my last straw was the summon feature - i strongly believe a car you are not in, backing out on its own from a parking space with the current sensors is super dangerous.
i was making jokes with the tesla expats when ol' musky launched his roadster into space that you could see the gaps in the fit and finish without a telescope. 1point3acres

just remembered some bits of trivia

    they took away our free snacks in deer creek and replaced them with shitty vendors
.1point3acres
    said vendors food poisoned people often enough osha or whatever the body is shut them down

    people were so mad about the free cereal being gone they'd intra-office snail mail bowls of cereal from the factory and post pictures in slack. .и

    deer creek's parking got so bad (too many people, not enough space) they hired permanent valets

    they were cited for the shitshow parking for fire safety violations (unconfirmed, but i believe it)

. 1point 3acres     elon publicly being a shitbag to trans people. From 1point 3acres bbs

    the first time we turned on real time telemetry for the dev fleet we caught somebody going 130mph over the san mateo bridge

    it networking so bad the company had permanent 5~8% consistent packet loss between various places (like, next rack)

    firmware git repo so large they had to mirror it (something like 2TB)

depending on when and what features you got (and if you got a marketing used car) they could go as low at $40k after incentives - but totally agree with you. fit/finish issues have been a thorn in their side forever
the touchscreen is kind of a safety issue in that you have to look at it to touch it, stealing focus. tactile buttons for some functions would have been better

the firmware repo was that size if you take into account a huge company, many devices in the car at play and incremental updates to firmware across all those devices + branches for people to do work in. i contributed to that mess by policy, not by choice, but whatever. i'd imagine they'd be smart enough to move to something like git lfs so it isn't as much of a pain

scale stuff:

tesla has a real thundering herd problem at this point. if you factor in common peak drive times for any region (bay area CA being the largest by pop) they have to weather something like 100k+ cars slamming servers all at once during rush hours. i saw this play out on some of the cj dashboards, it was fun to watch the production shit come to a grinding halt before they figured out they couldn't just-in-time the autoscale and had to provision ahead of time for peaks ..
..
i had to deal with marketing people sincerely asking me why we weren't going to run containers on the car in firmware. no, marketing, i don't care that the car would "update faster" or "features would release faster"
. 1point 3 acres
a web front-end (we'll say it's a cms that's php-based) that needed $500k in WAF bullshit just so we didn't get pwned every 5 minutes
.
fragmented installs of splunk. i think i counted well over 20 installs for various departments before they finally hired a decent data scientist that cleaned it up

so many random java, django, .net services from various places, more than i could count and i had to touch a lot of them with firmware. ActiveRecord controlling way way way too much. i consider this probably one of tesla's biggest scale problems - i don't think they actually know or can track exactly what they're running server side at all - so you end up with teams running vmware, nsx, k8s, openstack, hyper-v. ..

a car that has a json parser implemented in bash 3 because <interpreted language> is dangerous in the car. there are some seriously magic shell scripts on that thing that probably 3 people in the company understand in full
nodejs was a thing for a while but quickly broke down once we reached the 20k car mark - ended up replacing a bunch of that stuff with a Go variant.google  и

    bets on whether the fire was due to incompetence, act of nature, or deliberately set? ..
. ----
never attribute to malice what can more easily be explained by incompetence. Χ
.
    not surprised at all. earlier in Falcon 9 lifecycle at SpaceX, they kept having helium problems because the QC team kept signing off on >defective bottles and valves. do you think that attitude might have scared them into not saying anything?

absolutely. taking advantage of the "open door policy" was the fastest way to lose your job at tesla and from what i'm told, spacex, being run by the same guy was no different. there is so much pressure to ship on time they push people to work 14 hour days, 7 days a week - i did that for a while before i just couldn't take it anymore and just accepted being marked down in employee review for being late

the openvpn problem is easy to get around thundering herd/scale issues if you design it correctly and know how to run a network. in theory, you could get around a lot openvpn scale issues if you use bridged networking, ipv6 on the inside, and some redundant dhcp servers to hand out leases - that kind of shit won't work in most cloud providers though so you stuck at running that crap in a datacenter..--

tesla's issues around the services were many fold - the specifics would give away too much, but i'll say this: when you make all of your services depend on a single rdbms while simultaneously using the world's worst ORM, you get what's coming to you.
.--
i poked around on a 3 a friend has and after looking at a packet cap it looks like they're doing ssl'd amqp - i didn't see any openvpn packets so i suspect they got wise to how shitty it can be, but lol at running connected car stuff directly over the internet outside a private apn or a tunnel-baidu 1point3acres

    The staggering level of internal fragmentation reminds me of how PayPal was when I worked there in '09-15. They experimented for a few months with an "agile product solutions" team that basically >took "we need a widget that does this" orders and cranked out custom Java shit that never worked.

that's basically tesla in a nutshell only, i guess it kinda works. every different team has some kind of different service where you can get data but none of it published anywhere, there are no standards, and everyone just loves to write their own client implementations because they don't trust you to do it right (sorry that we don't have a client in C++ which is mandated by policy for the car)

poking holes in the firewall was always super fun - i would describe, in full detail all ports, sources, destinations, have security assessments done, etc and somehow, still, the firewall cj's would f*** up the ports. i once spent, and this is not a joke, 3 weeks chasing a single port down - i think that email thread had 100 reply-all's, two video confs and me visiting the firewall cj in fremont before it was finally fixed

    was there any sort of accountability for the devs there, or was it if you knew how to talk the talk you could bs your way through the ranks while producing nothing of value? was there any noticeable increase in the absurdity of musk's requests as time went on? anything particularly absurd he called for that was flat out shot down?

no, if you didn't do work it was really really obvious and they purged you quickly. that didn't mean it was any good but if you produced you were generally left to your own devices as long as you weren't breaking builds - this seemed to be true of most engineering teams.. 1point3acres
. Waral dи,
ol' musky did increasingly weird shit, but i wouldn't necessarily call it out of the ordinary for silicon valley - many folks, me included, for a time, viewed him as a bit of a Jobs-type. his behavior became really erratic around the time we wrapped up X and headed for 3 full steam - the more stuff piling on about autopilot, the more issues with the factory, the ongoing issues with X and then with 3 mfg, his ongoing spacex work - the dude really needs a nap and to just walk away from tesla at this point. its arguable he isn't running it successfully considering all the issues

    edit - running it successfully by silicon valley standards. too many issues to reach profitability because of really poor strategy and execution. too many people get wrapped up in his celebrity without really asking 'can he pull this off' which is the difference between him and Jobs - Jobs actually did shit

    yeah, i get that, it's just they make a product that will probably shit itself when the back end goes dark, and that product costs $65k-$120k so it's an outlier by sv standards.

the product shouldn't shit itself when the backend eventually goes dark - autopilot won't work, updates won't, remote phone shit won't but otherwise the driving and infotainment part of the car should still function if you pull the sim and put your own in. given how shit the firmware security is it'd be pretty easy to dump the firmware, compile up some statically linked tools for shits and just patch in your own services. there's been a few clever people on twitter who figured out you can run Go arm bins on the thing - after that it's just figuring out what crap you care about on CAN (if anything)..google  и

all that said, tesla did sell cars explicitly with the sim pulled and no network ever - service was always complaining to us because the ring logs on those cars would take hours to parse.

speaking of the ring logs - because there was no battery backed rtc, we had to stitch and best-guess times based on the intervals when the car did have valid time and patch that into the logs serially before they could be imported. inaccuracies in the signal data could and did lead to all kinds of bullshit when somebody needed to be debug issues. 1point3acres


评分

参与人数 3大米 +3 收起 理由
dada373678229 + 1 赞一个
jsc + 1 赞一个
h3ssian + 1 赞一个

查看全部评分

回复

使用道具 举报

地里匿名用户
🔗
匿名用户-OVNNN  | 添加认证 | 2021-6-19 04:20:50 来自APP
之前邻居是特斯拉的 他节假日都很少休假 一般就是加班 挺惨的
回复

使用道具 举报

地里匿名用户
🔗
匿名用户-HJUI8  | 添加认证 | 2021-6-19 05:48:09 来自APP
startup很多地方肯定很大厂不能比…
有个同学进去做了两年project manager 最近变成了sr product manager了…这升职速度这title随便给也是很爽的
回复

使用道具 举报

全局:
一个tesla recruiter告诉我朋友千万不要去。。。也没说原因,但是就是语重心长的样子
回复

使用道具 举报

全局:
来Tesla实习还行,full time就算了。。

评分

参与人数 1大米 +1 收起 理由
Thirteenthtree + 1 赞一个

查看全部评分

回复

使用道具 举报

您需要登录后才可以回帖 登录 | 注册账号
职场达人
  • ↑ 本版用于讨论职场各种干货话题,闲聊请去🔗聊聊或者🔗匿名版
  • ❌ 本版严禁水贴,引战,发布广告,拉群,贴个人联系方式,扣分无警告
  • ☑ 求职、面经等去 🔗北美求职和 🔗回国求职大区,刷题和学习请去 🔗终身学习大区
  • ☑ 请去专版发布 🔗内推, 🔗招聘信息,和讨论 🔗创业内容
  • ☑ PIP / DevList/ Need Support 等话题也已开设 🔗专版

本版积分规则

>
快速回复 返回顶部 返回列表