Jaakko Heinonen wrote: JH> On 2013-01-18, Alexander Motin wrote: JH> > > AM> > V> panic: make_dev_alias_v: bad si_name (error=22 si_name=enc_at_n5003048000bab37d/tpe0/slot_at_1/elmdesc_at_Slot 01/pass7) JH> JH> > > AM> The panic is triggered by the check added by the recent r244584 change. JH> > > AM> The space in device name came from the enclosure device, and I guess it JH> > > AM> may be quite often situation. Using human readable name supposed to help JH> > > AM> system administrators, but with spaces banned that may be a problem. JH> > > JH> > > That's was not created by human, it was generated (I think so) by system. JH> > JH> > These strings are flashed into enclosure firmware by manufacturer. JH> JH> You can't rely on that any string can be safely used as a device name JH> even if spaces were allowed. Consider for example duplicate names and JH> "../". JH> JH> Where these names are generated? The original report didn't contain a JH> backtrace. Yes. No backtrace, because of switching off all debuging in kernel. For now I can't use that's server for testing, but there are another servers waiting for upgrade. I will try to reproduce problem with kernel debuger enabled.Received on Fri Jan 18 2013 - 12:34:19 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:34 UTC