Re: panic after r244584

看板FB_current作者時間12年前 (2013/04/27 13:01), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串12/22 (看更多)
On 2013-01-18, Alexander Motin wrote: > > AM> > V> panic: make_dev_alias_v: bad si_name (error=22 si_name=enc@n5003048000bab37d/tpe0/slot@1/elmdesc@Slot 01/pass7) > > AM> The panic is triggered by the check added by the recent r244584 change. > > AM> The space in device name came from the enclosure device, and I guess it > > AM> may be quite often situation. Using human readable name supposed to help > > AM> system administrators, but with spaces banned that may be a problem. > > > > That's was not created by human, it was generated (I think so) by system. > > These strings are flashed into enclosure firmware by manufacturer. You can't rely on that any string can be safely used as a device name even if spaces were allowed. Consider for example duplicate names and "../". Where these names are generated? The original report didn't contain a backtrace. -- Jaakko _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
文章代碼(AID): #1HUrkt8m (FB_current)
討論串 (同標題文章)
文章代碼(AID): #1HUrkt8m (FB_current)